2025-11-24 17:13:41,213 - INFO - Loading models...
2025-11-24 17:13:41,239 - INFO - ✓ YOLO ONNX loaded
2025-11-24 17:13:41,276 - INFO - ✓ MediaPipe Face Mesh loaded
2025-11-24 17:13:41,855 - INFO - Frame 0 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 1
2025-11-24 17:13:42,281 - INFO - Frame 2 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 1
2025-11-24 17:13:42,557 - INFO - Frame 4 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 1
2025-11-24 17:13:42,982 - INFO - Frame 6 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-24 17:13:43,283 - INFO - Frame 8 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 1
2025-11-24 17:13:43,700 - INFO - Frame 10 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 1
2025-11-24 17:13:44,015 - INFO - Frame 12 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 1
2025-11-24 17:13:44,380 - INFO - Frame 14 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 1
2025-11-24 17:13:44,675 - INFO - Frame 16 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 1
2025-11-24 17:13:44,907 - INFO - Frame 18 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:13:45,158 - INFO - Frame 20 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 1
2025-11-24 17:13:45,427 - INFO - Frame 22 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 1
2025-11-24 17:13:45,681 - INFO - Frame 24 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 1
2025-11-24 17:13:45,935 - INFO - Frame 26 | PERCLOS: 0.00 | Yaw: 4.7° | Alerts: 1
2025-11-24 17:13:46,204 - INFO - Frame 28 | PERCLOS: 0.00 | Yaw: 5.2° | Alerts: 1
2025-11-24 17:13:46,487 - INFO - Frame 30 | PERCLOS: 0.24 | Yaw: 5.4° | Alerts: 1
2025-11-24 17:13:46,776 - INFO - Frame 32 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 1
2025-11-24 17:13:47,065 - INFO - Frame 34 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 1
2025-11-24 17:13:47,336 - INFO - Frame 36 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-24 17:13:47,608 - INFO - Frame 38 | PERCLOS: 0.00 | Yaw: 6.5° | Alerts: 1
2025-11-24 17:13:47,893 - INFO - Frame 40 | PERCLOS: 0.00 | Yaw: 6.1° | Alerts: 1
2025-11-24 17:13:48,172 - INFO - Frame 42 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 1
2025-11-24 17:13:48,376 - INFO - Frame 44 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 1
2025-11-24 17:13:48,614 - INFO - Frame 46 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 17:13:48,895 - INFO - Frame 48 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 17:13:49,108 - INFO - Frame 50 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 1
2025-11-24 17:13:49,286 - INFO - Frame 52 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 1
2025-11-24 17:13:49,528 - INFO - Frame 54 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 1
2025-11-24 17:13:49,794 - INFO - Frame 56 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-24 17:13:50,048 - INFO - Frame 58 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 1
2025-11-24 17:13:50,251 - INFO - Frame 60 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 1
2025-11-24 17:13:50,425 - INFO - Frame 62 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 1
2025-11-24 17:13:50,656 - INFO - Frame 64 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 17:13:50,911 - INFO - Frame 66 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-24 17:13:51,183 - INFO - Frame 68 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 1
2025-11-24 17:13:51,441 - INFO - Frame 70 | PERCLOS: 0.00 | Yaw: 5.2° | Alerts: 1
2025-11-24 17:13:51,707 - INFO - Frame 72 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 1
2025-11-24 17:13:51,978 - INFO - Frame 74 | PERCLOS: 0.00 | Yaw: 6.3° | Alerts: 1
2025-11-24 17:13:52,262 - INFO - Frame 76 | PERCLOS: 0.00 | Yaw: 6.6° | Alerts: 1
2025-11-24 17:13:52,540 - INFO - Frame 78 | PERCLOS: 0.00 | Yaw: 6.5° | Alerts: 1
2025-11-24 17:13:52,815 - INFO - Frame 80 | PERCLOS: 0.00 | Yaw: 6.8° | Alerts: 1
2025-11-24 17:13:53,093 - INFO - Frame 82 | PERCLOS: 0.00 | Yaw: 6.9° | Alerts: 1
2025-11-24 17:13:53,313 - INFO - Frame 84 | PERCLOS: 0.00 | Yaw: 6.8° | Alerts: 1
2025-11-24 17:13:53,419 - INFO - Frame 86 | PERCLOS: 0.00 | Yaw: 6.2° | Alerts: 1
2025-11-24 17:13:53,525 - INFO - Frame 88 | PERCLOS: 0.00 | Yaw: 6.1° | Alerts: 1
2025-11-24 17:13:53,685 - INFO - Frame 90 | PERCLOS: 0.00 | Yaw: 6.1° | Alerts: 1
2025-11-24 17:13:53,969 - INFO - Frame 92 | PERCLOS: 0.00 | Yaw: 6.3° | Alerts: 1
2025-11-24 17:13:54,241 - INFO - Frame 94 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 1
2025-11-24 17:13:54,453 - INFO - Frame 96 | PERCLOS: 0.00 | Yaw: 6.4° | Alerts: 1
2025-11-24 17:13:54,709 - INFO - Frame 98 | PERCLOS: 0.00 | Yaw: 6.3° | Alerts: 1
2025-11-24 17:13:54,986 - INFO - Frame 100 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 1
2025-11-24 17:13:55,203 - INFO - Frame 102 | PERCLOS: 0.12 | Yaw: 5.9° | Alerts: 1
2025-11-24 17:13:55,453 - INFO - Frame 104 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 17:13:55,731 - INFO - Frame 106 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 1
2025-11-24 17:13:56,023 - INFO - Frame 108 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 1
2025-11-24 17:13:56,294 - INFO - Frame 110 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 1
2025-11-24 17:13:56,572 - INFO - Frame 112 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 1
2025-11-24 17:13:56,851 - INFO - Frame 114 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 17:13:57,052 - INFO - Frame 116 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-24 17:13:57,235 - INFO - Frame 118 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 17:13:57,466 - INFO - Frame 120 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 17:13:57,735 - INFO - Frame 122 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 17:13:58,002 - INFO - Frame 124 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 1
2025-11-24 17:13:58,271 - INFO - Frame 126 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 17:13:58,537 - INFO - Frame 128 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 1
2025-11-24 17:13:58,806 - INFO - Frame 130 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 1
2025-11-24 17:13:59,080 - INFO - Frame 132 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 1
2025-11-24 17:13:59,355 - INFO - Frame 134 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 17:13:59,627 - INFO - Frame 136 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 17:13:59,891 - INFO - Frame 138 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 17:14:00,147 - INFO - Frame 140 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 17:14:00,408 - INFO - Frame 142 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 1
2025-11-24 17:14:00,680 - INFO - Frame 144 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 1
2025-11-24 17:14:00,951 - INFO - Frame 146 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 1
2025-11-24 17:14:01,245 - INFO - Frame 148 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 1
2025-11-24 17:14:01,513 - INFO - Frame 150 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 17:14:01,710 - INFO - Frame 152 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-24 17:14:01,939 - INFO - Frame 154 | PERCLOS: 0.65 | Yaw: 4.4° | Alerts: 2
2025-11-24 17:14:02,194 - INFO - Frame 156 | PERCLOS: 0.57 | Yaw: 6.5° | Alerts: 2
2025-11-24 17:14:02,460 - INFO - Frame 158 | PERCLOS: 0.55 | Yaw: 6.1° | Alerts: 2
2025-11-24 17:14:02,733 - INFO - Frame 160 | PERCLOS: 0.56 | Yaw: 5.4° | Alerts: 2
2025-11-24 17:14:03,010 - INFO - Frame 162 | PERCLOS: 0.36 | Yaw: 5.1° | Alerts: 2
2025-11-24 17:14:03,262 - INFO - Frame 164 | PERCLOS: 0.43 | Yaw: 4.8° | Alerts: 2
2025-11-24 17:14:03,470 - INFO - Frame 166 | PERCLOS: 0.53 | Yaw: 4.8° | Alerts: 2
2025-11-24 17:14:03,705 - INFO - Frame 168 | PERCLOS: 0.56 | Yaw: 4.4° | Alerts: 2
2025-11-24 17:14:03,959 - INFO - Frame 170 | PERCLOS: 0.24 | Yaw: 3.6° | Alerts: 1
2025-11-24 17:14:04,215 - INFO - Frame 172 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-24 17:14:04,418 - INFO - Frame 174 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 17:14:04,644 - INFO - Frame 176 | PERCLOS: 0.44 | Yaw: 4.1° | Alerts: 2
2025-11-24 17:14:04,900 - INFO - Frame 178 | PERCLOS: 0.36 | Yaw: 4.7° | Alerts: 2
2025-11-24 17:14:05,157 - INFO - Frame 180 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-24 17:14:05,426 - INFO - Frame 182 | PERCLOS: 0.00 | Yaw: 4.7° | Alerts: 1
2025-11-24 17:14:05,624 - INFO - Frame 184 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 1
2025-11-24 17:14:05,850 - INFO - Frame 186 | PERCLOS: 0.00 | Yaw: 4.1° | Alerts: 1
2025-11-24 17:14:06,110 - INFO - Frame 188 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 17:14:06,365 - INFO - Frame 190 | PERCLOS: 0.20 | Yaw: 4.5° | Alerts: 1
2025-11-24 17:14:06,617 - INFO - Frame 192 | PERCLOS: 0.32 | Yaw: 5.4° | Alerts: 2
2025-11-24 17:14:06,822 - INFO - Frame 194 | PERCLOS: 0.47 | Yaw: 5.1° | Alerts: 2
2025-11-24 17:14:06,928 - INFO - Frame 196 | PERCLOS: 0.42 | Yaw: 5.1° | Alerts: 2
2025-11-24 17:14:07,034 - INFO - Frame 198 | PERCLOS: 0.00 | Yaw: 4.9° | Alerts: 1
2025-11-24 17:14:07,145 - INFO - Frame 200 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 1
2025-11-24 17:14:07,431 - INFO - Frame 202 | PERCLOS: 0.00 | Yaw: 5.2° | Alerts: 1
2025-11-24 17:14:07,699 - INFO - Frame 204 | PERCLOS: 0.00 | Yaw: 5.4° | Alerts: 1
2025-11-24 17:14:07,962 - INFO - Frame 206 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 1
2025-11-24 17:14:08,228 - INFO - Frame 208 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-24 17:14:08,498 - INFO - Frame 210 | PERCLOS: 0.24 | Yaw: 5.1° | Alerts: 1
2025-11-24 17:14:08,761 - INFO - Frame 212 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 17:14:09,031 - INFO - Frame 214 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 17:14:09,296 - INFO - Frame 216 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 17:14:09,573 - INFO - Frame 218 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 1
2025-11-24 17:14:09,857 - INFO - Frame 220 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 1
2025-11-24 17:14:10,116 - INFO - Frame 222 | PERCLOS: 0.06 | Yaw: 1.4° | Alerts: 1
2025-11-24 17:14:10,314 - INFO - Frame 224 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 1
2025-11-24 17:14:10,547 - INFO - Frame 226 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-24 17:14:10,763 - INFO - Frame 228 | PERCLOS: 0.00 | Yaw: 5.1° | Alerts: 1
2025-11-24 17:14:11,011 - INFO - Frame 230 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-24 17:14:11,287 - INFO - Frame 232 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-24 17:14:11,563 - INFO - Frame 234 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 1
2025-11-24 17:14:11,834 - INFO - Frame 236 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-24 17:14:12,114 - INFO - Frame 238 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-24 17:14:12,366 - INFO - Frame 240 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-24 17:14:12,574 - INFO - Frame 242 | PERCLOS: 0.00 | Yaw: 4.7° | Alerts: 1
2025-11-24 17:14:12,817 - INFO - Frame 244 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 1
2025-11-24 17:14:13,085 - INFO - Frame 246 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 17:14:13,344 - INFO - Frame 248 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-24 17:14:13,602 - INFO - Frame 250 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 17:14:13,879 - INFO - Frame 252 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 17:14:14,151 - INFO - Frame 254 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 17:14:14,426 - INFO - Frame 256 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 17:14:14,695 - INFO - Frame 258 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 17:14:14,965 - INFO - Frame 260 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 17:14:15,175 - INFO - Frame 262 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 17:14:15,417 - INFO - Frame 264 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 17:14:15,616 - INFO - Frame 266 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 17:14:15,849 - INFO - Frame 268 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 17:14:16,130 - INFO - Frame 270 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 17:14:16,331 - INFO - Frame 272 | PERCLOS: 0.35 | Yaw: 3.4° | Alerts: 2
2025-11-24 17:14:16,569 - INFO - Frame 274 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 1
2025-11-24 17:14:16,779 - INFO - Frame 276 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 17:14:17,006 - INFO - Frame 278 | PERCLOS: 0.07 | Yaw: 2.3° | Alerts: 1
2025-11-24 17:14:17,205 - INFO - Frame 280 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:14:17,379 - INFO - Frame 282 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 17:14:17,551 - INFO - Frame 284 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:14:17,724 - INFO - Frame 286 | PERCLOS: 0.00 | Yaw: 5.9° | Alerts: 1
2025-11-24 17:14:17,961 - INFO - Frame 288 | PERCLOS: 0.00 | Yaw: 5.8° | Alerts: 0
2025-11-24 17:14:18,168 - INFO - Frame 290 | PERCLOS: 0.00 | Yaw: 5.8° | Alerts: 0
2025-11-24 17:14:18,340 - INFO - Frame 292 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 1
2025-11-24 17:14:18,563 - INFO - Frame 294 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 0
2025-11-24 17:14:18,733 - INFO - Frame 296 | PERCLOS: 0.00 | Yaw: 6.4° | Alerts: 1
2025-11-24 17:14:18,954 - INFO - Frame 298 | PERCLOS: 0.13 | Yaw: 12.2° | Alerts: 1
2025-11-24 17:14:19,198 - INFO - Frame 300 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:14:19,508 - INFO - Frame 302 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 17:14:19,771 - INFO - Frame 304 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-24 17:14:20,038 - INFO - Frame 306 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 17:14:20,309 - INFO - Frame 308 | PERCLOS: 0.26 | Yaw: 4.2° | Alerts: 1
2025-11-24 17:14:20,582 - INFO - Frame 310 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:14:20,855 - INFO - Frame 312 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 1
2025-11-24 17:14:21,106 - INFO - Frame 314 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 1
2025-11-24 17:14:21,357 - INFO - Frame 316 | PERCLOS: 0.23 | Yaw: 8.3° | Alerts: 1
2025-11-24 17:14:21,622 - INFO - Frame 318 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:14:21,885 - INFO - Frame 320 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-24 17:14:22,135 - INFO - Frame 322 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 17:14:22,392 - INFO - Frame 324 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:14:22,660 - INFO - Frame 326 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-24 17:14:22,872 - INFO - Frame 328 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 17:14:23,117 - INFO - Frame 330 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 17:14:23,388 - INFO - Frame 332 | PERCLOS: 0.17 | Yaw: 4.7° | Alerts: 1
2025-11-24 17:14:23,621 - INFO - Frame 334 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-24 17:14:23,808 - INFO - Frame 336 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 17:14:24,055 - INFO - Frame 338 | PERCLOS: 0.27 | Yaw: 3.8° | Alerts: 1
2025-11-24 17:14:24,320 - INFO - Frame 340 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 17:14:24,587 - INFO - Frame 342 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 17:14:24,797 - INFO - Frame 344 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-24 17:14:25,041 - INFO - Frame 346 | PERCLOS: 0.00 | Yaw: 11.2° | Alerts: 1
2025-11-24 17:14:25,309 - INFO - Frame 348 | PERCLOS: 0.00 | Yaw: 13.0° | Alerts: 1
2025-11-24 17:14:25,577 - INFO - Frame 350 | PERCLOS: 0.00 | Yaw: 14.5° | Alerts: 1
2025-11-24 17:14:25,842 - INFO - Frame 352 | PERCLOS: 0.00 | Yaw: 13.9° | Alerts: 1
2025-11-24 17:14:26,105 - INFO - Frame 354 | PERCLOS: 0.00 | Yaw: 13.3° | Alerts: 1
2025-11-24 17:14:26,359 - INFO - Frame 356 | PERCLOS: 0.00 | Yaw: 13.0° | Alerts: 1
2025-11-24 17:14:26,624 - INFO - Frame 358 | PERCLOS: 0.00 | Yaw: 13.4° | Alerts: 1
2025-11-24 17:14:26,887 - INFO - Frame 360 | PERCLOS: 0.11 | Yaw: -1.3° | Alerts: 1
2025-11-24 17:14:27,145 - INFO - Frame 362 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 17:14:27,411 - INFO - Frame 364 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 1
2025-11-24 17:14:27,619 - INFO - Frame 366 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 17:14:27,792 - INFO - Frame 368 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-24 17:14:27,963 - INFO - Frame 370 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-24 17:14:28,190 - INFO - Frame 372 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 17:14:28,390 - INFO - Frame 374 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 17:14:28,613 - INFO - Frame 376 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 17:14:28,871 - INFO - Frame 378 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 1
2025-11-24 17:14:29,124 - INFO - Frame 380 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 1
2025-11-24 17:14:29,402 - INFO - Frame 382 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 17:14:29,681 - INFO - Frame 384 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-24 17:14:29,958 - INFO - Frame 386 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:14:30,225 - INFO - Frame 388 | PERCLOS: 0.09 | Yaw: 3.8° | Alerts: 1
2025-11-24 17:14:30,435 - INFO - Frame 390 | PERCLOS: 0.14 | Yaw: 5.1° | Alerts: 1
2025-11-24 17:14:30,673 - INFO - Frame 392 | PERCLOS: 0.30 | Yaw: 3.8° | Alerts: 1
2025-11-24 17:14:30,939 - INFO - Frame 394 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 1
2025-11-24 17:14:31,147 - INFO - Frame 396 | PERCLOS: 0.14 | Yaw: 5.2° | Alerts: 1
2025-11-24 17:14:31,371 - INFO - Frame 398 | PERCLOS: 0.11 | Yaw: -2.8° | Alerts: 1
2025-11-24 17:14:31,622 - INFO - Frame 400 | PERCLOS: 0.00 | Yaw: -6.3° | Alerts: 1
2025-11-24 17:14:31,876 - INFO - Frame 402 | PERCLOS: 0.00 | Yaw: -6.1° | Alerts: 1
2025-11-24 17:14:32,130 - INFO - Frame 404 | PERCLOS: 0.00 | Yaw: -5.8° | Alerts: 1
2025-11-24 17:14:32,400 - INFO - Frame 406 | PERCLOS: 0.00 | Yaw: -6.5° | Alerts: 1
2025-11-24 17:14:32,597 - INFO - Frame 408 | PERCLOS: 0.09 | Yaw: -5.6° | Alerts: 1
2025-11-24 17:14:32,824 - INFO - Frame 410 | PERCLOS: 0.00 | Yaw: -4.8° | Alerts: 1
2025-11-24 17:14:33,075 - INFO - Frame 412 | PERCLOS: 0.00 | Yaw: -3.8° | Alerts: 1
2025-11-24 17:14:33,275 - INFO - Frame 414 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:14:33,449 - INFO - Frame 416 | PERCLOS: 0.11 | Yaw: 3.0° | Alerts: 1
2025-11-24 17:14:33,670 - INFO - Frame 418 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 17:14:33,938 - INFO - Frame 420 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 17:14:34,199 - INFO - Frame 422 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-24 17:14:34,459 - INFO - Frame 424 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 17:14:34,721 - INFO - Frame 426 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 1
2025-11-24 17:14:34,982 - INFO - Frame 428 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:14:35,240 - INFO - Frame 430 | PERCLOS: 0.00 | Yaw: -3.3° | Alerts: 1
2025-11-24 17:14:35,496 - INFO - Frame 432 | PERCLOS: 0.00 | Yaw: -2.1° | Alerts: 1
2025-11-24 17:14:35,743 - INFO - Frame 434 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:14:35,918 - INFO - Frame 436 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 17:14:36,182 - INFO - Frame 438 | PERCLOS: 0.00 | Yaw: 4.8° | Alerts: 1
2025-11-24 17:14:36,450 - INFO - Frame 440 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 1
2025-11-24 17:14:36,701 - INFO - Frame 442 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 1
2025-11-24 17:14:36,901 - INFO - Frame 444 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 17:14:37,140 - INFO - Frame 446 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-24 17:14:37,349 - INFO - Frame 448 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 1
2025-11-24 17:14:37,581 - INFO - Frame 450 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 1
2025-11-24 17:14:37,780 - INFO - Frame 452 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 17:14:38,023 - INFO - Frame 454 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-24 17:14:38,228 - INFO - Frame 456 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-24 17:14:38,498 - INFO - Frame 458 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 17:14:38,770 - INFO - Frame 460 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 1
2025-11-24 17:14:39,044 - INFO - Frame 462 | PERCLOS: 0.00 | Yaw: 4.8° | Alerts: 1
2025-11-24 17:14:39,314 - INFO - Frame 464 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-24 17:14:39,525 - INFO - Frame 466 | PERCLOS: 0.00 | Yaw: 4.9° | Alerts: 1
2025-11-24 17:14:39,799 - INFO - Frame 468 | PERCLOS: 0.00 | Yaw: 4.9° | Alerts: 1
2025-11-24 17:14:39,988 - INFO - Frame 470 | PERCLOS: 0.08 | Yaw: 5.0° | Alerts: 1
2025-11-24 17:14:40,248 - INFO - Frame 472 | PERCLOS: 0.07 | Yaw: 4.5° | Alerts: 1
2025-11-24 17:14:40,529 - INFO - Frame 474 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 17:14:40,790 - INFO - Frame 476 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 1
2025-11-24 17:14:41,073 - INFO - Frame 478 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-24 17:14:41,349 - INFO - Frame 480 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 1
2025-11-24 17:14:41,623 - INFO - Frame 482 | PERCLOS: 0.00 | Yaw: 6.3° | Alerts: 1
2025-11-24 17:14:41,889 - INFO - Frame 484 | PERCLOS: 0.00 | Yaw: 6.6° | Alerts: 1
2025-11-24 17:14:42,143 - INFO - Frame 486 | PERCLOS: 0.00 | Yaw: 7.0° | Alerts: 1
2025-11-24 17:14:42,414 - INFO - Frame 488 | PERCLOS: 0.00 | Yaw: 7.2° | Alerts: 1
2025-11-24 17:14:42,697 - INFO - Frame 490 | PERCLOS: 0.00 | Yaw: 7.0° | Alerts: 1
2025-11-24 17:14:42,804 - INFO - Frame 492 | PERCLOS: 0.00 | Yaw: 4.1° | Alerts: 1
2025-11-24 17:14:42,910 - INFO - Frame 494 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 17:14:43,017 - INFO - Frame 496 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 17:14:43,181 - INFO - Frame 498 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 1
2025-11-24 17:14:43,444 - INFO - Frame 500 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 17:14:43,715 - INFO - Frame 502 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 1
2025-11-24 17:14:43,995 - INFO - Frame 504 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 1
2025-11-24 17:14:44,263 - INFO - Frame 506 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 1
2025-11-24 17:14:44,541 - INFO - Frame 508 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:14:44,760 - INFO - Frame 510 | PERCLOS: 0.24 | Yaw: 0.4° | Alerts: 1
2025-11-24 17:14:45,010 - INFO - Frame 512 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 1
2025-11-24 17:14:45,289 - INFO - Frame 514 | PERCLOS: 0.00 | Yaw: 0.2° | Alerts: 1
2025-11-24 17:14:45,563 - INFO - Frame 516 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 1
2025-11-24 17:14:45,772 - INFO - Frame 518 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 1
2025-11-24 17:14:45,998 - INFO - Frame 520 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 1
2025-11-24 17:14:46,300 - INFO - Frame 522 | PERCLOS: 0.00 | Yaw: 0.2° | Alerts: 1
2025-11-24 17:14:46,570 - INFO - Frame 524 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 1
2025-11-24 17:14:46,858 - INFO - Frame 526 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 1
2025-11-24 17:14:47,089 - INFO - Frame 528 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 1
2025-11-24 17:14:47,344 - INFO - Frame 530 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 1
2025-11-24 17:14:47,600 - INFO - Frame 532 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 17:14:47,854 - INFO - Frame 534 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 1
2025-11-24 17:14:48,123 - INFO - Frame 536 | PERCLOS: 0.00 | Yaw: 6.3° | Alerts: 1
2025-11-24 17:14:48,388 - INFO - Frame 538 | PERCLOS: 0.00 | Yaw: 6.8° | Alerts: 1
2025-11-24 17:14:48,654 - INFO - Frame 540 | PERCLOS: 0.00 | Yaw: 7.4° | Alerts: 1
2025-11-24 17:14:48,931 - INFO - Frame 542 | PERCLOS: 0.00 | Yaw: 6.7° | Alerts: 1
2025-11-24 17:14:49,198 - INFO - Frame 544 | PERCLOS: 0.00 | Yaw: 7.1° | Alerts: 1
2025-11-24 17:14:49,417 - INFO - Frame 546 | PERCLOS: 0.00 | Yaw: 6.6° | Alerts: 1
2025-11-24 17:14:49,655 - INFO - Frame 548 | PERCLOS: 0.00 | Yaw: 6.1° | Alerts: 1
2025-11-24 17:14:49,857 - INFO - Frame 550 | PERCLOS: 0.00 | Yaw: 6.3° | Alerts: 1
2025-11-24 17:14:50,115 - INFO - Frame 552 | PERCLOS: 0.00 | Yaw: 7.0° | Alerts: 1
2025-11-24 17:14:50,289 - INFO - Frame 554 | PERCLOS: 0.00 | Yaw: 6.8° | Alerts: 1
2025-11-24 17:14:50,550 - INFO - Frame 556 | PERCLOS: 0.00 | Yaw: 6.7° | Alerts: 1
2025-11-24 17:14:50,821 - INFO - Frame 558 | PERCLOS: 0.00 | Yaw: 6.6° | Alerts: 1
2025-11-24 17:14:51,078 - INFO - Frame 560 | PERCLOS: 0.00 | Yaw: 6.7° | Alerts: 1
2025-11-24 17:14:51,331 - INFO - Frame 562 | PERCLOS: 0.00 | Yaw: 6.5° | Alerts: 1
2025-11-24 17:14:51,587 - INFO - Frame 564 | PERCLOS: 0.00 | Yaw: 6.4° | Alerts: 1
2025-11-24 17:14:51,843 - INFO - Frame 566 | PERCLOS: 0.00 | Yaw: 6.8° | Alerts: 1
2025-11-24 17:14:52,112 - INFO - Frame 568 | PERCLOS: 0.00 | Yaw: 6.5° | Alerts: 1
2025-11-24 17:14:52,383 - INFO - Frame 570 | PERCLOS: 0.00 | Yaw: 6.7° | Alerts: 1
2025-11-24 17:14:52,658 - INFO - Frame 572 | PERCLOS: 0.00 | Yaw: 6.2° | Alerts: 1
2025-11-24 17:14:52,923 - INFO - Frame 574 | PERCLOS: 0.00 | Yaw: 6.5° | Alerts: 1
2025-11-24 17:14:53,126 - INFO - Frame 576 | PERCLOS: 0.00 | Yaw: 6.9° | Alerts: 1
2025-11-24 17:14:53,356 - INFO - Frame 578 | PERCLOS: 0.00 | Yaw: 7.1° | Alerts: 1
2025-11-24 17:16:23,144 - INFO - Loading models...
2025-11-24 17:16:23,164 - INFO - ✓ YOLO ONNX loaded
2025-11-24 17:16:23,202 - INFO - ✓ MediaPipe Face Mesh loaded
2025-11-24 17:16:23,765 - INFO - Frame 0 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-24 17:16:23,980 - INFO - Frame 2 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-24 17:16:24,144 - INFO - Frame 4 | PERCLOS: 0.00 | Yaw: 4.7° | Alerts: 1
2025-11-24 17:16:24,371 - INFO - Frame 6 | PERCLOS: 0.00 | Yaw: 4.7° | Alerts: 1
2025-11-24 17:16:24,561 - INFO - Frame 8 | PERCLOS: 0.00 | Yaw: 4.8° | Alerts: 1
2025-11-24 17:16:24,769 - INFO - Frame 10 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 1
2025-11-24 17:16:24,981 - INFO - Frame 12 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 1
2025-11-24 17:16:25,177 - INFO - Frame 14 | PERCLOS: 0.00 | Yaw: 4.7° | Alerts: 1
2025-11-24 17:16:25,362 - INFO - Frame 16 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-24 17:16:25,534 - INFO - Frame 18 | PERCLOS: 0.00 | Yaw: 4.1° | Alerts: 1
2025-11-24 17:16:25,735 - INFO - Frame 20 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-24 17:16:25,898 - INFO - Frame 22 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 1
2025-11-24 17:16:26,105 - INFO - Frame 24 | PERCLOS: 0.00 | Yaw: 5.1° | Alerts: 1
2025-11-24 17:16:26,324 - INFO - Frame 26 | PERCLOS: 0.00 | Yaw: 5.8° | Alerts: 1
2025-11-24 17:16:26,498 - INFO - Frame 28 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-24 17:16:26,706 - INFO - Frame 30 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-24 17:16:26,864 - INFO - Frame 32 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:16:27,068 - INFO - Frame 34 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-24 17:16:27,237 - INFO - Frame 36 | PERCLOS: 0.32 | Yaw: 5.7° | Alerts: 2
2025-11-24 17:16:27,429 - INFO - Frame 38 | PERCLOS: 0.00 | Yaw: 4.7° | Alerts: 1
2025-11-24 17:16:27,622 - INFO - Frame 40 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 1
2025-11-24 17:16:27,818 - INFO - Frame 42 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-24 17:16:28,032 - INFO - Frame 44 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 1
2025-11-24 17:16:28,196 - INFO - Frame 46 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 17:16:28,406 - INFO - Frame 48 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 17:16:28,573 - INFO - Frame 50 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 17:16:28,790 - INFO - Frame 52 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 17:16:28,994 - INFO - Frame 54 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 1
2025-11-24 17:16:29,185 - INFO - Frame 56 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 1
2025-11-24 17:16:29,383 - INFO - Frame 58 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 1
2025-11-24 17:16:29,576 - INFO - Frame 60 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 17:16:29,790 - INFO - Frame 62 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-24 17:16:29,983 - INFO - Frame 64 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 17:16:30,153 - INFO - Frame 66 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-24 17:16:30,346 - INFO - Frame 68 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 1
2025-11-24 17:16:30,560 - INFO - Frame 70 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 1
2025-11-24 17:16:30,748 - INFO - Frame 72 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-24 17:16:30,942 - INFO - Frame 74 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 17:16:31,107 - INFO - Frame 76 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-24 17:16:31,300 - INFO - Frame 78 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-24 17:16:31,498 - INFO - Frame 80 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 17:16:31,698 - INFO - Frame 82 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 17:16:31,892 - INFO - Frame 84 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 17:16:32,106 - INFO - Frame 86 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 17:16:32,276 - INFO - Frame 88 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 17:16:32,489 - INFO - Frame 90 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 1
2025-11-24 17:16:32,657 - INFO - Frame 92 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 17:16:32,856 - INFO - Frame 94 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 17:16:33,045 - INFO - Frame 96 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-24 17:16:33,241 - INFO - Frame 98 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 17:16:33,457 - INFO - Frame 100 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 17:16:33,632 - INFO - Frame 102 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 1
2025-11-24 17:16:33,846 - INFO - Frame 104 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 1
2025-11-24 17:16:34,034 - INFO - Frame 106 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-24 17:16:34,194 - INFO - Frame 108 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 1
2025-11-24 17:16:34,387 - INFO - Frame 110 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 1
2025-11-24 17:16:34,579 - INFO - Frame 112 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 1
2025-11-24 17:16:34,878 - INFO - Frame 114 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 17:16:35,100 - INFO - Frame 116 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 1
2025-11-24 17:16:35,287 - INFO - Frame 118 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 1
2025-11-24 17:16:35,480 - INFO - Frame 120 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 17:16:35,673 - INFO - Frame 122 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 17:16:35,890 - INFO - Frame 124 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 1
2025-11-24 17:16:36,070 - INFO - Frame 126 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-24 17:16:36,296 - INFO - Frame 128 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 17:16:36,495 - INFO - Frame 130 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 17:16:36,661 - INFO - Frame 132 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 1
2025-11-24 17:16:36,859 - INFO - Frame 134 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 1
2025-11-24 17:16:37,075 - INFO - Frame 136 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 17:16:37,269 - INFO - Frame 138 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 17:16:37,484 - INFO - Frame 140 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 17:16:37,652 - INFO - Frame 142 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 1
2025-11-24 17:16:37,847 - INFO - Frame 144 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-24 17:16:38,042 - INFO - Frame 146 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 17:16:38,234 - INFO - Frame 148 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 17:16:38,428 - INFO - Frame 150 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 17:16:38,624 - INFO - Frame 152 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 17:16:38,827 - INFO - Frame 154 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 17:16:39,018 - INFO - Frame 156 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-24 17:16:39,197 - INFO - Frame 158 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 17:16:39,388 - INFO - Frame 160 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 17:16:39,558 - INFO - Frame 162 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 1
2025-11-24 17:16:39,750 - INFO - Frame 164 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 17:16:39,931 - INFO - Frame 166 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 17:16:40,140 - INFO - Frame 168 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 17:16:40,309 - INFO - Frame 170 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 17:16:40,506 - INFO - Frame 172 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 17:16:40,697 - INFO - Frame 174 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 17:16:40,892 - INFO - Frame 176 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 17:16:41,106 - INFO - Frame 178 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 17:16:41,276 - INFO - Frame 180 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 17:16:41,494 - INFO - Frame 182 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 1
2025-11-24 17:16:41,687 - INFO - Frame 184 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 17:16:41,859 - INFO - Frame 186 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 17:16:42,055 - INFO - Frame 188 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 17:16:42,290 - INFO - Frame 190 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 17:16:42,478 - INFO - Frame 192 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 17:16:42,649 - INFO - Frame 194 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 17:16:42,861 - INFO - Frame 196 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 17:16:43,026 - INFO - Frame 198 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 1
2025-11-24 17:16:43,219 - INFO - Frame 200 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 1
2025-11-24 17:16:43,414 - INFO - Frame 202 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 17:16:43,607 - INFO - Frame 204 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 17:16:43,801 - INFO - Frame 206 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 1
2025-11-24 17:16:44,011 - INFO - Frame 208 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 17:16:44,184 - INFO - Frame 210 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 17:16:44,380 - INFO - Frame 212 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 1
2025-11-24 17:16:44,578 - INFO - Frame 214 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 1
2025-11-24 17:16:44,771 - INFO - Frame 216 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:16:44,964 - INFO - Frame 218 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:16:45,264 - INFO - Frame 220 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:16:45,466 - INFO - Frame 222 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:16:45,672 - INFO - Frame 224 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:16:45,861 - INFO - Frame 226 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:16:46,055 - INFO - Frame 228 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:16:46,248 - INFO - Frame 230 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:16:46,441 - INFO - Frame 232 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:16:46,635 - INFO - Frame 234 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:16:46,830 - INFO - Frame 236 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:16:47,024 - INFO - Frame 238 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:16:47,236 - INFO - Frame 240 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:16:47,425 - INFO - Frame 242 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:16:47,582 - INFO - Frame 244 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:16:47,791 - INFO - Frame 246 | PERCLOS: 0.00 | Yaw: 4.8° | Alerts: 1
2025-11-24 17:16:47,961 - INFO - Frame 248 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 17:16:48,154 - INFO - Frame 250 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 1
2025-11-24 17:16:48,347 - INFO - Frame 252 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 17:16:48,557 - INFO - Frame 254 | PERCLOS: 0.00 | Yaw: 4.1° | Alerts: 1
2025-11-24 17:16:48,747 - INFO - Frame 256 | PERCLOS: 0.00 | Yaw: 5.9° | Alerts: 1
2025-11-24 17:16:48,953 - INFO - Frame 258 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:16:49,116 - INFO - Frame 260 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:16:49,315 - INFO - Frame 262 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:16:49,482 - INFO - Frame 264 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:16:49,682 - INFO - Frame 266 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:16:49,859 - INFO - Frame 268 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:16:50,018 - INFO - Frame 270 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:16:50,207 - INFO - Frame 272 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:16:50,420 - INFO - Frame 274 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:16:50,592 - INFO - Frame 276 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:16:50,808 - INFO - Frame 278 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:16:50,979 - INFO - Frame 280 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:16:51,173 - INFO - Frame 282 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:16:51,367 - INFO - Frame 284 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:16:51,565 - INFO - Frame 286 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:16:51,759 - INFO - Frame 288 | PERCLOS: 0.00 | Yaw: 4.1° | Alerts: 1
2025-11-24 17:16:51,929 - INFO - Frame 290 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 1
2025-11-24 17:16:52,123 - INFO - Frame 292 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 1
2025-11-24 17:16:52,315 - INFO - Frame 294 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 1
2025-11-24 17:16:52,528 - INFO - Frame 296 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 1
2025-11-24 17:16:52,744 - INFO - Frame 298 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 1
2025-11-24 17:16:52,937 - INFO - Frame 300 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 1
2025-11-24 17:16:53,122 - INFO - Frame 302 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 1
2025-11-24 17:16:53,278 - INFO - Frame 304 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 1
2025-11-24 17:16:53,472 - INFO - Frame 306 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 1
2025-11-24 17:16:53,679 - INFO - Frame 308 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 1
2025-11-24 17:16:53,858 - INFO - Frame 310 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 1
2025-11-24 17:16:54,036 - INFO - Frame 312 | PERCLOS: 0.38 | Yaw: 1.8° | Alerts: 2
2025-11-24 17:16:54,223 - INFO - Frame 314 | PERCLOS: 0.32 | Yaw: 3.5° | Alerts: 2
2025-11-24 17:16:54,406 - INFO - Frame 316 | PERCLOS: 0.06 | Yaw: 4.4° | Alerts: 1
2025-11-24 17:16:54,580 - INFO - Frame 318 | PERCLOS: 0.03 | Yaw: 4.1° | Alerts: 1
2025-11-24 17:16:54,743 - INFO - Frame 320 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 17:16:54,849 - INFO - Frame 322 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 17:16:54,954 - INFO - Frame 324 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 17:16:55,105 - INFO - Frame 326 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 17:16:55,378 - INFO - Frame 328 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 17:16:55,617 - INFO - Frame 330 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 1
2025-11-24 17:16:55,855 - INFO - Frame 332 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 17:16:56,129 - INFO - Frame 334 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 1
2025-11-24 17:16:56,400 - INFO - Frame 336 | PERCLOS: 0.29 | Yaw: 2.8° | Alerts: 1
2025-11-24 17:16:56,612 - INFO - Frame 338 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 1
2025-11-24 17:16:56,853 - INFO - Frame 340 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 1
2025-11-24 17:16:57,124 - INFO - Frame 342 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 1
2025-11-24 17:16:57,394 - INFO - Frame 344 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 1
2025-11-24 17:16:57,665 - INFO - Frame 346 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 1
2025-11-24 17:16:57,939 - INFO - Frame 348 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 1
2025-11-24 17:16:58,212 - INFO - Frame 350 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 1
2025-11-24 17:16:58,464 - INFO - Frame 352 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 1
2025-11-24 17:16:58,719 - INFO - Frame 354 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 1
2025-11-24 17:16:58,918 - INFO - Frame 356 | PERCLOS: 0.13 | Yaw: 2.3° | Alerts: 1
2025-11-24 17:16:59,092 - INFO - Frame 358 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 1
2025-11-24 17:16:59,320 - INFO - Frame 360 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 17:16:59,573 - INFO - Frame 362 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 17:16:59,844 - INFO - Frame 364 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 17:17:00,118 - INFO - Frame 366 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 17:17:00,390 - INFO - Frame 368 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 17:17:00,605 - INFO - Frame 370 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-24 17:17:00,848 - INFO - Frame 372 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 1
2025-11-24 17:17:01,123 - INFO - Frame 374 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 1
2025-11-24 17:17:01,398 - INFO - Frame 376 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 1
2025-11-24 17:17:01,682 - INFO - Frame 378 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 1
2025-11-24 17:17:01,945 - INFO - Frame 380 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 1
2025-11-24 17:17:02,208 - INFO - Frame 382 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 1
2025-11-24 17:17:02,483 - INFO - Frame 384 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 1
2025-11-24 17:17:02,740 - INFO - Frame 386 | PERCLOS: 0.36 | Yaw: 3.6° | Alerts: 2
2025-11-24 17:17:03,018 - INFO - Frame 388 | PERCLOS: 0.00 | Yaw: 4.1° | Alerts: 1
2025-11-24 17:17:03,291 - INFO - Frame 390 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-24 17:17:03,560 - INFO - Frame 392 | PERCLOS: 0.16 | Yaw: 4.0° | Alerts: 1
2025-11-24 17:17:03,666 - INFO - Frame 394 | PERCLOS: 0.10 | Yaw: 4.1° | Alerts: 1
2025-11-24 17:17:03,772 - INFO - Frame 396 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-24 17:17:03,877 - INFO - Frame 398 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 17:17:04,033 - INFO - Frame 400 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 17:17:04,291 - INFO - Frame 402 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 17:17:04,558 - INFO - Frame 404 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 17:17:04,768 - INFO - Frame 406 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 17:17:05,009 - INFO - Frame 408 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 17:17:05,206 - INFO - Frame 410 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 17:17:05,479 - INFO - Frame 412 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-24 17:17:05,754 - INFO - Frame 414 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 17:17:06,022 - INFO - Frame 416 | PERCLOS: 0.15 | Yaw: 3.8° | Alerts: 1
2025-11-24 17:17:06,296 - INFO - Frame 418 | PERCLOS: 0.17 | Yaw: 4.3° | Alerts: 1
2025-11-24 17:17:06,563 - INFO - Frame 420 | PERCLOS: 0.05 | Yaw: 4.0° | Alerts: 1
2025-11-24 17:17:06,777 - INFO - Frame 422 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 17:17:07,038 - INFO - Frame 424 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 17:17:07,325 - INFO - Frame 426 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 1
2025-11-24 17:17:07,556 - INFO - Frame 428 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-24 17:17:07,801 - INFO - Frame 430 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 1
2025-11-24 17:17:08,072 - INFO - Frame 432 | PERCLOS: 0.00 | Yaw: 4.1° | Alerts: 1
2025-11-24 17:17:08,342 - INFO - Frame 434 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 1
2025-11-24 17:17:08,609 - INFO - Frame 436 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 17:17:08,821 - INFO - Frame 438 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-24 17:17:09,063 - INFO - Frame 440 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 17:17:09,268 - INFO - Frame 442 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 1
2025-11-24 17:17:09,507 - INFO - Frame 444 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 17:17:09,796 - INFO - Frame 446 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 17:17:10,030 - INFO - Frame 448 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 17:17:10,280 - INFO - Frame 450 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 17:17:10,483 - INFO - Frame 452 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 17:17:10,657 - INFO - Frame 454 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 17:17:10,833 - INFO - Frame 456 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 1
2025-11-24 17:17:11,074 - INFO - Frame 458 | PERCLOS: 0.35 | Yaw: 3.8° | Alerts: 2
2025-11-24 17:17:15,994 - INFO - Loading models...
2025-11-24 17:17:16,019 - INFO - ✓ YOLO ONNX loaded
2025-11-24 17:17:16,052 - INFO - ✓ MediaPipe Face Mesh loaded
2025-11-24 17:17:16,655 - INFO - Frame 0 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 17:17:16,926 - INFO - Frame 2 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-24 17:17:17,201 - INFO - Frame 4 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 17:17:17,483 - INFO - Frame 6 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-24 17:17:17,811 - INFO - Frame 8 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 1
2025-11-24 17:17:18,221 - INFO - Frame 10 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-24 17:17:18,658 - INFO - Frame 12 | PERCLOS: 0.00 | Yaw: 4.1° | Alerts: 1
2025-11-24 17:17:18,974 - INFO - Frame 14 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 17:17:19,248 - INFO - Frame 16 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-24 17:17:19,675 - INFO - Frame 18 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 17:17:19,993 - INFO - Frame 20 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 17:17:20,267 - INFO - Frame 22 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 17:17:20,677 - INFO - Frame 24 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 17:17:20,964 - INFO - Frame 26 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 17:17:21,284 - INFO - Frame 28 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-24 17:17:21,584 - INFO - Frame 30 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 17:17:21,878 - INFO - Frame 32 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-24 17:17:22,175 - INFO - Frame 34 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 17:17:22,448 - INFO - Frame 36 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-24 17:17:22,854 - INFO - Frame 38 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 1
2025-11-24 17:17:23,160 - INFO - Frame 40 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 1
2025-11-24 17:17:23,428 - INFO - Frame 42 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 1
2025-11-24 17:17:23,855 - INFO - Frame 44 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 1
2025-11-24 17:17:24,146 - INFO - Frame 46 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 1
2025-11-24 17:17:24,454 - INFO - Frame 48 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 1
2025-11-24 17:17:24,744 - INFO - Frame 50 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 17:17:25,014 - INFO - Frame 52 | PERCLOS: 0.00 | Yaw: 4.7° | Alerts: 1
2025-11-24 17:17:25,304 - INFO - Frame 54 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 1
2025-11-24 17:17:25,598 - INFO - Frame 56 | PERCLOS: 0.20 | Yaw: 5.6° | Alerts: 1
2025-11-24 17:17:25,928 - INFO - Frame 58 | PERCLOS: 0.00 | Yaw: 5.2° | Alerts: 1
2025-11-24 17:17:26,193 - INFO - Frame 60 | PERCLOS: 0.00 | Yaw: 5.4° | Alerts: 1
2025-11-24 17:17:26,497 - INFO - Frame 62 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 1
2025-11-24 17:17:26,799 - INFO - Frame 64 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 17:17:27,091 - INFO - Frame 66 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 1
2025-11-24 17:17:27,359 - INFO - Frame 68 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 1
2025-11-24 17:17:27,672 - INFO - Frame 70 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 1
2025-11-24 17:17:27,946 - INFO - Frame 72 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 1
2025-11-24 17:17:28,411 - INFO - Frame 74 | PERCLOS: 0.14 | Yaw: 4.0° | Alerts: 1
2025-11-24 17:17:28,710 - INFO - Frame 76 | PERCLOS: 0.13 | Yaw: 5.5° | Alerts: 1
2025-11-24 17:17:29,019 - INFO - Frame 78 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 17:17:29,287 - INFO - Frame 80 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-24 17:17:29,581 - INFO - Frame 82 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 17:17:29,854 - INFO - Frame 84 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 17:17:30,157 - INFO - Frame 86 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 1
2025-11-24 17:17:30,426 - INFO - Frame 88 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 17:17:30,846 - INFO - Frame 90 | PERCLOS: 0.00 | Yaw: -0.3° | Alerts: 1
2025-11-24 17:17:31,155 - INFO - Frame 92 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 17:17:31,456 - INFO - Frame 94 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 1
2025-11-24 17:17:31,897 - INFO - Frame 96 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 1
2025-11-24 17:17:32,213 - INFO - Frame 98 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-24 17:17:32,494 - INFO - Frame 100 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 17:17:32,786 - INFO - Frame 102 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 17:17:33,338 - INFO - Frame 104 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 17:17:33,687 - INFO - Frame 106 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 17:17:33,976 - INFO - Frame 108 | PERCLOS: 0.00 | Yaw: 4.9° | Alerts: 1
2025-11-24 17:17:34,381 - INFO - Frame 110 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 1
2025-11-24 17:17:34,690 - INFO - Frame 112 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 1
2025-11-24 17:17:35,075 - INFO - Frame 114 | PERCLOS: 0.00 | Yaw: 5.1° | Alerts: 1
2025-11-24 17:23:08,253 - INFO - Loading models...
2025-11-24 17:23:08,276 - INFO - ✓ YOLO ONNX loaded
2025-11-24 17:23:08,316 - INFO - ✓ MediaPipe Face Mesh loaded
2025-11-24 17:23:08,323 - INFO - ✓ MediaPipe Pose loaded (for smoke & seatbelt)
2025-11-24 17:23:08,333 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:08,341 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:08,493 - INFO - ✓ Camera 0 opened successfully
2025-11-24 17:23:08,554 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:08,554 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:08,746 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:08,746 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:08,923 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:08,924 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:09,109 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:09,113 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:09,295 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:09,297 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:09,316 - INFO - Frame 0 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 0
2025-11-24 17:23:09,485 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:09,485 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:09,681 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:09,681 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:09,888 - INFO - Frame 2 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 0
2025-11-24 17:23:09,898 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:09,898 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:10,102 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:10,104 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:10,300 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:10,301 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:10,315 - INFO - Frame 4 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 0
2025-11-24 17:23:10,497 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:10,499 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:10,686 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:10,691 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:10,874 - INFO - Frame 6 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 0
2025-11-24 17:23:10,881 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:10,881 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:11,069 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:11,069 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:11,277 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:11,278 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:11,468 - INFO - Frame 8 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 0
2025-11-24 17:23:11,473 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:11,473 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:11,678 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:11,681 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:11,926 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:11,930 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:12,130 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:12,133 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:12,147 - INFO - Frame 10 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 0
2025-11-24 17:23:12,327 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:12,332 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:12,525 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:12,527 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:12,727 - INFO - Frame 12 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 0
2025-11-24 17:23:12,730 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:12,731 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:12,919 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:12,922 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:13,122 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:13,123 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:13,323 - INFO - Frame 14 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:23:13,327 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:13,331 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:13,526 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:13,527 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:13,735 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:13,740 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:13,918 - INFO - Frame 16 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 0
2025-11-24 17:23:13,925 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:13,926 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:14,107 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:14,112 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:14,299 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:14,300 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:14,496 - INFO - Frame 18 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 0
2025-11-24 17:23:14,502 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:14,503 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:14,701 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:14,701 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:14,913 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:14,913 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:15,116 - INFO - Frame 20 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 0
2025-11-24 17:23:15,120 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:15,125 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:15,314 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:15,315 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:15,507 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:15,508 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:15,525 - INFO - Frame 22 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 0
2025-11-24 17:23:15,696 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:15,702 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:15,907 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:15,907 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:16,097 - INFO - Frame 24 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 0
2025-11-24 17:23:16,103 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:16,104 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:16,321 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:16,321 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:16,525 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:16,525 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:16,675 - INFO - Frame 26 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 0
2025-11-24 17:23:16,725 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:16,731 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:16,930 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:16,930 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:17,135 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:17,137 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:17,149 - INFO - Frame 28 | PERCLOS: 0.00 | Yaw: 6.5° | Alerts: 0
2025-11-24 17:23:17,340 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:17,341 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:17,564 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:17,567 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:17,765 - INFO - Frame 30 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 0
2025-11-24 17:23:17,767 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:17,767 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:17,959 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:17,960 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:18,169 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:18,169 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:18,375 - INFO - Frame 32 | PERCLOS: 0.00 | Yaw: 5.4° | Alerts: 0
2025-11-24 17:23:18,378 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:18,379 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:18,569 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:18,570 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:18,760 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:18,762 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:18,952 - INFO - Frame 34 | PERCLOS: 0.00 | Yaw: 5.9° | Alerts: 0
2025-11-24 17:23:18,959 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:18,959 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:19,151 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:19,151 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:19,346 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:19,346 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:19,604 - INFO - Frame 36 | PERCLOS: 0.00 | Yaw: 5.9° | Alerts: 0
2025-11-24 17:23:19,607 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:19,609 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:19,799 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:19,802 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:19,999 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:20,000 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:20,197 - INFO - Frame 38 | PERCLOS: 0.00 | Yaw: 6.2° | Alerts: 0
2025-11-24 17:23:20,205 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:20,205 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:20,394 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:20,394 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:20,603 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:20,605 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:20,792 - INFO - Frame 40 | PERCLOS: 0.00 | Yaw: 6.4° | Alerts: 0
2025-11-24 17:23:20,799 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:20,800 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:21,008 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:21,008 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:21,218 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:21,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:21,410 - INFO - Frame 42 | PERCLOS: 0.00 | Yaw: 6.4° | Alerts: 0
2025-11-24 17:23:21,418 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:21,420 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:21,614 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:21,616 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:21,807 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:21,811 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:21,996 - INFO - Frame 44 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 0
2025-11-24 17:23:22,002 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:22,003 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:22,193 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:22,193 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:22,404 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:22,405 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:22,628 - INFO - Frame 46 | PERCLOS: 0.00 | Yaw: 5.1° | Alerts: 0
2025-11-24 17:23:22,636 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:22,636 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:22,819 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:22,820 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:23,017 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:23,017 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:23,209 - INFO - Frame 48 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 0
2025-11-24 17:23:23,213 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:23,213 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:23,413 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:23,415 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:23,606 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:23,611 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:23,625 - INFO - Frame 50 | PERCLOS: 0.00 | Yaw: 5.9° | Alerts: 0
2025-11-24 17:23:23,814 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:23,814 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:24,013 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:24,015 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:24,207 - INFO - Frame 52 | PERCLOS: 0.00 | Yaw: 5.2° | Alerts: 0
2025-11-24 17:23:24,214 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:24,214 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:24,408 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:24,408 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:24,610 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:24,615 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:24,799 - INFO - Frame 54 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 0
2025-11-24 17:23:24,807 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:24,807 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:24,998 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:24,998 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:25,192 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:25,192 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:25,389 - INFO - Frame 56 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 0
2025-11-24 17:23:25,395 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:25,397 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:25,589 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:25,593 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:25,773 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:25,776 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:25,969 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:25,969 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:25,984 - INFO - Frame 58 | PERCLOS: 0.36 | Yaw: 4.4° | Alerts: 1
2025-11-24 17:23:26,164 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:26,165 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:26,361 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:26,362 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:26,559 - INFO - Frame 60 | PERCLOS: 0.27 | Yaw: 4.5° | Alerts: 0
2025-11-24 17:23:26,567 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:26,568 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:26,753 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:26,754 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:23:59,556 - INFO - Loading models...
2025-11-24 17:23:59,576 - INFO - ✓ YOLO ONNX loaded
2025-11-24 17:23:59,615 - INFO - ✓ MediaPipe Face Mesh loaded
2025-11-24 17:23:59,622 - INFO - ✓ MediaPipe Pose loaded (for smoke & seatbelt)
2025-11-24 17:23:59,740 - INFO - ✓ Camera 0 opened successfully
2025-11-24 17:24:00,275 - INFO - Frame 0 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 0
2025-11-24 17:24:00,531 - INFO - Frame 2 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 0
2025-11-24 17:24:00,805 - INFO - Frame 4 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 0
2025-11-24 17:24:01,100 - INFO - Frame 6 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:24:01,390 - INFO - Frame 8 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:24:01,681 - INFO - Frame 10 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:24:01,959 - INFO - Frame 12 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:24:02,246 - INFO - Frame 14 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:24:02,523 - INFO - Frame 16 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:24:02,739 - INFO - Frame 18 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 0
2025-11-24 17:24:03,011 - INFO - Frame 20 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 0
2025-11-24 17:24:03,305 - INFO - Frame 22 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:24:03,521 - INFO - Frame 24 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:24:03,800 - INFO - Frame 26 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 0
2025-11-24 17:24:04,082 - INFO - Frame 28 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 0
2025-11-24 17:24:04,362 - INFO - Frame 30 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 0
2025-11-24 17:24:04,660 - INFO - Frame 32 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 0
2025-11-24 17:24:04,949 - INFO - Frame 34 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:24:05,164 - INFO - Frame 36 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 0
2025-11-24 17:24:05,444 - INFO - Frame 38 | PERCLOS: 0.02 | Yaw: 0.8° | Alerts: 0
2025-11-24 17:24:05,730 - INFO - Frame 40 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 0
2025-11-24 17:24:06,023 - INFO - Frame 42 | PERCLOS: 0.00 | Yaw: 0.2° | Alerts: 0
2025-11-24 17:24:06,313 - INFO - Frame 44 | PERCLOS: 0.39 | Yaw: -0.3° | Alerts: 1
2025-11-24 17:24:06,606 - INFO - Frame 46 | PERCLOS: 0.47 | Yaw: -0.1° | Alerts: 1
2025-11-24 17:24:06,880 - INFO - Frame 48 | PERCLOS: 0.22 | Yaw: 0.4° | Alerts: 0
2025-11-24 17:24:07,165 - INFO - Frame 50 | PERCLOS: 0.56 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:24:07,461 - INFO - Frame 52 | PERCLOS: 0.15 | Yaw: -1.0° | Alerts: 0
2025-11-24 17:24:07,761 - INFO - Frame 54 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 0
2025-11-24 17:24:08,058 - INFO - Frame 56 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 0
2025-11-24 17:24:08,356 - INFO - Frame 58 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 0
2025-11-24 17:24:08,573 - INFO - Frame 60 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 0
2025-11-24 17:24:08,903 - INFO - Frame 62 | PERCLOS: 0.00 | Yaw: -0.3° | Alerts: 0
2025-11-24 17:24:09,175 - INFO - Frame 64 | PERCLOS: 0.00 | Yaw: -0.3° | Alerts: 0
2025-11-24 17:24:09,390 - INFO - Frame 66 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 0
2025-11-24 17:24:09,668 - INFO - Frame 68 | PERCLOS: 0.00 | Yaw: -0.2° | Alerts: 0
2025-11-24 17:24:09,884 - INFO - Frame 70 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 0
2025-11-24 17:24:10,158 - INFO - Frame 72 | PERCLOS: 0.00 | Yaw: -0.0° | Alerts: 0
2025-11-24 17:24:10,456 - INFO - Frame 74 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 0
2025-11-24 17:24:10,757 - INFO - Frame 76 | PERCLOS: 0.00 | Yaw: -0.0° | Alerts: 0
2025-11-24 17:24:11,049 - INFO - Frame 78 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 0
2025-11-24 17:24:11,340 - INFO - Frame 80 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 0
2025-11-24 17:24:11,645 - INFO - Frame 82 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 0
2025-11-24 17:24:11,931 - INFO - Frame 84 | PERCLOS: 0.00 | Yaw: -1.8° | Alerts: 0
2025-11-24 17:24:12,210 - INFO - Frame 86 | PERCLOS: 0.00 | Yaw: -6.6° | Alerts: 0
2025-11-24 17:24:12,420 - INFO - Frame 88 | PERCLOS: 0.00 | Yaw: -6.5° | Alerts: 0
2025-11-24 17:24:12,701 - INFO - Frame 90 | PERCLOS: 0.00 | Yaw: -3.9° | Alerts: 0
2025-11-24 17:24:12,994 - INFO - Frame 92 | PERCLOS: 0.00 | Yaw: -2.4° | Alerts: 0
2025-11-24 17:24:13,270 - INFO - Frame 94 | PERCLOS: 0.00 | Yaw: -1.3° | Alerts: 0
2025-11-24 17:24:13,472 - INFO - Frame 96 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 0
2025-11-24 17:24:13,746 - INFO - Frame 98 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 0
2025-11-24 17:24:14,028 - INFO - Frame 100 | PERCLOS: 0.00 | Yaw: -0.8° | Alerts: 0
2025-11-24 17:24:14,230 - INFO - Frame 102 | PERCLOS: 0.00 | Yaw: -0.8° | Alerts: 0
2025-11-24 17:24:14,510 - INFO - Frame 104 | PERCLOS: 0.00 | Yaw: -0.0° | Alerts: 0
2025-11-24 17:24:14,810 - INFO - Frame 106 | PERCLOS: 0.11 | Yaw: 3.0° | Alerts: 0
2025-11-24 17:24:15,022 - INFO - Frame 108 | PERCLOS: 0.00 | Yaw: 4.8° | Alerts: 0
2025-11-24 17:24:15,294 - INFO - Frame 110 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 0
2025-11-24 17:24:15,590 - INFO - Frame 112 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 0
2025-11-24 17:24:15,880 - INFO - Frame 114 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 0
2025-11-24 17:24:16,161 - INFO - Frame 116 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 0
2025-11-24 17:24:16,462 - INFO - Frame 118 | PERCLOS: 0.00 | Yaw: 5.4° | Alerts: 0
2025-11-24 17:24:16,758 - INFO - Frame 120 | PERCLOS: 0.00 | Yaw: 8.3° | Alerts: 0
2025-11-24 17:24:17,037 - INFO - Frame 122 | PERCLOS: 0.00 | Yaw: 12.4° | Alerts: 0
2025-11-24 17:24:17,311 - INFO - Frame 124 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:24:17,592 - INFO - Frame 126 | PERCLOS: 0.00 | Yaw: 11.2° | Alerts: 0
2025-11-24 17:24:17,878 - INFO - Frame 128 | PERCLOS: 0.00 | Yaw: 10.7° | Alerts: 0
2025-11-24 17:24:18,154 - INFO - Frame 130 | PERCLOS: 0.00 | Yaw: 10.1° | Alerts: 0
2025-11-24 17:24:18,426 - INFO - Frame 132 | PERCLOS: 0.00 | Yaw: 9.5° | Alerts: 0
2025-11-24 17:24:18,629 - INFO - Frame 134 | PERCLOS: 0.00 | Yaw: 10.9° | Alerts: 0
2025-11-24 17:24:18,909 - INFO - Frame 136 | PERCLOS: 0.00 | Yaw: 6.5° | Alerts: 0
2025-11-24 17:24:19,267 - INFO - Frame 138 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 0
2025-11-24 17:24:19,565 - INFO - Frame 140 | PERCLOS: 0.00 | Yaw: 5.1° | Alerts: 0
2025-11-24 17:24:19,865 - INFO - Frame 142 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 0
2025-11-24 17:24:20,145 - INFO - Frame 144 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 0
2025-11-24 17:24:20,442 - INFO - Frame 146 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 0
2025-11-24 17:24:20,736 - INFO - Frame 148 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 0
2025-11-24 17:24:21,032 - INFO - Frame 150 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 0
2025-11-24 17:24:21,332 - INFO - Frame 152 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 1
2025-11-24 17:24:21,626 - INFO - Frame 154 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-24 17:24:21,930 - INFO - Frame 156 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 1
2025-11-24 17:24:22,205 - INFO - Frame 158 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 1
2025-11-24 17:24:22,535 - INFO - Frame 160 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 0
2025-11-24 17:24:22,830 - INFO - Frame 162 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 0
2025-11-24 17:24:23,111 - INFO - Frame 164 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 0
2025-11-24 17:24:23,319 - INFO - Frame 166 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 0
2025-11-24 17:24:23,579 - INFO - Frame 168 | PERCLOS: 0.00 | Yaw: -0.2° | Alerts: 0
2025-11-24 17:24:23,857 - INFO - Frame 170 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 0
2025-11-24 17:24:24,140 - INFO - Frame 172 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 0
2025-11-24 17:24:24,358 - INFO - Frame 174 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 0
2025-11-24 17:24:24,634 - INFO - Frame 176 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 0
2025-11-24 17:24:24,924 - INFO - Frame 178 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 0
2025-11-24 17:24:25,216 - INFO - Frame 180 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 0
2025-11-24 17:24:25,495 - INFO - Frame 182 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 0
2025-11-24 17:24:25,773 - INFO - Frame 184 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 0
2025-11-24 17:24:25,976 - INFO - Frame 186 | PERCLOS: 0.00 | Yaw: -0.9° | Alerts: 0
2025-11-24 17:24:26,250 - INFO - Frame 188 | PERCLOS: 0.00 | Yaw: -3.9° | Alerts: 0
2025-11-24 17:24:26,532 - INFO - Frame 190 | PERCLOS: 0.00 | Yaw: -6.1° | Alerts: 0
2025-11-24 17:24:26,827 - INFO - Frame 192 | PERCLOS: 0.00 | Yaw: -6.3° | Alerts: 0
2025-11-24 17:24:27,120 - INFO - Frame 194 | PERCLOS: 0.00 | Yaw: -6.2° | Alerts: 0
2025-11-24 17:24:27,411 - INFO - Frame 196 | PERCLOS: 0.00 | Yaw: -6.0° | Alerts: 0
2025-11-24 17:24:27,711 - INFO - Frame 198 | PERCLOS: 0.00 | Yaw: -5.6° | Alerts: 0
2025-11-24 17:24:28,010 - INFO - Frame 200 | PERCLOS: 0.00 | Yaw: -3.6° | Alerts: 0
2025-11-24 17:24:28,289 - INFO - Frame 202 | PERCLOS: 0.00 | Yaw: -2.8° | Alerts: 0
2025-11-24 17:24:28,508 - INFO - Frame 204 | PERCLOS: 0.00 | Yaw: -2.3° | Alerts: 0
2025-11-24 17:24:28,786 - INFO - Frame 206 | PERCLOS: 0.00 | Yaw: -1.9° | Alerts: 0
2025-11-24 17:24:29,064 - INFO - Frame 208 | PERCLOS: 0.00 | Yaw: -2.1° | Alerts: 0
2025-11-24 17:24:29,362 - INFO - Frame 210 | PERCLOS: 0.00 | Yaw: -2.5° | Alerts: 0
2025-11-24 17:24:29,662 - INFO - Frame 212 | PERCLOS: 0.00 | Yaw: -2.8° | Alerts: 0
2025-11-24 17:24:29,874 - INFO - Frame 214 | PERCLOS: 0.00 | Yaw: -2.7° | Alerts: 0
2025-11-24 17:24:30,129 - INFO - Frame 216 | PERCLOS: 0.00 | Yaw: -2.3° | Alerts: 0
2025-11-24 17:24:30,407 - INFO - Frame 218 | PERCLOS: 0.00 | Yaw: -2.2° | Alerts: 0
2025-11-24 17:24:30,681 - INFO - Frame 220 | PERCLOS: 0.00 | Yaw: -2.1° | Alerts: 0
2025-11-24 17:24:30,966 - INFO - Frame 222 | PERCLOS: 0.00 | Yaw: -2.0° | Alerts: 0
2025-11-24 17:24:31,262 - INFO - Frame 224 | PERCLOS: 0.00 | Yaw: -1.5° | Alerts: 0
2025-11-24 17:24:31,555 - INFO - Frame 226 | PERCLOS: 0.00 | Yaw: -1.3° | Alerts: 0
2025-11-24 17:24:31,845 - INFO - Frame 228 | PERCLOS: 0.00 | Yaw: -1.4° | Alerts: 0
2025-11-24 17:24:32,138 - INFO - Frame 230 | PERCLOS: 0.00 | Yaw: -1.7° | Alerts: 0
2025-11-24 17:24:32,436 - INFO - Frame 232 | PERCLOS: 0.00 | Yaw: -1.5° | Alerts: 0
2025-11-24 17:24:32,655 - INFO - Frame 234 | PERCLOS: 0.00 | Yaw: -1.4° | Alerts: 0
2025-11-24 17:24:32,930 - INFO - Frame 236 | PERCLOS: 0.00 | Yaw: -1.2° | Alerts: 0
2025-11-24 17:24:33,228 - INFO - Frame 238 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 0
2025-11-24 17:24:33,528 - INFO - Frame 240 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 0
2025-11-24 17:24:33,800 - INFO - Frame 242 | PERCLOS: 0.00 | Yaw: -0.8° | Alerts: 0
2025-11-24 17:24:34,082 - INFO - Frame 244 | PERCLOS: 0.37 | Yaw: -0.7° | Alerts: 1
2025-11-24 17:24:34,377 - INFO - Frame 246 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 0
2025-11-24 17:24:34,675 - INFO - Frame 248 | PERCLOS: 0.00 | Yaw: -1.6° | Alerts: 0
2025-11-24 17:24:34,892 - INFO - Frame 250 | PERCLOS: 0.00 | Yaw: -1.5° | Alerts: 0
2025-11-24 17:24:35,172 - INFO - Frame 252 | PERCLOS: 0.00 | Yaw: -1.5° | Alerts: 0
2025-11-24 17:24:35,466 - INFO - Frame 254 | PERCLOS: 0.00 | Yaw: -1.7° | Alerts: 0
2025-11-24 17:24:35,761 - INFO - Frame 256 | PERCLOS: 0.00 | Yaw: -0.8° | Alerts: 0
2025-11-24 17:24:36,058 - INFO - Frame 258 | PERCLOS: 0.00 | Yaw: -0.2° | Alerts: 0
2025-11-24 17:24:36,351 - INFO - Frame 260 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 0
2025-11-24 17:24:36,634 - INFO - Frame 262 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 0
2025-11-24 17:24:36,924 - INFO - Frame 264 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 0
2025-11-24 17:24:37,225 - INFO - Frame 266 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 0
2025-11-24 17:24:37,521 - INFO - Frame 268 | PERCLOS: 0.00 | Yaw: 4.7° | Alerts: 0
2025-11-24 17:24:37,819 - INFO - Frame 270 | PERCLOS: 0.00 | Yaw: 6.2° | Alerts: 0
2025-11-24 17:24:38,112 - INFO - Frame 272 | PERCLOS: 0.04 | Yaw: 4.2° | Alerts: 0
2025-11-24 17:24:38,407 - INFO - Frame 274 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:24:38,703 - INFO - Frame 276 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:24:38,994 - INFO - Frame 278 | PERCLOS: 0.00 | Yaw: 0.2° | Alerts: 0
2025-11-24 17:24:39,283 - INFO - Frame 280 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 0
2025-11-24 17:24:39,577 - INFO - Frame 282 | PERCLOS: 0.00 | Yaw: -0.9° | Alerts: 0
2025-11-24 17:24:39,855 - INFO - Frame 284 | PERCLOS: 0.00 | Yaw: -0.0° | Alerts: 0
2025-11-24 17:24:40,144 - INFO - Frame 286 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:24:40,431 - INFO - Frame 288 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 0
2025-11-24 17:24:40,722 - INFO - Frame 290 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 0
2025-11-24 17:24:40,947 - INFO - Frame 292 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:24:41,214 - INFO - Frame 294 | PERCLOS: 0.00 | Yaw: 10.0° | Alerts: 0
2025-11-24 17:24:41,503 - INFO - Frame 296 | PERCLOS: 0.00 | Yaw: 10.5° | Alerts: 0
2025-11-24 17:24:41,796 - INFO - Frame 298 | PERCLOS: 0.00 | Yaw: 10.2° | Alerts: 0
2025-11-24 17:24:42,094 - INFO - Frame 300 | PERCLOS: 0.00 | Yaw: 8.2° | Alerts: 0
2025-11-24 17:24:42,394 - INFO - Frame 302 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 0
2025-11-24 17:24:42,695 - INFO - Frame 304 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:24:42,996 - INFO - Frame 306 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 0
2025-11-24 17:24:43,293 - INFO - Frame 308 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 0
2025-11-24 17:24:43,591 - INFO - Frame 310 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 0
2025-11-24 17:24:43,811 - INFO - Frame 312 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 0
2025-11-24 17:24:44,093 - INFO - Frame 314 | PERCLOS: 0.00 | Yaw: 0.2° | Alerts: 0
2025-11-24 17:24:44,383 - INFO - Frame 316 | PERCLOS: 0.00 | Yaw: 0.2° | Alerts: 0
2025-11-24 17:24:44,668 - INFO - Frame 318 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 0
2025-11-24 17:24:44,949 - INFO - Frame 320 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 0
2025-11-24 17:24:45,157 - INFO - Frame 322 | PERCLOS: 0.03 | Yaw: -6.1° | Alerts: 0
2025-11-24 17:24:45,413 - INFO - Frame 324 | PERCLOS: 0.00 | Yaw: -8.3° | Alerts: 0
2025-11-24 17:24:45,705 - INFO - Frame 326 | PERCLOS: 0.00 | Yaw: -8.0° | Alerts: 0
2025-11-24 17:24:45,978 - INFO - Frame 328 | PERCLOS: 0.00 | Yaw: -7.3° | Alerts: 0
2025-11-24 17:24:46,193 - INFO - Frame 330 | PERCLOS: 0.00 | Yaw: -6.6° | Alerts: 0
2025-11-24 17:24:46,476 - INFO - Frame 332 | PERCLOS: 0.00 | Yaw: -6.9° | Alerts: 0
2025-11-24 17:24:46,770 - INFO - Frame 334 | PERCLOS: 0.00 | Yaw: -6.7° | Alerts: 0
2025-11-24 17:24:47,053 - INFO - Frame 336 | PERCLOS: 0.00 | Yaw: -6.5° | Alerts: 0
2025-11-24 17:24:47,351 - INFO - Frame 338 | PERCLOS: 0.00 | Yaw: -6.4° | Alerts: 0
2025-11-24 17:24:47,627 - INFO - Frame 340 | PERCLOS: 0.00 | Yaw: -4.5° | Alerts: 0
2025-11-24 17:24:47,907 - INFO - Frame 342 | PERCLOS: 0.00 | Yaw: -3.6° | Alerts: 0
2025-11-24 17:24:48,207 - INFO - Frame 344 | PERCLOS: 0.00 | Yaw: -3.1° | Alerts: 0
2025-11-24 17:24:48,511 - INFO - Frame 346 | PERCLOS: 0.00 | Yaw: -3.1° | Alerts: 0
2025-11-24 17:24:48,797 - INFO - Frame 348 | PERCLOS: 0.00 | Yaw: -2.9° | Alerts: 0
2025-11-24 17:24:49,091 - INFO - Frame 350 | PERCLOS: 0.00 | Yaw: -3.1° | Alerts: 0
2025-11-24 17:24:49,300 - INFO - Frame 352 | PERCLOS: 0.00 | Yaw: -3.4° | Alerts: 0
2025-11-24 17:24:49,573 - INFO - Frame 354 | PERCLOS: 0.00 | Yaw: -2.4° | Alerts: 0
2025-11-24 17:24:49,770 - INFO - Frame 356 | PERCLOS: 0.00 | Yaw: -1.5° | Alerts: 0
2025-11-24 17:24:50,036 - INFO - Frame 358 | PERCLOS: 0.00 | Yaw: -0.9° | Alerts: 0
2025-11-24 17:24:50,310 - INFO - Frame 360 | PERCLOS: 0.00 | Yaw: -0.0° | Alerts: 0
2025-11-24 17:24:50,587 - INFO - Frame 362 | PERCLOS: 0.00 | Yaw: -0.2° | Alerts: 0
2025-11-24 17:24:50,790 - INFO - Frame 364 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 0
2025-11-24 17:24:51,053 - INFO - Frame 366 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 0
2025-11-24 17:24:51,334 - INFO - Frame 368 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 0
2025-11-24 17:24:51,630 - INFO - Frame 370 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:24:51,945 - INFO - Frame 372 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:24:52,244 - INFO - Frame 374 | PERCLOS: 0.00 | Yaw: -0.8° | Alerts: 0
2025-11-24 17:24:52,541 - INFO - Frame 376 | PERCLOS: 0.00 | Yaw: -2.1° | Alerts: 0
2025-11-24 17:24:52,840 - INFO - Frame 378 | PERCLOS: 0.00 | Yaw: -2.6° | Alerts: 0
2025-11-24 17:24:53,129 - INFO - Frame 380 | PERCLOS: 0.00 | Yaw: -2.2° | Alerts: 0
2025-11-24 17:24:53,427 - INFO - Frame 382 | PERCLOS: 0.00 | Yaw: -2.1° | Alerts: 0
2025-11-24 17:24:53,721 - INFO - Frame 384 | PERCLOS: 0.00 | Yaw: -2.4° | Alerts: 0
2025-11-24 17:24:54,016 - INFO - Frame 386 | PERCLOS: 0.00 | Yaw: -2.2° | Alerts: 0
2025-11-24 17:24:54,308 - INFO - Frame 388 | PERCLOS: 0.00 | Yaw: -2.4° | Alerts: 0
2025-11-24 17:24:54,593 - INFO - Frame 390 | PERCLOS: 0.00 | Yaw: -2.3° | Alerts: 0
2025-11-24 17:24:54,892 - INFO - Frame 392 | PERCLOS: 0.00 | Yaw: -2.4° | Alerts: 0
2025-11-24 17:24:55,181 - INFO - Frame 394 | PERCLOS: 0.00 | Yaw: -2.3° | Alerts: 0
2025-11-24 17:24:55,401 - INFO - Frame 396 | PERCLOS: 0.00 | Yaw: -1.7° | Alerts: 0
2025-11-24 17:24:55,658 - INFO - Frame 398 | PERCLOS: 0.00 | Yaw: -1.4° | Alerts: 0
2025-11-24 17:24:55,931 - INFO - Frame 400 | PERCLOS: 0.00 | Yaw: -0.9° | Alerts: 0
2025-11-24 17:24:56,143 - INFO - Frame 402 | PERCLOS: 0.00 | Yaw: -1.2° | Alerts: 0
2025-11-24 17:24:56,419 - INFO - Frame 404 | PERCLOS: 0.00 | Yaw: -1.9° | Alerts: 0
2025-11-24 17:24:56,718 - INFO - Frame 406 | PERCLOS: 0.08 | Yaw: -2.3° | Alerts: 0
2025-11-24 17:24:57,014 - INFO - Frame 408 | PERCLOS: 0.00 | Yaw: -2.2° | Alerts: 0
2025-11-24 17:24:57,311 - INFO - Frame 410 | PERCLOS: 0.00 | Yaw: -2.5° | Alerts: 0
2025-11-24 17:24:57,608 - INFO - Frame 412 | PERCLOS: 0.00 | Yaw: -2.1° | Alerts: 0
2025-11-24 17:24:57,900 - INFO - Frame 414 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 0
2025-11-24 17:24:58,198 - INFO - Frame 416 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:24:58,493 - INFO - Frame 418 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 0
2025-11-24 17:24:58,793 - INFO - Frame 420 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 0
2025-11-24 17:24:59,003 - INFO - Frame 422 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:24:59,277 - INFO - Frame 424 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 0
2025-11-24 17:24:59,578 - INFO - Frame 426 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:24:59,872 - INFO - Frame 428 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 0
2025-11-24 17:25:00,162 - INFO - Frame 430 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 0
2025-11-24 17:25:00,376 - INFO - Frame 432 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 0
2025-11-24 17:25:00,648 - INFO - Frame 434 | PERCLOS: 0.00 | Yaw: -0.2° | Alerts: 0
2025-11-24 17:25:00,927 - INFO - Frame 436 | PERCLOS: 0.00 | Yaw: -0.3° | Alerts: 0
2025-11-24 17:25:01,204 - INFO - Frame 438 | PERCLOS: 0.00 | Yaw: -0.2° | Alerts: 0
2025-11-24 17:25:01,490 - INFO - Frame 440 | PERCLOS: 0.00 | Yaw: -0.3° | Alerts: 0
2025-11-24 17:25:01,777 - INFO - Frame 442 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 0
2025-11-24 17:25:02,066 - INFO - Frame 444 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 0
2025-11-24 17:25:02,341 - INFO - Frame 446 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 0
2025-11-24 17:25:02,620 - INFO - Frame 448 | PERCLOS: 0.00 | Yaw: -0.9° | Alerts: 0
2025-11-24 17:25:02,921 - INFO - Frame 450 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 0
2025-11-24 17:25:03,138 - INFO - Frame 452 | PERCLOS: 0.00 | Yaw: -0.8° | Alerts: 0
2025-11-24 17:25:03,416 - INFO - Frame 454 | PERCLOS: 0.00 | Yaw: -1.1° | Alerts: 0
2025-11-24 17:25:03,706 - INFO - Frame 456 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 0
2025-11-24 17:25:04,004 - INFO - Frame 458 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 0
2025-11-24 17:25:04,218 - INFO - Frame 460 | PERCLOS: 0.00 | Yaw: -1.1° | Alerts: 0
2025-11-24 17:25:04,487 - INFO - Frame 462 | PERCLOS: 0.00 | Yaw: -1.2° | Alerts: 0
2025-11-24 17:25:04,766 - INFO - Frame 464 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 0
2025-11-24 17:25:05,058 - INFO - Frame 466 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 0
2025-11-24 17:25:05,354 - INFO - Frame 468 | PERCLOS: 0.00 | Yaw: -1.1° | Alerts: 0
2025-11-24 17:25:05,652 - INFO - Frame 470 | PERCLOS: 0.00 | Yaw: -4.7° | Alerts: 0
2025-11-24 17:25:05,855 - INFO - Frame 472 | PERCLOS: 0.00 | Yaw: -6.1° | Alerts: 0
2025-11-24 17:25:06,131 - INFO - Frame 474 | PERCLOS: 0.00 | Yaw: -5.2° | Alerts: 0
2025-11-24 17:25:06,432 - INFO - Frame 476 | PERCLOS: 0.00 | Yaw: -4.8° | Alerts: 0
2025-11-24 17:25:06,729 - INFO - Frame 478 | PERCLOS: 0.00 | Yaw: -4.9° | Alerts: 0
2025-11-24 17:25:07,028 - INFO - Frame 480 | PERCLOS: 0.00 | Yaw: -3.4° | Alerts: 0
2025-11-24 17:25:07,318 - INFO - Frame 482 | PERCLOS: 0.00 | Yaw: -2.3° | Alerts: 0
2025-11-24 17:25:07,618 - INFO - Frame 484 | PERCLOS: 0.00 | Yaw: -1.2° | Alerts: 0
2025-11-24 17:25:07,904 - INFO - Frame 486 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 0
2025-11-24 17:25:08,191 - INFO - Frame 488 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 0
2025-11-24 17:25:08,475 - INFO - Frame 490 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 0
2025-11-24 17:25:08,688 - INFO - Frame 492 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 0
2025-11-24 17:25:08,954 - INFO - Frame 494 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 0
2025-11-24 17:25:09,247 - INFO - Frame 496 | PERCLOS: 0.00 | Yaw: -1.1° | Alerts: 0
2025-11-24 17:25:09,462 - INFO - Frame 498 | PERCLOS: 0.00 | Yaw: -1.2° | Alerts: 0
2025-11-24 17:25:09,738 - INFO - Frame 500 | PERCLOS: 0.00 | Yaw: -1.2° | Alerts: 0
2025-11-24 17:25:09,952 - INFO - Frame 502 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 0
2025-11-24 17:25:10,230 - INFO - Frame 504 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 0
2025-11-24 17:25:10,525 - INFO - Frame 506 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 0
2025-11-24 17:25:10,739 - INFO - Frame 508 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 0
2025-11-24 17:25:11,020 - INFO - Frame 510 | PERCLOS: 0.00 | Yaw: -1.2° | Alerts: 0
2025-11-24 17:25:11,239 - INFO - Frame 512 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 0
2025-11-24 17:25:11,514 - INFO - Frame 514 | PERCLOS: 0.00 | Yaw: -1.2° | Alerts: 0
2025-11-24 17:25:11,812 - INFO - Frame 516 | PERCLOS: 0.00 | Yaw: -1.2° | Alerts: 0
2025-11-24 17:25:12,095 - INFO - Frame 518 | PERCLOS: 0.00 | Yaw: -1.3° | Alerts: 0
2025-11-24 17:25:12,396 - INFO - Frame 520 | PERCLOS: 0.09 | Yaw: -0.9° | Alerts: 0
2025-11-24 17:25:12,602 - INFO - Frame 522 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 0
2025-11-24 17:25:12,863 - INFO - Frame 524 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 0
2025-11-24 17:25:13,144 - INFO - Frame 526 | PERCLOS: 0.00 | Yaw: -0.0° | Alerts: 0
2025-11-24 17:25:13,351 - INFO - Frame 528 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 0
2025-11-24 17:25:13,624 - INFO - Frame 530 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:25:13,922 - INFO - Frame 532 | PERCLOS: 0.21 | Yaw: 1.7° | Alerts: 0
2025-11-24 17:25:14,204 - INFO - Frame 534 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 0
2025-11-24 17:25:14,408 - INFO - Frame 536 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 0
2025-11-24 17:25:14,663 - INFO - Frame 538 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 0
2025-11-24 17:25:14,947 - INFO - Frame 540 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 0
2025-11-24 17:25:15,234 - INFO - Frame 542 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 0
2025-11-24 17:25:15,522 - INFO - Frame 544 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 0
2025-11-24 17:25:15,816 - INFO - Frame 546 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 0
2025-11-24 17:25:16,111 - INFO - Frame 548 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 0
2025-11-24 17:25:16,404 - INFO - Frame 550 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 0
2025-11-24 17:25:16,695 - INFO - Frame 552 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 0
2025-11-24 17:25:16,913 - INFO - Frame 554 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 0
2025-11-24 17:25:17,192 - INFO - Frame 556 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 0
2025-11-24 17:25:17,477 - INFO - Frame 558 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 0
2025-11-24 17:25:17,773 - INFO - Frame 560 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 0
2025-11-24 17:25:18,058 - INFO - Frame 562 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 0
2025-11-24 17:25:18,350 - INFO - Frame 564 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 0
2025-11-24 17:25:18,636 - INFO - Frame 566 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 0
2025-11-24 17:25:18,926 - INFO - Frame 568 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 0
2025-11-24 17:25:19,222 - INFO - Frame 570 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 0
2025-11-24 17:25:19,578 - INFO - Frame 572 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 0
2025-11-24 17:25:19,853 - INFO - Frame 574 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 0
2025-11-24 17:25:20,129 - INFO - Frame 576 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 0
2025-11-24 17:25:20,426 - INFO - Frame 578 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 0
2025-11-24 17:25:20,642 - INFO - Frame 580 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:25:20,923 - INFO - Frame 582 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:25:21,221 - INFO - Frame 584 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 0
2025-11-24 17:25:21,498 - INFO - Frame 586 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:25:21,773 - INFO - Frame 588 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 0
2025-11-24 17:25:22,072 - INFO - Frame 590 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 0
2025-11-24 17:25:22,284 - INFO - Frame 592 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:25:22,549 - INFO - Frame 594 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:25:22,845 - INFO - Frame 596 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:25:23,143 - INFO - Frame 598 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 0
2025-11-24 17:25:23,432 - INFO - Frame 600 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 0
2025-11-24 17:25:23,725 - INFO - Frame 602 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 0
2025-11-24 17:25:24,025 - INFO - Frame 604 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 0
2025-11-24 17:25:24,316 - INFO - Frame 606 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 0
2025-11-24 17:25:24,523 - INFO - Frame 608 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:25:24,798 - INFO - Frame 610 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:25:25,077 - INFO - Frame 612 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:25:25,374 - INFO - Frame 614 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:25:25,673 - INFO - Frame 616 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:25:25,965 - INFO - Frame 618 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 0
2025-11-24 17:25:26,261 - INFO - Frame 620 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 0
2025-11-24 17:25:26,554 - INFO - Frame 622 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:25:26,836 - INFO - Frame 624 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:25:27,128 - INFO - Frame 626 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:25:27,411 - INFO - Frame 628 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:25:27,615 - INFO - Frame 630 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:25:27,890 - INFO - Frame 632 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:25:28,190 - INFO - Frame 634 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 0
2025-11-24 17:25:28,485 - INFO - Frame 636 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:25:28,783 - INFO - Frame 638 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:25:29,081 - INFO - Frame 640 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 0
2025-11-24 17:25:29,363 - INFO - Frame 642 | PERCLOS: 0.01 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:25:29,653 - INFO - Frame 644 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:25:29,937 - INFO - Frame 646 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 0
2025-11-24 17:25:30,228 - INFO - Frame 648 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 0
2025-11-24 17:25:30,526 - INFO - Frame 650 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:25:30,812 - INFO - Frame 652 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:25:31,090 - INFO - Frame 654 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:25:31,367 - INFO - Frame 656 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:25:31,591 - INFO - Frame 658 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 0
2025-11-24 17:25:31,863 - INFO - Frame 660 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:25:32,144 - INFO - Frame 662 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:25:32,426 - INFO - Frame 664 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:25:32,726 - INFO - Frame 666 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 0
2025-11-24 17:25:33,024 - INFO - Frame 668 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 0
2025-11-24 17:25:33,325 - INFO - Frame 670 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 0
2025-11-24 17:25:33,619 - INFO - Frame 672 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 0
2025-11-24 17:25:33,919 - INFO - Frame 674 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 0
2025-11-24 17:25:34,216 - INFO - Frame 676 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:25:34,503 - INFO - Frame 678 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 0
2025-11-24 17:25:34,798 - INFO - Frame 680 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:25:35,094 - INFO - Frame 682 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:25:35,387 - INFO - Frame 684 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:25:35,606 - INFO - Frame 686 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 0
2025-11-24 17:25:35,882 - INFO - Frame 688 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 0
2025-11-24 17:25:36,161 - INFO - Frame 690 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 0
2025-11-24 17:25:36,462 - INFO - Frame 692 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:25:36,751 - INFO - Frame 694 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 0
2025-11-24 17:25:37,027 - INFO - Frame 696 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 0
2025-11-24 17:25:37,309 - INFO - Frame 698 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:25:37,522 - INFO - Frame 700 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 0
2025-11-24 17:25:37,794 - INFO - Frame 702 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 0
2025-11-24 17:25:38,082 - INFO - Frame 704 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 0
2025-11-24 17:25:38,378 - INFO - Frame 706 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 0
2025-11-24 17:25:38,682 - INFO - Frame 708 | PERCLOS: 0.00 | Yaw: 5.4° | Alerts: 0
2025-11-24 17:25:38,965 - INFO - Frame 710 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 0
2025-11-24 17:25:39,178 - INFO - Frame 712 | PERCLOS: 0.00 | Yaw: 6.7° | Alerts: 0
2025-11-24 17:25:39,446 - INFO - Frame 714 | PERCLOS: 0.00 | Yaw: 7.2° | Alerts: 0
2025-11-24 17:25:39,722 - INFO - Frame 716 | PERCLOS: 0.00 | Yaw: 7.2° | Alerts: 0
2025-11-24 17:25:40,013 - INFO - Frame 718 | PERCLOS: 0.00 | Yaw: 6.5° | Alerts: 0
2025-11-24 17:25:40,298 - INFO - Frame 720 | PERCLOS: 0.00 | Yaw: 6.9° | Alerts: 0
2025-11-24 17:25:40,508 - INFO - Frame 722 | PERCLOS: 0.00 | Yaw: 7.1° | Alerts: 0
2025-11-24 17:25:40,787 - INFO - Frame 724 | PERCLOS: 0.00 | Yaw: 7.1° | Alerts: 0
2025-11-24 17:25:41,058 - INFO - Frame 726 | PERCLOS: 0.00 | Yaw: 7.6° | Alerts: 0
2025-11-24 17:25:41,350 - INFO - Frame 728 | PERCLOS: 0.00 | Yaw: 7.6° | Alerts: 0
2025-11-24 17:25:41,622 - INFO - Frame 730 | PERCLOS: 0.00 | Yaw: 7.4° | Alerts: 0
2025-11-24 17:25:41,900 - INFO - Frame 732 | PERCLOS: 0.00 | Yaw: 7.3° | Alerts: 0
2025-11-24 17:25:42,181 - INFO - Frame 734 | PERCLOS: 0.00 | Yaw: 7.0° | Alerts: 0
2025-11-24 17:25:42,462 - INFO - Frame 736 | PERCLOS: 0.00 | Yaw: 6.6° | Alerts: 0
2025-11-24 17:25:42,741 - INFO - Frame 738 | PERCLOS: 0.00 | Yaw: 6.1° | Alerts: 0
2025-11-24 17:25:42,962 - INFO - Frame 740 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 0
2025-11-24 17:25:43,239 - INFO - Frame 742 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 0
2025-11-24 17:25:43,545 - INFO - Frame 744 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 0
2025-11-24 17:25:43,872 - INFO - Frame 746 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 0
2025-11-24 17:25:44,143 - INFO - Frame 748 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 0
2025-11-24 17:25:44,420 - INFO - Frame 750 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 0
2025-11-24 17:25:44,719 - INFO - Frame 752 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 0
2025-11-24 17:25:45,002 - INFO - Frame 754 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 0
2025-11-24 17:25:45,206 - INFO - Frame 756 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 0
2025-11-24 17:25:45,469 - INFO - Frame 758 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 0
2025-11-24 17:25:45,760 - INFO - Frame 760 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 0
2025-11-24 17:25:46,060 - INFO - Frame 762 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 0
2025-11-24 17:25:46,371 - INFO - Frame 764 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 0
2025-11-24 17:25:46,659 - INFO - Frame 766 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 0
2025-11-24 17:25:46,950 - INFO - Frame 768 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 0
2025-11-24 17:25:47,247 - INFO - Frame 770 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 0
2025-11-24 17:25:47,552 - INFO - Frame 772 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 0
2025-11-24 17:25:47,840 - INFO - Frame 774 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 0
2025-11-24 17:25:48,135 - INFO - Frame 776 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 0
2025-11-24 17:25:48,430 - INFO - Frame 778 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 0
2025-11-24 17:25:48,716 - INFO - Frame 780 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 0
2025-11-24 17:25:49,011 - INFO - Frame 782 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 0
2025-11-24 17:25:49,308 - INFO - Frame 784 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 0
2025-11-24 17:25:49,525 - INFO - Frame 786 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 0
2025-11-24 17:25:49,797 - INFO - Frame 788 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 0
2025-11-24 17:25:50,074 - INFO - Frame 790 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 0
2025-11-24 17:25:50,365 - INFO - Frame 792 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 0
2025-11-24 17:25:50,660 - INFO - Frame 794 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 0
2025-11-24 17:25:50,944 - INFO - Frame 796 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 0
2025-11-24 17:25:51,229 - INFO - Frame 798 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 0
2025-11-24 17:25:51,536 - INFO - Frame 800 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 0
2025-11-24 17:25:51,832 - INFO - Frame 802 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 0
2025-11-24 17:25:52,125 - INFO - Frame 804 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 0
2025-11-24 17:25:52,423 - INFO - Frame 806 | PERCLOS: 0.23 | Yaw: 3.7° | Alerts: 0
2025-11-24 17:25:52,726 - INFO - Frame 808 | PERCLOS: 0.00 | Yaw: 6.2° | Alerts: 0
2025-11-24 17:25:53,023 - INFO - Frame 810 | PERCLOS: 0.00 | Yaw: 6.9° | Alerts: 0
2025-11-24 17:25:53,212 - INFO - Frame 812 | PERCLOS: 0.00 | Yaw: 7.3° | Alerts: 0
2025-11-24 17:25:53,367 - INFO - Frame 814 | PERCLOS: 0.00 | Yaw: 6.9° | Alerts: 0
2025-11-24 17:25:53,475 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:53,572 - INFO - Frame 816 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 0
2025-11-24 17:25:53,574 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:53,669 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:53,763 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:53,852 - INFO - Frame 818 | PERCLOS: 0.00 | Yaw: 5.4° | Alerts: 0
2025-11-24 17:25:53,855 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:53,945 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:54,038 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:54,136 - INFO - Frame 820 | PERCLOS: 0.00 | Yaw: 5.2° | Alerts: 0
2025-11-24 17:25:54,139 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:54,235 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:54,341 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:54,434 - INFO - Frame 822 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 0
2025-11-24 17:25:54,436 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:54,536 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:54,639 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:54,737 - INFO - Frame 824 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 0
2025-11-24 17:25:54,739 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:54,830 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:54,923 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:55,020 - INFO - Frame 826 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 0
2025-11-24 17:25:55,021 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:55,114 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:55,207 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:55,300 - INFO - Frame 828 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 0
2025-11-24 17:25:55,302 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:55,394 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:55,489 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:55,583 - INFO - Frame 830 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 0
2025-11-24 17:25:55,586 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:55,684 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:55,790 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:55,879 - INFO - Frame 832 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 0
2025-11-24 17:25:55,881 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:55,975 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:56,075 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:56,166 - INFO - Frame 834 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 0
2025-11-24 17:25:56,168 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:56,260 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:56,353 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:56,445 - INFO - Frame 836 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 0
2025-11-24 17:25:56,446 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:56,538 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:56,632 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:56,722 - INFO - Frame 838 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 0
2025-11-24 17:25:56,725 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:56,817 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:56,906 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:56,927 - INFO - Frame 840 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 0
2025-11-24 17:25:56,997 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:57,091 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:57,186 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:57,207 - INFO - Frame 842 | PERCLOS: 0.69 | Yaw: 3.8° | Alerts: 1
2025-11-24 17:25:57,272 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:57,372 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:57,464 - INFO - Frame 844 | PERCLOS: 0.24 | Yaw: 4.5° | Alerts: 0
2025-11-24 17:25:57,466 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:57,558 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:57,657 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:57,679 - INFO - Frame 846 | PERCLOS: 0.20 | Yaw: 4.4° | Alerts: 0
2025-11-24 17:25:57,753 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:57,852 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:25:57,942 - INFO - Frame 848 | PERCLOS: 0.12 | Yaw: 4.6° | Alerts: 0
2025-11-24 17:25:57,944 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:07,942 - INFO - Loading models...
2025-11-24 17:30:07,967 - INFO - ✓ YOLO ONNX loaded
2025-11-24 17:30:07,998 - INFO - ✓ MediaPipe Face Mesh loaded
2025-11-24 17:30:08,004 - INFO - ✓ MediaPipe Pose loaded (for smoke & seatbelt)
2025-11-24 17:30:08,015 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:08,169 - INFO - ✓ Camera 0 opened successfully
2025-11-24 17:30:08,183 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:08,316 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:08,447 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:08,591 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:08,733 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:08,749 - INFO - Frame 0 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 0
2025-11-24 17:30:08,873 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:09,017 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:09,161 - INFO - Frame 2 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 0
2025-11-24 17:30:09,166 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:09,297 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:09,446 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:09,597 - INFO - Frame 4 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 0
2025-11-24 17:30:09,600 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:09,774 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:09,917 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:09,934 - INFO - Frame 6 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 0
2025-11-24 17:30:10,069 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:10,224 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:10,378 - INFO - Frame 8 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 0
2025-11-24 17:30:10,384 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:10,530 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:10,688 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:10,838 - INFO - Frame 10 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 0
2025-11-24 17:30:10,845 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:10,996 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:11,148 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:11,302 - INFO - Frame 12 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 0
2025-11-24 17:30:11,307 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:11,460 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:11,606 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:11,765 - INFO - Frame 14 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 0
2025-11-24 17:30:11,772 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:11,925 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:12,083 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:12,247 - INFO - Frame 16 | PERCLOS: 0.00 | Yaw: 4.8° | Alerts: 0
2025-11-24 17:30:12,251 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:12,402 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:12,555 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:12,718 - INFO - Frame 18 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:30:12,727 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:12,870 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:13,025 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:13,041 - INFO - Frame 20 | PERCLOS: 0.00 | Yaw: 4.7° | Alerts: 0
2025-11-24 17:30:13,177 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:13,329 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:13,481 - INFO - Frame 22 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 0
2025-11-24 17:30:13,487 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:13,643 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:13,796 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:13,953 - INFO - Frame 24 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 0
2025-11-24 17:30:13,957 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:14,096 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:14,259 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:14,275 - INFO - Frame 26 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 0
2025-11-24 17:30:14,416 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:14,579 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:14,729 - INFO - Frame 28 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 0
2025-11-24 17:30:14,736 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:14,891 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:15,044 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:15,201 - INFO - Frame 30 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 0
2025-11-24 17:30:15,205 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:15,358 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:15,502 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:15,517 - INFO - Frame 32 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 0
2025-11-24 17:30:15,696 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:15,851 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:16,009 - INFO - Frame 34 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 0
2025-11-24 17:30:16,014 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:16,171 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:16,322 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:16,480 - INFO - Frame 36 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:30:16,482 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:16,643 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:16,797 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:16,816 - INFO - Frame 38 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:30:16,957 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:17,114 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:17,253 - INFO - Frame 40 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 0
2025-11-24 17:30:17,260 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:17,408 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:17,562 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:17,726 - INFO - Frame 42 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:30:17,731 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:17,888 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:18,036 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:18,192 - INFO - Frame 44 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 0
2025-11-24 17:30:18,197 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:18,350 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:18,508 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:18,666 - INFO - Frame 46 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 0
2025-11-24 17:30:18,671 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:18,826 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:18,982 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:19,141 - INFO - Frame 48 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 0
2025-11-24 17:30:19,145 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:19,302 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:19,463 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:19,661 - INFO - Frame 50 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:30:19,662 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:19,811 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:19,963 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:20,110 - INFO - Frame 52 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:30:20,114 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:20,269 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:20,431 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:20,447 - INFO - Frame 54 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:30:20,589 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:20,748 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:20,904 - INFO - Frame 56 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 0
2025-11-24 17:30:20,908 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:21,048 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:21,206 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:21,221 - INFO - Frame 58 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:30:21,364 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:21,533 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:21,683 - INFO - Frame 60 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 0
2025-11-24 17:30:21,688 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:21,845 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:22,005 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:22,159 - INFO - Frame 62 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:30:22,163 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:22,311 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:22,469 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:22,486 - INFO - Frame 64 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:30:22,632 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:22,787 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:22,940 - INFO - Frame 66 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:30:22,946 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:23,104 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:23,249 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:23,402 - INFO - Frame 68 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:30:23,404 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:23,551 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:23,709 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:23,857 - INFO - Frame 70 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:30:23,860 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:24,004 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:24,147 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:24,163 - INFO - Frame 72 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:30:24,302 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:24,459 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:24,616 - INFO - Frame 74 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 0
2025-11-24 17:30:24,622 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:24,776 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:24,935 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:25,097 - INFO - Frame 76 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:30:25,102 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:25,251 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:25,399 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:25,554 - INFO - Frame 78 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:30:25,556 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:25,704 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:25,857 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:26,014 - INFO - Frame 80 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 0
2025-11-24 17:30:26,020 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:26,174 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:26,327 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:26,472 - INFO - Frame 82 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:30:26,476 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:26,618 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:26,766 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:26,783 - INFO - Frame 84 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 0
2025-11-24 17:30:26,918 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:27,067 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:27,229 - INFO - Frame 86 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 0
2025-11-24 17:30:27,234 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:27,394 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:27,548 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:27,700 - INFO - Frame 88 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:30:27,704 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:27,850 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:28,004 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:28,017 - INFO - Frame 90 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:30:28,148 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:28,307 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:28,462 - INFO - Frame 92 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 0
2025-11-24 17:30:28,468 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:28,615 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:28,777 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:28,925 - INFO - Frame 94 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:30:28,930 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:29,081 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:29,235 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:29,252 - INFO - Frame 96 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 0
2025-11-24 17:30:29,392 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:29,541 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:29,691 - INFO - Frame 98 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:30:29,695 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:29,849 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:29,998 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:30,014 - INFO - Frame 100 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 0
2025-11-24 17:30:30,158 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:30,311 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:30,471 - INFO - Frame 102 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 0
2025-11-24 17:30:30,474 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:30,628 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:30,787 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:30,941 - INFO - Frame 104 | PERCLOS: 0.24 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:30:30,947 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:31,104 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:31,256 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:31,420 - INFO - Frame 106 | PERCLOS: 0.87 | Yaw: 0.2° | Alerts: 1
2025-11-24 17:30:31,422 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:31,573 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:31,720 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:31,871 - INFO - Frame 108 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 0
2025-11-24 17:30:31,877 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:32,027 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:32,183 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:32,347 - INFO - Frame 110 | PERCLOS: 0.57 | Yaw: 0.2° | Alerts: 1
2025-11-24 17:30:32,349 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:32,499 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:32,655 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:32,809 - INFO - Frame 112 | PERCLOS: 0.25 | Yaw: 0.2° | Alerts: 0
2025-11-24 17:30:32,815 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:32,976 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:33,129 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:33,284 - INFO - Frame 114 | PERCLOS: 0.03 | Yaw: 0.2° | Alerts: 0
2025-11-24 17:30:33,287 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:33,441 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:33,597 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:33,756 - INFO - Frame 116 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 0
2025-11-24 17:30:33,762 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:33,915 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:34,057 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:34,217 - INFO - Frame 118 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:30:34,221 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:34,369 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:34,514 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:34,665 - INFO - Frame 120 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:30:34,669 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:34,814 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:34,972 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:34,989 - INFO - Frame 122 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:30:35,129 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:35,279 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:35,441 - INFO - Frame 124 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 0
2025-11-24 17:30:35,447 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:35,627 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:35,790 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:35,947 - INFO - Frame 126 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:30:35,953 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:36,108 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:36,261 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:36,421 - INFO - Frame 128 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 0
2025-11-24 17:30:36,426 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:36,580 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:36,743 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:36,899 - INFO - Frame 130 | PERCLOS: 0.28 | Yaw: 0.3° | Alerts: 0
2025-11-24 17:30:36,905 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:37,053 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:37,201 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:37,361 - INFO - Frame 132 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 0
2025-11-24 17:30:37,365 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:37,514 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:37,670 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:37,687 - INFO - Frame 134 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 0
2025-11-24 17:30:37,826 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:37,980 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:38,138 - INFO - Frame 136 | PERCLOS: 0.00 | Yaw: 0.2° | Alerts: 0
2025-11-24 17:30:38,142 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:38,287 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:38,442 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:38,460 - INFO - Frame 138 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 0
2025-11-24 17:30:38,590 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:38,748 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:38,901 - INFO - Frame 140 | PERCLOS: 0.27 | Yaw: 0.2° | Alerts: 0
2025-11-24 17:30:38,906 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:39,063 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:39,218 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:39,373 - INFO - Frame 142 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 0
2025-11-24 17:30:39,377 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:39,530 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:39,687 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:39,704 - INFO - Frame 144 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 0
2025-11-24 17:30:39,840 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:39,992 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:40,151 - INFO - Frame 146 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 0
2025-11-24 17:30:40,157 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:40,311 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:40,463 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:40,619 - INFO - Frame 148 | PERCLOS: 0.12 | Yaw: 0.2° | Alerts: 0
2025-11-24 17:30:40,625 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:40,777 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:40,932 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:41,096 - INFO - Frame 150 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 0
2025-11-24 17:30:41,098 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:41,251 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:41,412 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:41,568 - INFO - Frame 152 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 0
2025-11-24 17:30:41,572 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:41,727 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:41,886 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:42,042 - INFO - Frame 154 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 0
2025-11-24 17:30:42,046 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:42,193 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:42,345 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:42,361 - INFO - Frame 156 | PERCLOS: 0.00 | Yaw: 0.2° | Alerts: 0
2025-11-24 17:30:42,496 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:42,654 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:42,805 - INFO - Frame 158 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 0
2025-11-24 17:30:42,809 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:42,957 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:43,107 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:43,124 - INFO - Frame 160 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 0
2025-11-24 17:30:43,258 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:43,415 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:43,568 - INFO - Frame 162 | PERCLOS: 0.00 | Yaw: 6.7° | Alerts: 0
2025-11-24 17:30:43,573 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:43,727 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:43,888 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:44,041 - INFO - Frame 164 | PERCLOS: 0.00 | Yaw: 7.0° | Alerts: 0
2025-11-24 17:30:44,046 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:44,202 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:44,349 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:44,505 - INFO - Frame 166 | PERCLOS: 0.00 | Yaw: 7.6° | Alerts: 0
2025-11-24 17:30:44,512 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:44,668 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:44,828 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:44,989 - INFO - Frame 168 | PERCLOS: 0.02 | Yaw: 5.7° | Alerts: 0
2025-11-24 17:30:44,991 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:45,137 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:45,296 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:45,442 - INFO - Frame 170 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 0
2025-11-24 17:30:45,448 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:45,596 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:45,751 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:45,914 - INFO - Frame 172 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 0
2025-11-24 17:30:45,916 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:46,069 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:46,228 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:46,384 - INFO - Frame 174 | PERCLOS: 0.24 | Yaw: 2.6° | Alerts: 0
2025-11-24 17:30:46,390 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:46,540 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:46,698 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:46,847 - INFO - Frame 176 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 0
2025-11-24 17:30:46,853 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:47,008 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:47,165 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:47,312 - INFO - Frame 178 | PERCLOS: 0.00 | Yaw: 7.0° | Alerts: 0
2025-11-24 17:30:47,317 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:47,465 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:47,617 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:47,778 - INFO - Frame 180 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:30:47,784 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:47,933 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:48,087 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:48,240 - INFO - Frame 182 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:30:48,243 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:48,389 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:48,550 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:48,567 - INFO - Frame 184 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:30:48,700 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:48,852 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:49,001 - INFO - Frame 186 | PERCLOS: 0.00 | Yaw: 7.7° | Alerts: 0
2025-11-24 17:30:49,007 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:49,154 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:49,314 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:49,468 - INFO - Frame 188 | PERCLOS: 0.00 | Yaw: 6.9° | Alerts: 0
2025-11-24 17:30:49,478 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:49,622 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:49,773 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:49,914 - INFO - Frame 190 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 0
2025-11-24 17:30:49,918 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:50,072 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:50,225 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:50,382 - INFO - Frame 192 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 0
2025-11-24 17:30:50,388 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:50,540 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:50,701 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:50,851 - INFO - Frame 194 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 0
2025-11-24 17:30:50,856 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:51,017 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:51,170 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:51,328 - INFO - Frame 196 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:30:51,333 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:51,489 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:51,649 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:51,842 - INFO - Frame 198 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:30:51,847 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:51,998 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:52,150 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:52,316 - INFO - Frame 200 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:30:52,321 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:52,475 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:52,632 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:52,787 - INFO - Frame 202 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 0
2025-11-24 17:30:52,793 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:52,947 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:53,098 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:53,255 - INFO - Frame 204 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 0
2025-11-24 17:30:53,261 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:53,415 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:53,573 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:53,726 - INFO - Frame 206 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 0
2025-11-24 17:30:53,730 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:53,879 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:54,035 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:54,052 - INFO - Frame 208 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:30:54,191 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:54,348 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:54,504 - INFO - Frame 210 | PERCLOS: 0.16 | Yaw: 4.7° | Alerts: 0
2025-11-24 17:30:54,510 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:54,669 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:54,823 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:54,975 - INFO - Frame 212 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 0
2025-11-24 17:30:54,979 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:55,135 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:55,289 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:55,441 - INFO - Frame 214 | PERCLOS: 0.00 | Yaw: 6.2° | Alerts: 0
2025-11-24 17:30:55,447 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:55,602 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:55,760 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:55,917 - INFO - Frame 216 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 0
2025-11-24 17:30:55,922 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:56,080 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:56,237 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:56,387 - INFO - Frame 218 | PERCLOS: 0.00 | Yaw: 6.5° | Alerts: 0
2025-11-24 17:30:56,391 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:56,539 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:56,691 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:56,708 - INFO - Frame 220 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 0
2025-11-24 17:30:56,840 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:56,986 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:57,144 - INFO - Frame 222 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 0
2025-11-24 17:30:57,148 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:57,286 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:57,441 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:57,459 - INFO - Frame 224 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 0
2025-11-24 17:30:57,603 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:57,759 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:57,911 - INFO - Frame 226 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 0
2025-11-24 17:30:57,918 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:58,061 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:58,209 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:58,357 - INFO - Frame 228 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 0
2025-11-24 17:30:58,360 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:58,511 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:58,670 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:58,813 - INFO - Frame 230 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 0
2025-11-24 17:30:58,819 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:58,967 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:59,115 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:59,279 - INFO - Frame 232 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 0
2025-11-24 17:30:59,281 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:59,439 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:59,587 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:59,744 - INFO - Frame 234 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 0
2025-11-24 17:30:59,749 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:30:59,908 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:00,054 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:00,214 - INFO - Frame 236 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 0
2025-11-24 17:31:00,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:00,376 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:00,534 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:00,698 - INFO - Frame 238 | PERCLOS: 0.41 | Yaw: 4.6° | Alerts: 1
2025-11-24 17:31:00,698 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:00,855 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:01,011 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:01,161 - INFO - Frame 240 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:31:01,167 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:01,322 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:01,476 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:01,632 - INFO - Frame 242 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:31:01,635 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:01,797 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:01,953 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:02,108 - INFO - Frame 244 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:31:02,110 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:02,258 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:02,408 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:02,562 - INFO - Frame 246 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:31:02,567 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:02,708 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:02,861 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:03,016 - INFO - Frame 248 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:31:03,020 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:03,175 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:03,336 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:03,484 - INFO - Frame 250 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:31:03,488 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:03,635 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:03,793 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:03,811 - INFO - Frame 252 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:31:03,952 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:04,107 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:04,266 - INFO - Frame 254 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:31:04,269 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:04,404 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:04,564 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:04,584 - INFO - Frame 256 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:31:04,720 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:04,871 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:05,027 - INFO - Frame 258 | PERCLOS: 0.00 | Yaw: 7.4° | Alerts: 0
2025-11-24 17:31:05,033 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:05,191 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:05,345 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:05,497 - INFO - Frame 260 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 0
2025-11-24 17:31:05,503 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:05,660 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:05,848 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:05,864 - INFO - Frame 262 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 0
2025-11-24 17:31:05,999 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:06,171 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:06,306 - INFO - Frame 264 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 0
2025-11-24 17:31:06,311 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:06,467 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:06,622 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:06,780 - INFO - Frame 266 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 0
2025-11-24 17:31:06,786 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:06,933 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:07,085 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:07,240 - INFO - Frame 268 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 0
2025-11-24 17:31:07,245 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:07,400 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:07,548 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:07,707 - INFO - Frame 270 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 0
2025-11-24 17:31:07,714 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:07,868 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:08,028 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:08,177 - INFO - Frame 272 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 0
2025-11-24 17:31:08,183 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:08,351 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:08,497 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:08,658 - INFO - Frame 274 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 0
2025-11-24 17:31:08,659 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:08,819 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:08,970 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:09,126 - INFO - Frame 276 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 0
2025-11-24 17:31:09,130 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:09,271 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:09,425 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:09,442 - INFO - Frame 278 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 0
2025-11-24 17:31:09,584 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:09,738 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:09,896 - INFO - Frame 280 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 0
2025-11-24 17:31:09,898 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:10,055 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:10,210 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:10,366 - INFO - Frame 282 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 0
2025-11-24 17:31:10,370 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:10,511 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:10,662 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:10,680 - INFO - Frame 284 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 0
2025-11-24 17:31:10,816 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:10,976 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:11,127 - INFO - Frame 286 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 0
2025-11-24 17:31:11,133 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:11,283 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:11,441 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:11,587 - INFO - Frame 288 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 0
2025-11-24 17:31:11,588 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:11,741 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:11,891 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:12,045 - INFO - Frame 290 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 0
2025-11-24 17:31:12,049 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:12,197 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:12,359 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:12,376 - INFO - Frame 292 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 0
2025-11-24 17:31:12,518 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:12,671 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:12,833 - INFO - Frame 294 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 0
2025-11-24 17:31:12,835 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:12,984 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:13,145 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:13,298 - INFO - Frame 296 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 0
2025-11-24 17:31:13,304 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:13,459 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:13,624 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:13,779 - INFO - Frame 298 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 0
2025-11-24 17:31:13,785 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:13,940 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:14,099 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:14,254 - INFO - Frame 300 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 0
2025-11-24 17:31:14,256 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:14,410 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:14,566 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:14,717 - INFO - Frame 302 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 0
2025-11-24 17:31:14,723 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:14,877 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:15,037 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:15,052 - INFO - Frame 304 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 0
2025-11-24 17:31:15,198 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:15,350 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:15,508 - INFO - Frame 306 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 0
2025-11-24 17:31:15,512 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:15,660 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:15,809 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:15,826 - INFO - Frame 308 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 0
2025-11-24 17:31:15,958 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:16,105 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:16,270 - INFO - Frame 310 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 0
2025-11-24 17:31:16,276 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:16,430 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:16,590 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:16,746 - INFO - Frame 312 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 0
2025-11-24 17:31:16,749 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:16,908 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:17,061 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:17,207 - INFO - Frame 314 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 0
2025-11-24 17:31:17,213 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:17,366 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:17,523 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:17,677 - INFO - Frame 316 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 0
2025-11-24 17:31:17,680 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:17,834 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:17,987 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:18,003 - INFO - Frame 318 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 0
2025-11-24 17:31:18,146 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:18,301 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:18,399 - INFO - Frame 320 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 0
2025-11-24 17:31:18,463 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:18,617 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:18,765 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:18,928 - INFO - Frame 322 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 0
2025-11-24 17:31:18,930 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:19,080 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:19,237 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:19,397 - INFO - Frame 324 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 0
2025-11-24 17:31:19,403 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:19,604 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:19,761 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:19,921 - INFO - Frame 326 | PERCLOS: 0.22 | Yaw: 2.8° | Alerts: 0
2025-11-24 17:31:19,926 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:20,079 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:20,237 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:20,385 - INFO - Frame 328 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 0
2025-11-24 17:31:20,390 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:20,543 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:20,692 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:20,852 - INFO - Frame 330 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 0
2025-11-24 17:31:20,857 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:21,014 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:21,159 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:21,177 - INFO - Frame 332 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 0
2025-11-24 17:31:21,314 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:21,471 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:21,627 - INFO - Frame 334 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 0
2025-11-24 17:31:21,633 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:21,788 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:21,936 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:22,087 - INFO - Frame 336 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 0
2025-11-24 17:31:22,091 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:22,249 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:22,406 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:22,420 - INFO - Frame 338 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 0
2025-11-24 17:31:22,573 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:22,729 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:22,880 - INFO - Frame 340 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 0
2025-11-24 17:31:22,881 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:23,030 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:23,182 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:23,343 - INFO - Frame 342 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 0
2025-11-24 17:31:23,347 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:23,487 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:23,641 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:23,665 - INFO - Frame 344 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 0
2025-11-24 17:31:23,799 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:23,958 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:24,120 - INFO - Frame 346 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 0
2025-11-24 17:31:24,128 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:24,274 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:24,427 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:24,448 - INFO - Frame 348 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 0
2025-11-24 17:31:24,587 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:24,737 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:24,900 - INFO - Frame 350 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 0
2025-11-24 17:31:24,905 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:25,057 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:25,214 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:25,368 - INFO - Frame 352 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 0
2025-11-24 17:31:25,373 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:25,533 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:25,677 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:25,694 - INFO - Frame 354 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 0
2025-11-24 17:31:25,833 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:25,974 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:26,122 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:26,127 - INFO - Frame 356 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 17:31:26,278 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:26,441 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:26,589 - INFO - Frame 358 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 0
2025-11-24 17:31:26,595 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:26,751 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:26,902 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:27,061 - INFO - Frame 360 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 0
2025-11-24 17:31:27,066 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:27,215 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:27,364 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:27,519 - INFO - Frame 362 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 0
2025-11-24 17:31:27,521 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:27,672 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:27,819 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:27,974 - INFO - Frame 364 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 0
2025-11-24 17:31:27,979 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:28,142 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:28,304 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:28,444 - INFO - Frame 366 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 0
2025-11-24 17:31:28,450 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:28,599 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:28,748 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:28,910 - INFO - Frame 368 | PERCLOS: 0.37 | Yaw: 2.8° | Alerts: 1
2025-11-24 17:31:28,916 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:29,071 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:29,225 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:29,374 - INFO - Frame 370 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 0
2025-11-24 17:31:29,380 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:29,514 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:29,664 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:29,682 - INFO - Frame 372 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 0
2025-11-24 17:31:29,833 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:29,986 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:30,089 - INFO - Frame 374 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 0
2025-11-24 17:31:30,154 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:30,302 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:30,451 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:30,468 - INFO - Frame 376 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 0
2025-11-24 17:31:30,618 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:30,771 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:30,924 - INFO - Frame 378 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:31:30,929 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:31,083 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:31,238 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:31,408 - INFO - Frame 380 | PERCLOS: 0.00 | Yaw: 5.4° | Alerts: 0
2025-11-24 17:31:31,412 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:31,562 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:31,722 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:31,741 - INFO - Frame 382 | PERCLOS: 0.00 | Yaw: 5.2° | Alerts: 0
2025-11-24 17:31:31,869 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:32,026 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:32,177 - INFO - Frame 384 | PERCLOS: 0.00 | Yaw: 5.2° | Alerts: 0
2025-11-24 17:31:32,185 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:32,337 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:32,492 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:32,648 - INFO - Frame 386 | PERCLOS: 0.00 | Yaw: 4.9° | Alerts: 0
2025-11-24 17:31:32,655 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:32,819 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:32,968 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:33,126 - INFO - Frame 388 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 0
2025-11-24 17:31:33,130 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:33,279 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:33,419 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:33,434 - INFO - Frame 390 | PERCLOS: 0.00 | Yaw: 5.8° | Alerts: 0
2025-11-24 17:31:33,573 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:33,737 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:33,893 - INFO - Frame 392 | PERCLOS: 0.00 | Yaw: 5.8° | Alerts: 0
2025-11-24 17:31:33,896 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:34,039 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:34,189 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:34,208 - INFO - Frame 394 | PERCLOS: 0.00 | Yaw: 7.0° | Alerts: 0
2025-11-24 17:31:34,355 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:34,532 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:34,693 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:34,709 - INFO - Frame 396 | PERCLOS: 0.00 | Yaw: 6.9° | Alerts: 0
2025-11-24 17:31:34,840 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:35,011 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:35,165 - INFO - Frame 398 | PERCLOS: 0.00 | Yaw: 6.6° | Alerts: 0
2025-11-24 17:31:35,170 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:35,324 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:35,484 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:35,639 - INFO - Frame 400 | PERCLOS: 0.50 | Yaw: 6.6° | Alerts: 1
2025-11-24 17:31:35,645 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:35,803 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:35,956 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:36,106 - INFO - Frame 402 | PERCLOS: 0.00 | Yaw: 7.1° | Alerts: 0
2025-11-24 17:31:36,112 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:36,263 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:36,413 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:36,571 - INFO - Frame 404 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 0
2025-11-24 17:31:36,578 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:36,726 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:36,883 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:36,901 - INFO - Frame 406 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 0
2025-11-24 17:31:37,036 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:37,186 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:37,342 - INFO - Frame 408 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 0
2025-11-24 17:31:37,347 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:37,496 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:37,650 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:37,807 - INFO - Frame 410 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 0
2025-11-24 17:31:37,813 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:37,965 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:38,124 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:38,278 - INFO - Frame 412 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 0
2025-11-24 17:31:38,284 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:38,431 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:38,577 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:38,596 - INFO - Frame 414 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 0
2025-11-24 17:31:38,738 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:38,895 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:39,052 - INFO - Frame 416 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 0
2025-11-24 17:31:39,056 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:39,203 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:39,355 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:39,370 - INFO - Frame 418 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 0
2025-11-24 17:31:39,517 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:39,678 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:39,827 - INFO - Frame 420 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 0
2025-11-24 17:31:39,833 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:39,985 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:40,145 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:40,304 - INFO - Frame 422 | PERCLOS: 0.78 | Yaw: 1.4° | Alerts: 1
2025-11-24 17:31:40,308 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:40,467 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:40,627 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:40,788 - INFO - Frame 424 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 0
2025-11-24 17:31:40,795 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:40,951 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:41,118 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:41,289 - INFO - Frame 426 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 0
2025-11-24 17:31:41,293 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:41,447 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:41,602 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:41,761 - INFO - Frame 428 | PERCLOS: 0.63 | Yaw: 1.5° | Alerts: 1
2025-11-24 17:31:41,766 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:41,917 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:42,065 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:42,081 - INFO - Frame 430 | PERCLOS: 0.76 | Yaw: 1.4° | Alerts: 1
2025-11-24 17:31:42,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:42,372 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:42,526 - INFO - Frame 432 | PERCLOS: 0.66 | Yaw: 1.5° | Alerts: 1
2025-11-24 17:31:42,530 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:42,685 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:42,850 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:43,011 - INFO - Frame 434 | PERCLOS: 0.06 | Yaw: 1.4° | Alerts: 0
2025-11-24 17:31:43,013 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:43,168 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:43,315 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:43,479 - INFO - Frame 436 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 0
2025-11-24 17:31:43,483 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:43,637 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:43,786 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:43,938 - INFO - Frame 438 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 0
2025-11-24 17:31:43,945 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:44,093 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:44,257 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:44,404 - INFO - Frame 440 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 0
2025-11-24 17:31:44,408 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:44,555 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:44,710 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:44,726 - INFO - Frame 442 | PERCLOS: 0.00 | Yaw: 4.7° | Alerts: 0
2025-11-24 17:31:44,865 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:45,021 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:45,171 - INFO - Frame 444 | PERCLOS: 0.88 | Yaw: 4.5° | Alerts: 1
2025-11-24 17:31:45,172 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:45,323 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:45,478 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:45,627 - INFO - Frame 446 | PERCLOS: 0.77 | Yaw: 4.4° | Alerts: 1
2025-11-24 17:31:45,630 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:45,784 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:45,939 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:45,952 - INFO - Frame 448 | PERCLOS: 0.74 | Yaw: 4.2° | Alerts: 1
2025-11-24 17:31:46,091 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:46,247 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:46,397 - INFO - Frame 450 | PERCLOS: 0.41 | Yaw: 4.2° | Alerts: 1
2025-11-24 17:31:46,401 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:46,559 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:46,702 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:46,719 - INFO - Frame 452 | PERCLOS: 0.17 | Yaw: 4.2° | Alerts: 0
2025-11-24 17:31:46,860 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:47,006 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:47,166 - INFO - Frame 454 | PERCLOS: 0.23 | Yaw: 4.0° | Alerts: 0
2025-11-24 17:31:47,171 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:47,328 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:47,482 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:47,638 - INFO - Frame 456 | PERCLOS: 0.23 | Yaw: 4.2° | Alerts: 0
2025-11-24 17:31:47,642 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:47,789 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:47,943 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:47,968 - INFO - Frame 458 | PERCLOS: 0.26 | Yaw: 4.1° | Alerts: 0
2025-11-24 17:31:48,100 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:48,267 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:48,421 - INFO - Frame 460 | PERCLOS: 0.32 | Yaw: 4.2° | Alerts: 1
2025-11-24 17:31:48,424 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:48,576 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:48,732 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:48,894 - INFO - Frame 462 | PERCLOS: 0.04 | Yaw: 4.3° | Alerts: 0
2025-11-24 17:31:48,898 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:49,053 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:49,200 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:49,357 - INFO - Frame 464 | PERCLOS: 0.64 | Yaw: 4.1° | Alerts: 1
2025-11-24 17:31:49,363 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:49,517 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:49,670 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:49,826 - INFO - Frame 466 | PERCLOS: 0.80 | Yaw: 4.2° | Alerts: 1
2025-11-24 17:31:49,831 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:49,983 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:50,143 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:50,306 - INFO - Frame 468 | PERCLOS: 0.73 | Yaw: 4.2° | Alerts: 1
2025-11-24 17:31:50,308 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:50,460 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:50,618 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:50,794 - INFO - Frame 470 | PERCLOS: 0.25 | Yaw: 4.1° | Alerts: 0
2025-11-24 17:31:50,797 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:50,946 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:51,106 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:51,261 - INFO - Frame 472 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 0
2025-11-24 17:31:51,265 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:51,412 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:51,572 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:51,724 - INFO - Frame 474 | PERCLOS: 0.00 | Yaw: 4.1° | Alerts: 0
2025-11-24 17:31:51,730 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:51,880 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:52,036 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:52,199 - INFO - Frame 476 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 0
2025-11-24 17:31:52,206 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:52,363 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:52,522 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:52,685 - INFO - Frame 478 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 0
2025-11-24 17:31:52,691 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:52,845 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:52,994 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:53,161 - INFO - Frame 480 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 0
2025-11-24 17:31:53,166 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:53,318 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:53,484 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:53,641 - INFO - Frame 482 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 0
2025-11-24 17:31:53,647 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:53,793 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:53,940 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:54,095 - INFO - Frame 484 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 0
2025-11-24 17:31:54,101 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:54,255 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:54,401 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:54,557 - INFO - Frame 486 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 0
2025-11-24 17:31:54,563 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:54,709 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:54,862 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:55,011 - INFO - Frame 488 | PERCLOS: 0.78 | Yaw: 4.0° | Alerts: 1
2025-11-24 17:31:55,016 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:55,183 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:55,337 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:55,487 - INFO - Frame 490 | PERCLOS: 0.78 | Yaw: 4.1° | Alerts: 1
2025-11-24 17:31:55,492 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:55,631 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:55,798 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:55,959 - INFO - Frame 492 | PERCLOS: 0.46 | Yaw: 4.1° | Alerts: 1
2025-11-24 17:31:55,959 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:56,112 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:56,266 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:56,424 - INFO - Frame 494 | PERCLOS: 0.04 | Yaw: 4.1° | Alerts: 0
2025-11-24 17:31:56,430 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:56,583 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:56,732 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:56,892 - INFO - Frame 496 | PERCLOS: 0.10 | Yaw: 3.9° | Alerts: 0
2025-11-24 17:31:56,894 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:57,049 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:57,214 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:57,370 - INFO - Frame 498 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 0
2025-11-24 17:31:57,378 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:57,523 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:57,675 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:57,837 - INFO - Frame 500 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 0
2025-11-24 17:31:57,839 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:57,992 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:58,150 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:58,299 - INFO - Frame 502 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 0
2025-11-24 17:31:58,303 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:58,457 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:58,601 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:58,757 - INFO - Frame 504 | PERCLOS: 0.00 | Yaw: 4.1° | Alerts: 0
2025-11-24 17:31:58,764 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:58,930 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:59,089 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:59,239 - INFO - Frame 506 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 0
2025-11-24 17:31:59,245 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:59,393 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:59,541 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:59,686 - INFO - Frame 508 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 0
2025-11-24 17:31:59,695 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:31:59,844 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:00,013 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:00,164 - INFO - Frame 510 | PERCLOS: 0.60 | Yaw: 4.1° | Alerts: 1
2025-11-24 17:32:00,170 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:00,313 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:00,454 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:00,610 - INFO - Frame 512 | PERCLOS: 0.74 | Yaw: 4.0° | Alerts: 1
2025-11-24 17:32:00,617 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:00,776 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:00,929 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:01,086 - INFO - Frame 514 | PERCLOS: 0.72 | Yaw: 4.1° | Alerts: 1
2025-11-24 17:32:01,091 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:01,255 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:01,410 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:01,567 - INFO - Frame 516 | PERCLOS: 0.23 | Yaw: 4.2° | Alerts: 0
2025-11-24 17:32:01,572 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:01,717 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:01,865 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:02,023 - INFO - Frame 518 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 0
2025-11-24 17:32:02,029 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:02,188 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:02,331 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:02,368 - INFO - Frame 520 | PERCLOS: 0.00 | Yaw: 6.2° | Alerts: 0
2025-11-24 17:32:02,495 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:02,651 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:02,795 - INFO - Frame 522 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 0
2025-11-24 17:32:02,801 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:02,967 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:03,116 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:03,132 - INFO - Frame 524 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 0
2025-11-24 17:32:03,260 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:03,409 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:03,560 - INFO - Frame 526 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 0
2025-11-24 17:32:03,564 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:03,717 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:03,865 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:03,881 - INFO - Frame 528 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 0
2025-11-24 17:32:04,022 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:04,179 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:04,336 - INFO - Frame 530 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:32:04,339 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:04,486 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:04,639 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:04,657 - INFO - Frame 532 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:32:04,798 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:04,952 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:05,103 - INFO - Frame 534 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:32:05,109 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:05,263 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:05,416 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:05,574 - INFO - Frame 536 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:32:05,579 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:05,746 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:05,906 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:06,054 - INFO - Frame 538 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:32:06,059 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:06,214 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:06,392 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:06,547 - INFO - Frame 540 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:32:06,552 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:06,698 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:06,852 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:06,999 - INFO - Frame 542 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:32:07,004 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:07,168 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:07,319 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:07,480 - INFO - Frame 544 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:32:07,485 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:07,638 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:07,793 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:07,947 - INFO - Frame 546 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:32:07,956 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:08,104 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:08,257 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:08,276 - INFO - Frame 548 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:32:08,407 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:08,559 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:08,707 - INFO - Frame 550 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:32:08,712 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:08,858 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:09,004 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:09,021 - INFO - Frame 552 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:32:09,149 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:09,316 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:09,470 - INFO - Frame 554 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:32:09,470 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:09,625 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:09,780 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:09,935 - INFO - Frame 556 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:32:09,938 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:10,090 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:10,248 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:10,393 - INFO - Frame 558 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:32:10,398 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:10,544 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:10,697 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:10,852 - INFO - Frame 560 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:32:10,858 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:11,015 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:11,163 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:11,318 - INFO - Frame 562 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:32:11,323 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:11,469 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:11,627 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:11,778 - INFO - Frame 564 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:32:11,782 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:11,926 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:12,077 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:12,093 - INFO - Frame 566 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:32:12,233 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:12,394 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:12,560 - INFO - Frame 568 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:32:12,567 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:12,726 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:12,880 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:13,032 - INFO - Frame 570 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:32:13,034 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:13,179 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:13,333 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:13,488 - INFO - Frame 572 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:32:13,493 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:13,648 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:13,797 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:13,948 - INFO - Frame 574 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:32:13,953 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:14,115 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:14,275 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:14,436 - INFO - Frame 576 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:32:14,441 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:14,590 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:14,744 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:14,908 - INFO - Frame 578 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:32:14,910 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:15,062 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:15,217 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:15,369 - INFO - Frame 580 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:32:15,375 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:15,525 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:15,689 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:15,838 - INFO - Frame 582 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:32:15,842 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:15,997 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:16,154 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:16,303 - INFO - Frame 584 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:32:16,307 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:16,458 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:16,615 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:16,772 - INFO - Frame 586 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:32:16,778 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:16,913 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:17,072 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:17,089 - INFO - Frame 588 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 1
2025-11-24 17:32:17,222 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:17,383 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:17,545 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:17,562 - INFO - Frame 590 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 0
2025-11-24 17:32:17,700 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:17,853 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:18,010 - INFO - Frame 592 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 0
2025-11-24 17:32:18,015 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:18,175 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:18,318 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:18,336 - INFO - Frame 594 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 0
2025-11-24 17:32:18,472 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:18,624 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:18,764 - INFO - Frame 596 | PERCLOS: 0.00 | Yaw: -1.1° | Alerts: 0
2025-11-24 17:32:18,768 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:18,923 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:19,085 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:19,236 - INFO - Frame 598 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:32:19,241 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:19,402 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:19,594 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:19,618 - INFO - Frame 600 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:32:19,747 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:19,900 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:20,050 - INFO - Frame 602 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 0
2025-11-24 17:32:20,056 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:20,205 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:20,352 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:20,512 - INFO - Frame 604 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 0
2025-11-24 17:32:20,516 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:20,664 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:20,823 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:20,842 - INFO - Frame 606 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 0
2025-11-24 17:32:20,970 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:21,124 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:21,277 - INFO - Frame 608 | PERCLOS: 0.27 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:32:21,283 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:21,446 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:21,593 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:21,746 - INFO - Frame 610 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 0
2025-11-24 17:32:21,752 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:21,906 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:22,063 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:22,214 - INFO - Frame 612 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 0
2025-11-24 17:32:22,219 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:22,375 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:22,533 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:22,689 - INFO - Frame 614 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:32:22,694 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:22,846 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:23,000 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:23,148 - INFO - Frame 616 | PERCLOS: 0.00 | Yaw: -3.8° | Alerts: 0
2025-11-24 17:32:23,153 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:23,304 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:23,474 - INFO - Frame 618 | PERCLOS: 0.00 | Yaw: -5.6° | Alerts: 0
2025-11-24 17:32:23,477 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:23,630 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:23,777 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:23,926 - INFO - Frame 620 | PERCLOS: 0.00 | Yaw: -3.0° | Alerts: 0
2025-11-24 17:32:23,932 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:24,079 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:24,236 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:24,386 - INFO - Frame 622 | PERCLOS: 0.00 | Yaw: -3.2° | Alerts: 0
2025-11-24 17:32:24,391 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:24,545 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:24,694 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:24,713 - INFO - Frame 624 | PERCLOS: 0.00 | Yaw: -3.3° | Alerts: 0
2025-11-24 17:32:24,842 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:25,006 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:25,155 - INFO - Frame 626 | PERCLOS: 0.00 | Yaw: -3.1° | Alerts: 0
2025-11-24 17:32:25,159 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:25,315 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:25,460 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:25,607 - INFO - Frame 628 | PERCLOS: 0.00 | Yaw: -2.9° | Alerts: 0
2025-11-24 17:32:25,612 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:25,770 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:25,912 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:26,068 - INFO - Frame 630 | PERCLOS: 0.00 | Yaw: -2.7° | Alerts: 0
2025-11-24 17:32:26,070 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:26,219 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:26,375 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:26,392 - INFO - Frame 632 | PERCLOS: 0.00 | Yaw: -2.6° | Alerts: 0
2025-11-24 17:32:26,529 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:26,687 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:26,829 - INFO - Frame 634 | PERCLOS: 0.00 | Yaw: -2.5° | Alerts: 0
2025-11-24 17:32:26,838 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:26,992 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:27,141 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:27,162 - INFO - Frame 636 | PERCLOS: 0.00 | Yaw: -1.8° | Alerts: 0
2025-11-24 17:32:27,300 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:27,457 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:27,613 - INFO - Frame 638 | PERCLOS: 0.00 | Yaw: -1.1° | Alerts: 0
2025-11-24 17:32:27,620 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:27,774 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:27,937 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:28,096 - INFO - Frame 640 | PERCLOS: 0.00 | Yaw: -0.8° | Alerts: 0
2025-11-24 17:32:28,100 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:28,260 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:28,394 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:28,550 - INFO - Frame 642 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 0
2025-11-24 17:32:28,556 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:28,703 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:28,859 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:28,877 - INFO - Frame 644 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 0
2025-11-24 17:32:29,007 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:29,173 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:29,335 - INFO - Frame 646 | PERCLOS: 0.00 | Yaw: -0.3° | Alerts: 0
2025-11-24 17:32:29,338 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:29,485 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:29,636 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:29,652 - INFO - Frame 648 | PERCLOS: 0.00 | Yaw: -0.2° | Alerts: 0
2025-11-24 17:32:29,789 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:29,947 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:30,103 - INFO - Frame 650 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 0
2025-11-24 17:32:30,109 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:30,255 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:30,413 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:30,572 - INFO - Frame 652 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 0
2025-11-24 17:32:30,578 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:30,726 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:30,884 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:31,027 - INFO - Frame 654 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 0
2025-11-24 17:32:31,033 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:31,199 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:31,355 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:31,508 - INFO - Frame 656 | PERCLOS: 0.00 | Yaw: -0.8° | Alerts: 0
2025-11-24 17:32:31,512 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:31,661 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:31,815 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:31,829 - INFO - Frame 658 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 0
2025-11-24 17:32:31,973 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:32,131 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:32,289 - INFO - Frame 660 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 0
2025-11-24 17:32:32,294 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:32,445 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:32,598 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:32,750 - INFO - Frame 662 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 0
2025-11-24 17:32:32,755 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:32,903 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:33,058 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:33,216 - INFO - Frame 664 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 0
2025-11-24 17:32:33,222 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:33,369 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:33,518 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:33,677 - INFO - Frame 666 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 0
2025-11-24 17:32:33,683 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:33,833 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:33,984 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:34,148 - INFO - Frame 668 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 0
2025-11-24 17:32:34,150 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:34,300 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:34,450 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:34,613 - INFO - Frame 670 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 0
2025-11-24 17:32:34,617 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:34,766 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:34,948 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:35,094 - INFO - Frame 672 | PERCLOS: 0.00 | Yaw: 0.2° | Alerts: 0
2025-11-24 17:32:35,099 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:35,258 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:35,422 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:35,565 - INFO - Frame 674 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:32:35,570 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:35,724 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:35,888 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:36,040 - INFO - Frame 676 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 0
2025-11-24 17:32:36,046 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:36,197 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:36,353 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:36,503 - INFO - Frame 678 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 0
2025-11-24 17:32:36,509 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:36,652 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:36,809 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:36,942 - INFO - Frame 680 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 0
2025-11-24 17:32:36,948 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:37,099 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:37,263 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:37,427 - INFO - Frame 682 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 0
2025-11-24 17:32:37,434 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:37,583 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:37,726 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:37,876 - INFO - Frame 684 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 0
2025-11-24 17:32:37,881 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:38,030 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:38,180 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:38,333 - INFO - Frame 686 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 0
2025-11-24 17:32:38,339 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:38,485 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:38,631 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:38,788 - INFO - Frame 688 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:32:38,794 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:38,942 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:39,097 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:39,245 - INFO - Frame 690 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:32:39,249 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:39,412 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:39,562 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:39,577 - INFO - Frame 692 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 0
2025-11-24 17:32:39,711 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:39,857 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:40,015 - INFO - Frame 694 | PERCLOS: 0.10 | Yaw: 1.5° | Alerts: 0
2025-11-24 17:32:40,021 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:40,168 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:40,324 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:40,486 - INFO - Frame 696 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 0
2025-11-24 17:32:40,492 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:40,651 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:40,804 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:40,962 - INFO - Frame 698 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 0
2025-11-24 17:32:40,968 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:41,122 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:41,273 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:41,439 - INFO - Frame 700 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 0
2025-11-24 17:32:41,444 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:41,594 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:41,747 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:41,764 - INFO - Frame 702 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 0
2025-11-24 17:32:41,898 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:42,040 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:42,190 - INFO - Frame 704 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 0
2025-11-24 17:32:42,194 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:42,347 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:42,502 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:42,658 - INFO - Frame 706 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 0
2025-11-24 17:32:42,663 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:42,814 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:42,969 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:43,128 - INFO - Frame 708 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 0
2025-11-24 17:32:43,135 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:43,288 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:43,461 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:43,612 - INFO - Frame 710 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:32:43,617 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:43,766 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:43,918 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:44,064 - INFO - Frame 712 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:32:44,071 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:44,222 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:44,382 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:44,530 - INFO - Frame 714 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:32:44,537 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:44,691 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:44,838 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:44,995 - INFO - Frame 716 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 0
2025-11-24 17:32:44,999 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:45,140 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:45,297 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:45,311 - INFO - Frame 718 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:32:45,466 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:45,611 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:45,766 - INFO - Frame 720 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:32:45,772 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:45,928 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:46,077 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:46,238 - INFO - Frame 722 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:32:46,244 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:46,398 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:46,552 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:46,706 - INFO - Frame 724 | PERCLOS: 0.31 | Yaw: 0.9° | Alerts: 1
2025-11-24 17:32:46,712 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:46,867 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:47,020 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:47,035 - INFO - Frame 726 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:32:47,167 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:47,322 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:47,494 - INFO - Frame 728 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 0
2025-11-24 17:32:47,500 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:47,638 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:47,797 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:47,956 - INFO - Frame 730 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 0
2025-11-24 17:32:47,962 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:48,116 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:48,267 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:48,409 - INFO - Frame 732 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 0
2025-11-24 17:32:48,415 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:48,567 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:48,719 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:48,873 - INFO - Frame 734 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 0
2025-11-24 17:32:48,879 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:49,034 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:49,189 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:49,341 - INFO - Frame 736 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 0
2025-11-24 17:32:49,347 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:49,501 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:49,665 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:49,811 - INFO - Frame 738 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:32:49,815 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:49,969 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:50,125 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:50,141 - INFO - Frame 740 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 0
2025-11-24 17:32:50,280 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:50,434 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:50,588 - INFO - Frame 742 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:32:50,593 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:50,741 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:50,890 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:51,040 - INFO - Frame 744 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 0
2025-11-24 17:32:51,043 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:51,191 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:51,343 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:51,362 - INFO - Frame 746 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:32:51,530 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:51,710 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:51,855 - INFO - Frame 748 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 0
2025-11-24 17:32:51,859 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:52,011 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:52,157 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:52,180 - INFO - Frame 750 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:32:52,313 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:52,466 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:52,621 - INFO - Frame 752 | PERCLOS: 0.46 | Yaw: -0.5° | Alerts: 1
2025-11-24 17:32:52,627 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:52,784 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:52,943 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:53,099 - INFO - Frame 754 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 0
2025-11-24 17:32:53,105 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:53,264 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:53,415 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:53,583 - INFO - Frame 756 | PERCLOS: 0.01 | Yaw: -0.6° | Alerts: 0
2025-11-24 17:32:53,589 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:53,738 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:53,892 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:53,909 - INFO - Frame 758 | PERCLOS: 0.00 | Yaw: -0.0° | Alerts: 0
2025-11-24 17:32:54,048 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:54,203 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:54,360 - INFO - Frame 760 | PERCLOS: 0.00 | Yaw: 0.2° | Alerts: 0
2025-11-24 17:32:54,364 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:54,506 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:54,654 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:54,673 - INFO - Frame 762 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 0
2025-11-24 17:32:54,810 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:54,970 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:55,127 - INFO - Frame 764 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 0
2025-11-24 17:32:55,132 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:55,279 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:55,455 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:55,611 - INFO - Frame 766 | PERCLOS: 0.13 | Yaw: 1.9° | Alerts: 0
2025-11-24 17:32:55,615 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:55,768 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:55,918 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:56,066 - INFO - Frame 768 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 0
2025-11-24 17:32:56,071 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:56,225 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:56,374 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:56,535 - INFO - Frame 770 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 0
2025-11-24 17:32:56,539 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:56,687 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:56,840 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:57,007 - INFO - Frame 772 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 0
2025-11-24 17:32:57,007 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:57,156 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:57,323 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:57,475 - INFO - Frame 774 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 0
2025-11-24 17:32:57,481 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:57,636 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:57,787 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:57,948 - INFO - Frame 776 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 0
2025-11-24 17:32:57,950 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:58,107 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:58,263 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:58,424 - INFO - Frame 778 | PERCLOS: 0.37 | Yaw: -2.9° | Alerts: 1
2025-11-24 17:32:58,430 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:58,571 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:58,720 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:58,872 - INFO - Frame 780 | PERCLOS: 0.00 | Yaw: -4.0° | Alerts: 0
2025-11-24 17:32:58,878 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:59,021 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:59,199 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:59,349 - INFO - Frame 782 | PERCLOS: 0.30 | Yaw: -7.0° | Alerts: 1
2025-11-24 17:32:59,357 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:59,502 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:59,667 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:59,684 - INFO - Frame 784 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:32:59,815 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:32:59,966 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:00,124 - INFO - Frame 786 | PERCLOS: 0.00 | Yaw: -8.5° | Alerts: 0
2025-11-24 17:33:00,130 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:00,278 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:00,427 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:00,576 - INFO - Frame 788 | PERCLOS: 0.20 | Yaw: -5.5° | Alerts: 0
2025-11-24 17:33:00,582 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:00,738 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:00,892 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:01,047 - INFO - Frame 790 | PERCLOS: 0.12 | Yaw: -1.3° | Alerts: 0
2025-11-24 17:33:01,053 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:01,206 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:01,370 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:01,533 - INFO - Frame 792 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 0
2025-11-24 17:33:01,534 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:01,684 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:01,836 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:01,993 - INFO - Frame 794 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 0
2025-11-24 17:33:01,997 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:02,146 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:02,296 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:02,320 - INFO - Frame 796 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 0
2025-11-24 17:33:02,454 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:02,607 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:02,758 - INFO - Frame 798 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 0
2025-11-24 17:33:02,764 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:02,922 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:03,078 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:03,240 - INFO - Frame 800 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 0
2025-11-24 17:33:03,246 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:03,414 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:03,563 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:03,718 - INFO - Frame 802 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 0
2025-11-24 17:33:03,722 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:03,867 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:04,024 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:04,173 - INFO - Frame 804 | PERCLOS: 0.16 | Yaw: 5.5° | Alerts: 0
2025-11-24 17:33:04,179 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:04,329 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:04,482 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:04,628 - INFO - Frame 806 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:33:04,630 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:04,778 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:04,937 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:04,955 - INFO - Frame 808 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:33:05,096 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:05,252 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:05,405 - INFO - Frame 810 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:33:05,408 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:05,575 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:05,724 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:05,739 - INFO - Frame 812 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:33:05,880 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:06,033 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:06,178 - INFO - Frame 814 | PERCLOS: 0.00 | Yaw: 8.4° | Alerts: 0
2025-11-24 17:33:06,186 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:06,337 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:06,487 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:06,646 - INFO - Frame 816 | PERCLOS: 0.00 | Yaw: 6.9° | Alerts: 0
2025-11-24 17:33:06,652 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:06,805 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:06,961 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:07,111 - INFO - Frame 818 | PERCLOS: 0.00 | Yaw: 6.6° | Alerts: 0
2025-11-24 17:33:07,117 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:07,274 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:07,427 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:07,580 - INFO - Frame 820 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 0
2025-11-24 17:33:07,585 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:07,753 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:07,934 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:08,091 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:08,109 - INFO - Frame 822 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 0
2025-11-24 17:33:08,256 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:08,407 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:08,563 - INFO - Frame 824 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 0
2025-11-24 17:33:08,567 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:08,716 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:08,868 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:09,021 - INFO - Frame 826 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 0
2025-11-24 17:33:09,025 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:09,168 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:09,320 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:09,332 - INFO - Frame 828 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 17:33:09,473 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:09,628 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:09,788 - INFO - Frame 830 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 0
2025-11-24 17:33:09,793 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:09,977 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:10,132 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:10,296 - INFO - Frame 832 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 17:33:10,298 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:10,458 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:10,619 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:10,785 - INFO - Frame 834 | PERCLOS: 0.13 | Yaw: 2.0° | Alerts: 1
2025-11-24 17:33:10,787 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:10,940 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:11,087 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:11,245 - INFO - Frame 836 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 1
2025-11-24 17:33:11,249 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:11,407 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:11,548 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:11,712 - INFO - Frame 838 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 1
2025-11-24 17:33:11,713 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:11,867 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:12,036 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:12,197 - INFO - Frame 840 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 1
2025-11-24 17:33:12,197 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:12,343 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:12,502 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:12,660 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:12,663 - INFO - Frame 842 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-24 17:33:12,815 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:12,962 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:13,116 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:13,117 - INFO - Frame 844 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 17:33:13,273 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:13,428 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:13,590 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:13,592 - INFO - Frame 846 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 1
2025-11-24 17:33:13,743 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:13,900 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:14,072 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:14,075 - INFO - Frame 848 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 1
2025-11-24 17:33:14,230 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:14,384 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:14,546 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:14,546 - INFO - Frame 850 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 1
2025-11-24 17:33:14,701 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:14,851 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:15,012 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:15,017 - INFO - Frame 852 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 1
2025-11-24 17:33:15,176 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:15,338 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:15,486 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:15,486 - INFO - Frame 854 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 1
2025-11-24 17:33:15,644 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:15,802 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:15,961 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:15,963 - INFO - Frame 856 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-24 17:33:16,109 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:16,284 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:16,436 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:16,436 - INFO - Frame 858 | PERCLOS: 0.02 | Yaw: 2.0° | Alerts: 1
2025-11-24 17:33:16,581 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:16,738 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:16,900 - INFO - Frame 860 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 0
2025-11-24 17:33:16,906 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:17,054 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:17,215 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:17,374 - INFO - Frame 862 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 1
2025-11-24 17:33:17,374 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:17,520 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:17,677 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:17,841 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:17,841 - INFO - Frame 864 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-24 17:33:17,989 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:18,142 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:18,320 - INFO - Frame 866 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-24 17:33:18,322 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:18,471 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:18,633 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:18,793 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:18,793 - INFO - Frame 868 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 1
2025-11-24 17:33:18,950 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:19,097 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:19,261 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:19,263 - INFO - Frame 870 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 1
2025-11-24 17:33:19,411 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:19,626 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:19,804 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:19,804 - INFO - Frame 872 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 1
2025-11-24 17:33:19,964 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:20,118 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:20,282 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:20,285 - INFO - Frame 874 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 17:33:20,453 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:20,608 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:20,767 - INFO - Frame 876 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 17:33:20,767 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:20,921 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:21,079 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:21,222 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:21,225 - INFO - Frame 878 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 17:33:21,381 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:21,544 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:21,703 - INFO - Frame 880 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 0
2025-11-24 17:33:21,707 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:21,860 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:22,009 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:22,161 - INFO - Frame 882 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 0
2025-11-24 17:33:22,164 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:22,321 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:22,470 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:22,639 - INFO - Frame 884 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 17:33:22,643 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:22,792 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:22,952 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:23,104 - INFO - Frame 886 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 0
2025-11-24 17:33:23,110 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:23,266 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:23,416 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:23,577 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:23,579 - INFO - Frame 888 | PERCLOS: 0.18 | Yaw: 2.4° | Alerts: 1
2025-11-24 17:33:23,734 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:23,882 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:24,043 - INFO - Frame 890 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 0
2025-11-24 17:33:24,047 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:24,192 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:24,342 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:24,358 - INFO - Frame 892 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 0
2025-11-24 17:33:24,499 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:24,654 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:24,819 - INFO - Frame 894 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 0
2025-11-24 17:33:24,824 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:24,970 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:25,129 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:25,289 - INFO - Frame 896 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 0
2025-11-24 17:33:25,293 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:25,446 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:25,601 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:25,619 - INFO - Frame 898 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 0
2025-11-24 17:33:25,765 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:25,914 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:26,072 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:26,072 - INFO - Frame 900 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 0
2025-11-24 17:33:26,217 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:26,375 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:26,531 - INFO - Frame 902 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 0
2025-11-24 17:33:26,537 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:26,688 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:26,847 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:27,028 - INFO - Frame 904 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 0
2025-11-24 17:33:27,031 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:27,177 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:27,335 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:27,352 - INFO - Frame 906 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 0
2025-11-24 17:33:27,492 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:27,648 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:27,808 - INFO - Frame 908 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 17:33:27,813 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:27,974 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:28,124 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:28,284 - INFO - Frame 910 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 0
2025-11-24 17:33:28,288 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:28,435 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:28,589 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:28,608 - INFO - Frame 912 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-24 17:33:28,746 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:28,902 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:29,064 - INFO - Frame 914 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 0
2025-11-24 17:33:29,069 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:29,218 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:29,381 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:29,543 - INFO - Frame 916 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 17:33:29,543 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:29,700 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:29,857 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:30,015 - INFO - Frame 918 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 0
2025-11-24 17:33:30,021 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:30,170 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:30,326 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:30,478 - INFO - Frame 920 | PERCLOS: 0.57 | Yaw: 3.2° | Alerts: 1
2025-11-24 17:33:30,482 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:30,634 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:30,786 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:30,806 - INFO - Frame 922 | PERCLOS: 0.30 | Yaw: 3.1° | Alerts: 0
2025-11-24 17:33:30,944 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:31,102 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:31,265 - INFO - Frame 924 | PERCLOS: 0.36 | Yaw: 3.1° | Alerts: 1
2025-11-24 17:33:31,269 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:31,425 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:31,583 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:31,744 - INFO - Frame 926 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 0
2025-11-24 17:33:31,750 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:31,908 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:32,061 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:32,224 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:32,228 - INFO - Frame 928 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 1
2025-11-24 17:33:32,383 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:32,538 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:32,699 - INFO - Frame 930 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 17:33:32,700 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:32,858 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:33,007 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:33,166 - INFO - Frame 932 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 0
2025-11-24 17:33:33,171 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:33,324 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:33,483 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:33,624 - INFO - Frame 934 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 0
2025-11-24 17:33:33,628 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:33,800 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:33,956 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:33,975 - INFO - Frame 936 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 0
2025-11-24 17:33:34,116 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:34,268 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:34,429 - INFO - Frame 938 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 0
2025-11-24 17:33:34,432 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:34,576 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:34,732 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:34,748 - INFO - Frame 940 | PERCLOS: 0.00 | Yaw: -2.3° | Alerts: 0
2025-11-24 17:33:34,895 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:35,051 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:35,208 - INFO - Frame 942 | PERCLOS: 0.00 | Yaw: -1.8° | Alerts: 0
2025-11-24 17:33:35,213 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:35,371 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:35,528 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:35,723 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:35,738 - INFO - Frame 944 | PERCLOS: 0.00 | Yaw: -1.3° | Alerts: 0
2025-11-24 17:33:35,881 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:36,039 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:36,196 - INFO - Frame 946 | PERCLOS: 0.00 | Yaw: -1.2° | Alerts: 0
2025-11-24 17:33:36,202 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:36,358 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:36,515 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:36,670 - INFO - Frame 948 | PERCLOS: 0.00 | Yaw: -1.2° | Alerts: 0
2025-11-24 17:33:36,674 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:36,822 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:36,984 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:37,002 - INFO - Frame 950 | PERCLOS: 0.00 | Yaw: -0.9° | Alerts: 0
2025-11-24 17:33:37,135 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:37,284 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:37,452 - INFO - Frame 952 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 0
2025-11-24 17:33:37,457 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:37,613 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:37,758 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:37,914 - INFO - Frame 954 | PERCLOS: 0.00 | Yaw: -0.2° | Alerts: 0
2025-11-24 17:33:37,920 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:38,080 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:38,235 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:38,395 - INFO - Frame 956 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 1
2025-11-24 17:33:38,396 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:38,566 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:38,727 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:38,885 - INFO - Frame 958 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 0
2025-11-24 17:33:38,889 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:39,036 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:39,194 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:39,212 - INFO - Frame 960 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 1
2025-11-24 17:33:39,352 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:39,513 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:39,677 - INFO - Frame 962 | PERCLOS: 0.34 | Yaw: 1.2° | Alerts: 2
2025-11-24 17:33:39,677 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:39,823 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:39,980 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:40,137 - INFO - Frame 964 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 1
2025-11-24 17:33:40,137 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:40,288 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:40,433 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:40,607 - INFO - Frame 966 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 1
2025-11-24 17:33:40,607 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:40,767 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:40,928 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:41,095 - INFO - Frame 968 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 1
2025-11-24 17:33:41,096 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:41,249 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:41,413 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:41,560 - INFO - Frame 970 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 0
2025-11-24 17:33:41,564 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:41,718 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:41,875 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:41,894 - INFO - Frame 972 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 1
2025-11-24 17:33:42,024 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:42,171 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:42,331 - INFO - Frame 974 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 1
2025-11-24 17:33:42,331 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:42,485 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:42,641 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:42,807 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:42,807 - INFO - Frame 976 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 1
2025-11-24 17:33:42,957 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:43,116 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:43,264 - INFO - Frame 978 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 0
2025-11-24 17:33:43,267 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:43,419 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:43,567 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:43,585 - INFO - Frame 980 | PERCLOS: 0.24 | Yaw: 1.1° | Alerts: 1
2025-11-24 17:33:43,721 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:43,877 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:44,038 - INFO - Frame 982 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 1
2025-11-24 17:33:44,042 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:44,193 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:44,340 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:44,505 - INFO - Frame 984 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 0
2025-11-24 17:33:44,510 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:44,655 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:44,810 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:44,969 - INFO - Frame 986 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:33:44,975 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:45,142 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:45,298 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:45,464 - INFO - Frame 988 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 1
2025-11-24 17:33:45,467 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:45,627 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:45,786 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:45,945 - INFO - Frame 990 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 0
2025-11-24 17:33:45,952 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:46,109 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:46,253 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:46,267 - INFO - Frame 992 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 1
2025-11-24 17:33:46,405 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:46,558 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:46,723 - INFO - Frame 994 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 1
2025-11-24 17:33:46,723 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:46,875 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:47,030 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:47,186 - INFO - Frame 996 | PERCLOS: 0.22 | Yaw: 0.9° | Alerts: 1
2025-11-24 17:33:47,188 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:47,350 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:47,503 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:47,654 - INFO - Frame 998 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 1
2025-11-24 17:33:47,656 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:47,804 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:47,959 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:48,112 - INFO - Frame 1000 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 0
2025-11-24 17:33:48,115 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:48,273 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:48,431 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:48,575 - INFO - Frame 1002 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 0
2025-11-24 17:33:48,581 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:48,742 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:48,895 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:48,915 - INFO - Frame 1004 | PERCLOS: 0.00 | Yaw: -1.8° | Alerts: 0
2025-11-24 17:33:49,054 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:49,212 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:49,356 - INFO - Frame 1006 | PERCLOS: 0.00 | Yaw: -1.8° | Alerts: 0
2025-11-24 17:33:49,359 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:49,497 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:49,650 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:49,665 - INFO - Frame 1008 | PERCLOS: 0.00 | Yaw: -1.3° | Alerts: 0
2025-11-24 17:33:49,822 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:49,970 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:50,127 - INFO - Frame 1010 | PERCLOS: 0.00 | Yaw: -1.3° | Alerts: 0
2025-11-24 17:33:50,132 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:50,286 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:50,445 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:50,599 - INFO - Frame 1012 | PERCLOS: 0.00 | Yaw: -1.1° | Alerts: 0
2025-11-24 17:33:50,603 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:50,764 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:50,921 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:51,074 - INFO - Frame 1014 | PERCLOS: 0.00 | Yaw: -1.1° | Alerts: 0
2025-11-24 17:33:51,079 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:51,238 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:51,394 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:51,549 - INFO - Frame 1016 | PERCLOS: 0.00 | Yaw: -0.9° | Alerts: 0
2025-11-24 17:33:51,553 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:51,697 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:51,889 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:52,044 - INFO - Frame 1018 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 0
2025-11-24 17:33:52,050 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:52,210 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:52,367 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:52,530 - INFO - Frame 1020 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 0
2025-11-24 17:33:52,536 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:52,684 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:52,842 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:53,002 - INFO - Frame 1022 | PERCLOS: 0.00 | Yaw: -0.9° | Alerts: 0
2025-11-24 17:33:53,007 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:53,158 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:53,306 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:53,456 - INFO - Frame 1024 | PERCLOS: 0.00 | Yaw: -0.9° | Alerts: 0
2025-11-24 17:33:53,460 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:53,602 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:53,758 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:53,778 - INFO - Frame 1026 | PERCLOS: 0.00 | Yaw: -0.8° | Alerts: 0
2025-11-24 17:33:53,912 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:54,074 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:54,228 - INFO - Frame 1028 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 0
2025-11-24 17:33:54,235 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:54,385 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:54,543 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:54,705 - INFO - Frame 1030 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 0
2025-11-24 17:33:54,710 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:54,856 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:55,007 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:55,161 - INFO - Frame 1032 | PERCLOS: 0.45 | Yaw: -0.4° | Alerts: 1
2025-11-24 17:33:55,166 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:55,317 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:55,469 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:55,623 - INFO - Frame 1034 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 0
2025-11-24 17:33:55,626 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:55,786 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:55,939 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:56,099 - INFO - Frame 1036 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 0
2025-11-24 17:33:56,104 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:56,257 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:56,409 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:56,427 - INFO - Frame 1038 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 0
2025-11-24 17:33:56,567 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:56,741 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:56,892 - INFO - Frame 1040 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 0
2025-11-24 17:33:56,897 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:57,054 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:57,208 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:57,363 - INFO - Frame 1042 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 0
2025-11-24 17:33:57,368 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:57,517 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:57,674 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:57,837 - INFO - Frame 1044 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 0
2025-11-24 17:33:57,840 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:57,995 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:58,148 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:58,166 - INFO - Frame 1046 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 0
2025-11-24 17:33:58,297 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:58,444 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:58,605 - INFO - Frame 1048 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 0
2025-11-24 17:33:58,611 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:58,765 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:58,945 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:59,097 - INFO - Frame 1050 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 0
2025-11-24 17:33:59,103 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:59,253 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:59,409 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:59,567 - INFO - Frame 1052 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 0
2025-11-24 17:33:59,574 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:59,727 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:33:59,878 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:00,035 - INFO - Frame 1054 | PERCLOS: 0.00 | Yaw: -0.0° | Alerts: 0
2025-11-24 17:34:00,039 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:00,184 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:00,346 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:00,363 - INFO - Frame 1056 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 0
2025-11-24 17:34:00,501 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:00,660 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:00,820 - INFO - Frame 1058 | PERCLOS: 0.57 | Yaw: 1.1° | Alerts: 1
2025-11-24 17:34:00,826 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:00,981 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:01,140 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:01,290 - INFO - Frame 1060 | PERCLOS: 0.06 | Yaw: 3.1° | Alerts: 0
2025-11-24 17:34:01,296 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:01,466 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:01,626 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:01,784 - INFO - Frame 1062 | PERCLOS: 0.52 | Yaw: 3.7° | Alerts: 1
2025-11-24 17:34:01,788 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:01,939 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:02,100 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:02,261 - INFO - Frame 1064 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 0
2025-11-24 17:34:02,266 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:02,417 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:02,565 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:02,583 - INFO - Frame 1066 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:34:02,724 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:02,885 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:03,043 - INFO - Frame 1068 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:34:03,047 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:03,201 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:03,356 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:03,373 - INFO - Frame 1070 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:34:03,509 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:03,663 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:03,834 - INFO - Frame 1072 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:34:03,838 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:03,986 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:04,135 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:04,286 - INFO - Frame 1074 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:34:04,290 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:04,434 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:04,586 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:04,747 - INFO - Frame 1076 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:34:04,753 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:04,900 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:05,057 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:05,217 - INFO - Frame 1078 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:34:05,222 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:05,379 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:05,534 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:05,693 - INFO - Frame 1080 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:34:05,698 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:05,856 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:06,013 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:06,184 - INFO - Frame 1082 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:34:06,188 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:06,344 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:06,505 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:06,653 - INFO - Frame 1084 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:34:06,656 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:06,807 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:06,960 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:06,978 - INFO - Frame 1086 | PERCLOS: 0.00 | Yaw: -9.3° | Alerts: 0
2025-11-24 17:34:07,116 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:07,279 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:07,441 - INFO - Frame 1088 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 0
2025-11-24 17:34:07,445 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:07,596 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:07,752 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:07,904 - INFO - Frame 1090 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 0
2025-11-24 17:34:07,910 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:08,065 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:08,222 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:08,406 - INFO - Frame 1092 | PERCLOS: 0.00 | Yaw: 8.1° | Alerts: 0
2025-11-24 17:34:08,412 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:08,562 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:08,734 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:08,883 - INFO - Frame 1094 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:34:08,888 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:09,040 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:09,191 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:09,343 - INFO - Frame 1096 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:34:09,348 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:09,507 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:09,666 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:09,821 - INFO - Frame 1098 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:34:09,822 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:09,971 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:10,134 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:10,279 - INFO - Frame 1100 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:34:10,287 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:10,428 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:10,581 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:10,739 - INFO - Frame 1102 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:34:10,743 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:10,885 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:11,049 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:11,214 - INFO - Frame 1104 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:34:11,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:11,372 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:11,541 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:11,559 - INFO - Frame 1106 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:34:11,694 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:11,852 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:12,016 - INFO - Frame 1108 | PERCLOS: 0.00 | Yaw: 11.1° | Alerts: 0
2025-11-24 17:34:12,021 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:12,173 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:12,321 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:12,478 - INFO - Frame 1110 | PERCLOS: 0.00 | Yaw: 9.5° | Alerts: 0
2025-11-24 17:34:12,484 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:12,632 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:12,779 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:12,940 - INFO - Frame 1112 | PERCLOS: 0.07 | Yaw: 4.6° | Alerts: 0
2025-11-24 17:34:12,947 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:13,099 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:13,257 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:13,431 - INFO - Frame 1114 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 0
2025-11-24 17:34:13,437 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:13,596 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:13,748 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:13,910 - INFO - Frame 1116 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 0
2025-11-24 17:34:13,916 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:14,078 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:14,231 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:14,389 - INFO - Frame 1118 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 0
2025-11-24 17:34:14,393 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:14,540 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:14,689 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:14,712 - INFO - Frame 1120 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 0
2025-11-24 17:34:14,850 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:15,004 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:15,166 - INFO - Frame 1122 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 0
2025-11-24 17:34:15,172 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:15,321 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:15,482 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:15,657 - INFO - Frame 1124 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 0
2025-11-24 17:34:15,660 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:15,811 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:15,964 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:15,982 - INFO - Frame 1126 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 0
2025-11-24 17:34:16,120 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:16,275 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:16,436 - INFO - Frame 1128 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:34:16,440 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:16,598 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:16,755 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:16,922 - INFO - Frame 1130 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:34:16,923 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:17,084 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:17,238 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:17,391 - INFO - Frame 1132 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:34:17,395 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:17,543 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:17,695 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:17,852 - INFO - Frame 1134 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:34:17,855 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:18,018 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:18,177 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:18,195 - INFO - Frame 1136 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:34:18,330 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:18,493 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:18,646 - INFO - Frame 1138 | PERCLOS: 0.00 | Yaw: 11.8° | Alerts: 0
2025-11-24 17:34:18,652 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:18,805 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:18,967 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:19,123 - INFO - Frame 1140 | PERCLOS: 0.00 | Yaw: 9.4° | Alerts: 0
2025-11-24 17:34:19,128 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:19,283 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:19,442 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:19,643 - INFO - Frame 1142 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 0
2025-11-24 17:34:19,648 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:19,796 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:19,954 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:19,969 - INFO - Frame 1144 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 0
2025-11-24 17:34:20,112 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:20,276 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:20,434 - INFO - Frame 1146 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 0
2025-11-24 17:34:20,440 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:20,608 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:20,767 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:20,786 - INFO - Frame 1148 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 0
2025-11-24 17:34:20,933 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:21,091 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:21,240 - INFO - Frame 1150 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 0
2025-11-24 17:34:21,246 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:21,398 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:21,559 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:21,757 - INFO - Frame 1152 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 0
2025-11-24 17:34:21,762 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:21,916 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:22,070 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:22,232 - INFO - Frame 1154 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 0
2025-11-24 17:34:22,237 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:22,403 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:22,556 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:22,572 - INFO - Frame 1156 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:34:22,710 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:22,865 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:23,028 - INFO - Frame 1158 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:34:23,035 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:23,193 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:23,347 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:23,509 - INFO - Frame 1160 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:34:23,514 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:23,672 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:23,825 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:23,989 - INFO - Frame 1162 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:34:23,992 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:24,132 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:24,286 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:24,445 - INFO - Frame 1164 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 0
2025-11-24 17:34:24,449 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:24,606 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:24,761 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:24,776 - INFO - Frame 1166 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:34:24,911 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:25,076 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:25,248 - INFO - Frame 1168 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:34:25,253 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:25,388 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:25,553 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:25,579 - INFO - Frame 1170 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 0
2025-11-24 17:34:25,715 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:25,873 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:26,028 - INFO - Frame 1172 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:34:26,032 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:26,184 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:26,339 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:26,358 - INFO - Frame 1174 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 0
2025-11-24 17:34:26,493 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:26,647 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:26,791 - INFO - Frame 1176 | PERCLOS: 0.16 | Yaw: 11.4° | Alerts: 0
2025-11-24 17:34:26,795 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:26,960 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:27,109 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:27,259 - INFO - Frame 1178 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:34:27,265 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:27,409 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:27,566 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:27,735 - INFO - Frame 1180 | PERCLOS: 0.00 | Yaw: 10.5° | Alerts: 0
2025-11-24 17:34:27,739 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:27,893 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:28,052 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:28,066 - INFO - Frame 1182 | PERCLOS: 0.00 | Yaw: 10.0° | Alerts: 0
2025-11-24 17:34:28,213 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:28,371 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:28,531 - INFO - Frame 1184 | PERCLOS: 0.00 | Yaw: 9.0° | Alerts: 0
2025-11-24 17:34:28,537 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:28,695 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:28,860 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:29,016 - INFO - Frame 1186 | PERCLOS: 0.00 | Yaw: 8.1° | Alerts: 0
2025-11-24 17:34:29,020 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:29,175 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:29,331 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:29,483 - INFO - Frame 1188 | PERCLOS: 0.31 | Yaw: 6.2° | Alerts: 1
2025-11-24 17:34:29,485 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:29,632 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:29,783 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:29,921 - INFO - Frame 1190 | PERCLOS: 0.00 | Yaw: 6.2° | Alerts: 0
2025-11-24 17:34:29,926 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:30,103 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:30,244 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:30,410 - INFO - Frame 1192 | PERCLOS: 0.25 | Yaw: 6.9° | Alerts: 0
2025-11-24 17:34:30,413 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:30,560 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:30,721 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:30,739 - INFO - Frame 1194 | PERCLOS: 0.00 | Yaw: 8.2° | Alerts: 0
2025-11-24 17:34:30,883 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:31,044 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:31,197 - INFO - Frame 1196 | PERCLOS: 0.00 | Yaw: 8.7° | Alerts: 0
2025-11-24 17:34:31,204 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:31,364 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:31,524 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:31,544 - INFO - Frame 1198 | PERCLOS: 0.00 | Yaw: 8.5° | Alerts: 0
2025-11-24 17:34:31,687 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:31,842 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:31,995 - INFO - Frame 1200 | PERCLOS: 0.00 | Yaw: 8.5° | Alerts: 0
2025-11-24 17:34:32,001 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:32,144 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:32,297 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:32,320 - INFO - Frame 1202 | PERCLOS: 0.00 | Yaw: 8.6° | Alerts: 0
2025-11-24 17:34:32,451 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:32,626 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:32,779 - INFO - Frame 1204 | PERCLOS: 0.00 | Yaw: 8.5° | Alerts: 0
2025-11-24 17:34:32,785 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:32,929 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:33,088 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:33,109 - INFO - Frame 1206 | PERCLOS: 0.00 | Yaw: 8.4° | Alerts: 0
2025-11-24 17:34:33,243 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:33,401 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:33,562 - INFO - Frame 1208 | PERCLOS: 0.00 | Yaw: 8.1° | Alerts: 0
2025-11-24 17:34:33,567 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:33,729 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:33,884 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:34,051 - INFO - Frame 1210 | PERCLOS: 0.00 | Yaw: 8.3° | Alerts: 0
2025-11-24 17:34:34,052 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:34,212 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:34,367 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:34,529 - INFO - Frame 1212 | PERCLOS: 0.00 | Yaw: 8.2° | Alerts: 0
2025-11-24 17:34:34,533 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:34,692 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:34,862 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:35,023 - INFO - Frame 1214 | PERCLOS: 0.00 | Yaw: 8.7° | Alerts: 0
2025-11-24 17:34:35,028 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:35,187 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:35,345 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:35,505 - INFO - Frame 1216 | PERCLOS: 0.00 | Yaw: 9.5° | Alerts: 0
2025-11-24 17:34:35,507 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:35,661 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:35,817 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:35,968 - INFO - Frame 1218 | PERCLOS: 0.00 | Yaw: 11.0° | Alerts: 0
2025-11-24 17:34:35,973 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:36,127 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:36,285 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:36,447 - INFO - Frame 1220 | PERCLOS: 0.00 | Yaw: 10.7° | Alerts: 0
2025-11-24 17:34:36,448 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:36,601 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:36,763 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:36,914 - INFO - Frame 1222 | PERCLOS: 0.00 | Yaw: 10.8° | Alerts: 0
2025-11-24 17:34:36,919 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:37,074 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:37,225 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:37,241 - INFO - Frame 1224 | PERCLOS: 0.00 | Yaw: 10.8° | Alerts: 0
2025-11-24 17:34:37,401 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:37,551 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:37,710 - INFO - Frame 1226 | PERCLOS: 0.00 | Yaw: 10.9° | Alerts: 0
2025-11-24 17:34:37,714 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:37,867 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:38,024 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:38,039 - INFO - Frame 1228 | PERCLOS: 0.00 | Yaw: 10.5° | Alerts: 0
2025-11-24 17:34:38,174 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:38,329 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:38,491 - INFO - Frame 1230 | PERCLOS: 0.00 | Yaw: 10.9° | Alerts: 0
2025-11-24 17:34:38,495 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:38,644 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:38,800 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:38,953 - INFO - Frame 1232 | PERCLOS: 0.00 | Yaw: 11.4° | Alerts: 0
2025-11-24 17:34:38,958 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:39,102 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:39,267 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:39,284 - INFO - Frame 1234 | PERCLOS: 0.00 | Yaw: 11.0° | Alerts: 0
2025-11-24 17:34:39,430 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:39,591 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:39,751 - INFO - Frame 1236 | PERCLOS: 0.00 | Yaw: 11.1° | Alerts: 0
2025-11-24 17:34:39,758 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:39,910 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:40,071 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:40,228 - INFO - Frame 1238 | PERCLOS: 0.00 | Yaw: 11.9° | Alerts: 0
2025-11-24 17:34:40,235 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:40,392 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:40,553 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:40,711 - INFO - Frame 1240 | PERCLOS: 0.00 | Yaw: 11.5° | Alerts: 0
2025-11-24 17:34:40,717 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:40,874 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:41,035 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:41,193 - INFO - Frame 1242 | PERCLOS: 0.00 | Yaw: 11.4° | Alerts: 0
2025-11-24 17:34:41,197 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:41,352 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:41,499 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:41,515 - INFO - Frame 1244 | PERCLOS: 0.00 | Yaw: 11.3° | Alerts: 0
2025-11-24 17:34:41,658 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:41,813 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:41,978 - INFO - Frame 1246 | PERCLOS: 0.00 | Yaw: 11.2° | Alerts: 0
2025-11-24 17:34:41,985 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:42,154 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:42,311 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:42,472 - INFO - Frame 1248 | PERCLOS: 0.00 | Yaw: 11.5° | Alerts: 0
2025-11-24 17:34:42,477 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:42,631 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:42,782 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:42,942 - INFO - Frame 1250 | PERCLOS: 0.00 | Yaw: 11.1° | Alerts: 0
2025-11-24 17:34:42,947 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:43,096 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:43,251 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:43,410 - INFO - Frame 1252 | PERCLOS: 0.00 | Yaw: 12.5° | Alerts: 0
2025-11-24 17:34:43,415 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:43,571 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:43,727 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:43,881 - INFO - Frame 1254 | PERCLOS: 0.00 | Yaw: 12.4° | Alerts: 0
2025-11-24 17:34:43,885 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:44,040 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:44,205 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:44,224 - INFO - Frame 1256 | PERCLOS: 0.00 | Yaw: 12.1° | Alerts: 0
2025-11-24 17:34:44,364 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:44,520 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:44,674 - INFO - Frame 1258 | PERCLOS: 0.00 | Yaw: 11.9° | Alerts: 0
2025-11-24 17:34:44,677 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:44,830 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:44,987 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:45,005 - INFO - Frame 1260 | PERCLOS: 0.00 | Yaw: 10.3° | Alerts: 0
2025-11-24 17:34:45,141 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:45,299 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:45,456 - INFO - Frame 1262 | PERCLOS: 0.00 | Yaw: 7.4° | Alerts: 0
2025-11-24 17:34:45,461 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:45,605 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:45,765 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:45,778 - INFO - Frame 1264 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 0
2025-11-24 17:34:45,931 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:46,088 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:46,246 - INFO - Frame 1266 | PERCLOS: 0.31 | Yaw: -6.0° | Alerts: 1
2025-11-24 17:34:46,246 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:46,405 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:46,576 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:46,730 - INFO - Frame 1268 | PERCLOS: 0.00 | Yaw: -9.4° | Alerts: 0
2025-11-24 17:34:46,734 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:46,884 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:47,040 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:47,200 - INFO - Frame 1270 | PERCLOS: 0.00 | Yaw: -12.8° | Alerts: 0
2025-11-24 17:34:47,202 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:47,361 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:47,517 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:47,672 - INFO - Frame 1272 | PERCLOS: 0.14 | Yaw: -8.2° | Alerts: 0
2025-11-24 17:34:47,676 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:47,832 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:47,980 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:47,999 - INFO - Frame 1274 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 0
2025-11-24 17:34:48,138 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:48,283 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:48,433 - INFO - Frame 1276 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 0
2025-11-24 17:34:48,438 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:48,592 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:48,745 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:48,909 - INFO - Frame 1278 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 0
2025-11-24 17:34:48,915 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:49,104 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:49,262 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:49,285 - INFO - Frame 1280 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 0
2025-11-24 17:34:49,419 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:49,578 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:49,738 - INFO - Frame 1282 | PERCLOS: 0.00 | Yaw: 4.7° | Alerts: 0
2025-11-24 17:34:49,744 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:49,891 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:50,052 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:50,210 - INFO - Frame 1284 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 0
2025-11-24 17:34:50,215 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:50,372 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:50,523 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:50,677 - INFO - Frame 1286 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 0
2025-11-24 17:34:50,683 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:50,835 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:50,984 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:51,148 - INFO - Frame 1288 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 0
2025-11-24 17:34:51,155 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:51,318 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:51,468 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:51,628 - INFO - Frame 1290 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 0
2025-11-24 17:34:51,633 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:51,781 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:51,937 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:51,954 - INFO - Frame 1292 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 0
2025-11-24 17:34:52,097 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:52,258 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:52,415 - INFO - Frame 1294 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 0
2025-11-24 17:34:52,418 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:52,566 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:52,723 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:52,737 - INFO - Frame 1296 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 0
2025-11-24 17:34:52,884 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:53,039 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:53,199 - INFO - Frame 1298 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 0
2025-11-24 17:34:53,200 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:53,349 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:53,502 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:53,668 - INFO - Frame 1300 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 0
2025-11-24 17:34:53,672 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:53,821 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:53,984 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:54,002 - INFO - Frame 1302 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 0
2025-11-24 17:34:54,145 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:54,307 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:54,470 - INFO - Frame 1304 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 0
2025-11-24 17:34:54,474 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:54,636 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:54,794 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:54,955 - INFO - Frame 1306 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 0
2025-11-24 17:34:54,960 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:55,110 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:55,261 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:55,417 - INFO - Frame 1308 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 0
2025-11-24 17:34:55,423 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:55,579 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:55,732 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:55,907 - INFO - Frame 1310 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 0
2025-11-24 17:34:55,913 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:56,067 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:56,219 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:56,382 - INFO - Frame 1312 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 0
2025-11-24 17:34:56,385 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:56,535 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:56,695 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:56,852 - INFO - Frame 1314 | PERCLOS: 0.03 | Yaw: 5.5° | Alerts: 0
2025-11-24 17:34:56,854 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:57,003 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:57,161 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:57,319 - INFO - Frame 1316 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 0
2025-11-24 17:34:57,325 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:57,477 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:57,632 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:57,786 - INFO - Frame 1318 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 0
2025-11-24 17:34:57,789 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:57,936 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:58,091 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:58,105 - INFO - Frame 1320 | PERCLOS: 0.63 | Yaw: 1.1° | Alerts: 1
2025-11-24 17:34:58,267 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:58,437 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:58,577 - INFO - Frame 1322 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 0
2025-11-24 17:34:58,581 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:58,749 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:58,906 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:58,925 - INFO - Frame 1324 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 0
2025-11-24 17:34:59,065 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:59,225 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:59,384 - INFO - Frame 1326 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:34:59,387 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:59,530 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:59,684 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:34:59,842 - INFO - Frame 1328 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 0
2025-11-24 17:34:59,849 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:00,000 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:00,163 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:00,326 - INFO - Frame 1330 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:35:00,330 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:00,487 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:00,650 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:00,807 - INFO - Frame 1332 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:35:00,811 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:00,974 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:01,133 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:01,155 - INFO - Frame 1334 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:35:01,285 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:01,443 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:01,603 - INFO - Frame 1336 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:35:01,606 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:01,752 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:01,916 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:01,933 - INFO - Frame 1338 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:35:02,073 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:02,229 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:02,388 - INFO - Frame 1340 | PERCLOS: 0.47 | Yaw: 1.3° | Alerts: 1
2025-11-24 17:35:02,393 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:02,550 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:02,711 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:02,866 - INFO - Frame 1342 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 0
2025-11-24 17:35:02,871 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:03,046 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:03,207 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:03,365 - INFO - Frame 1344 | PERCLOS: 0.02 | Yaw: 1.1° | Alerts: 0
2025-11-24 17:35:03,371 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:03,532 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:03,684 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:03,847 - INFO - Frame 1346 | PERCLOS: 0.00 | Yaw: -2.3° | Alerts: 0
2025-11-24 17:35:03,852 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:04,005 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:04,163 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:04,177 - INFO - Frame 1348 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 0
2025-11-24 17:35:04,322 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:04,480 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:04,633 - INFO - Frame 1350 | PERCLOS: 0.00 | Yaw: 9.0° | Alerts: 0
2025-11-24 17:35:04,639 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:04,793 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:04,942 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:05,107 - INFO - Frame 1352 | PERCLOS: 0.00 | Yaw: 9.8° | Alerts: 0
2025-11-24 17:35:05,112 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:05,273 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:05,441 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:05,614 - INFO - Frame 1354 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:35:05,616 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:05,771 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:05,963 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:05,982 - INFO - Frame 1356 | PERCLOS: 0.34 | Yaw: 8.8° | Alerts: 1
2025-11-24 17:35:06,119 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:06,282 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:06,444 - INFO - Frame 1358 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 0
2025-11-24 17:35:06,449 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:06,609 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:06,768 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:06,932 - INFO - Frame 1360 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 0
2025-11-24 17:35:06,934 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:07,080 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:07,238 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:07,389 - INFO - Frame 1362 | PERCLOS: 0.00 | Yaw: 4.7° | Alerts: 0
2025-11-24 17:35:07,392 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:07,545 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:07,707 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:07,875 - INFO - Frame 1364 | PERCLOS: 0.00 | Yaw: 6.7° | Alerts: 0
2025-11-24 17:35:07,881 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:08,045 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:08,197 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:08,352 - INFO - Frame 1366 | PERCLOS: 0.40 | Yaw: 6.6° | Alerts: 1
2025-11-24 17:35:08,357 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:08,510 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:08,664 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:08,819 - INFO - Frame 1368 | PERCLOS: 0.00 | Yaw: 4.8° | Alerts: 0
2025-11-24 17:35:08,823 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:08,967 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:09,125 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:09,282 - INFO - Frame 1370 | PERCLOS: 0.24 | Yaw: 4.0° | Alerts: 0
2025-11-24 17:35:09,289 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:09,446 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:09,598 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:09,752 - INFO - Frame 1372 | PERCLOS: 0.10 | Yaw: 4.4° | Alerts: 0
2025-11-24 17:35:09,758 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:09,917 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:10,086 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:10,253 - INFO - Frame 1374 | PERCLOS: 0.06 | Yaw: 4.5° | Alerts: 0
2025-11-24 17:35:10,256 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:10,413 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:10,570 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:10,730 - INFO - Frame 1376 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 0
2025-11-24 17:35:10,734 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:10,877 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:11,045 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:11,062 - INFO - Frame 1378 | PERCLOS: 0.04 | Yaw: 4.5° | Alerts: 0
2025-11-24 17:35:11,198 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:11,361 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:11,522 - INFO - Frame 1380 | PERCLOS: 0.07 | Yaw: 4.5° | Alerts: 0
2025-11-24 17:35:11,524 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:11,676 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:11,836 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:11,997 - INFO - Frame 1382 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 0
2025-11-24 17:35:11,998 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:12,153 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:12,302 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:12,465 - INFO - Frame 1384 | PERCLOS: 0.00 | Yaw: 4.7° | Alerts: 0
2025-11-24 17:35:12,469 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:12,622 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:12,788 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:12,946 - INFO - Frame 1386 | PERCLOS: 0.00 | Yaw: 5.1° | Alerts: 0
2025-11-24 17:35:12,949 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:13,105 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:13,269 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:13,429 - INFO - Frame 1388 | PERCLOS: 0.77 | Yaw: 5.7° | Alerts: 1
2025-11-24 17:35:13,431 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:13,595 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:13,755 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:13,910 - INFO - Frame 1390 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 0
2025-11-24 17:35:13,914 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:14,058 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:14,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:14,233 - INFO - Frame 1392 | PERCLOS: 0.79 | Yaw: 6.5° | Alerts: 1
2025-11-24 17:35:14,376 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:14,530 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:14,697 - INFO - Frame 1394 | PERCLOS: 0.00 | Yaw: 9.0° | Alerts: 0
2025-11-24 17:35:14,701 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:14,853 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:15,011 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:15,185 - INFO - Frame 1396 | PERCLOS: 0.11 | Yaw: 9.4° | Alerts: 0
2025-11-24 17:35:15,191 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:15,335 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:15,496 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:15,654 - INFO - Frame 1398 | PERCLOS: 0.00 | Yaw: 9.2° | Alerts: 0
2025-11-24 17:35:15,660 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:15,817 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:15,971 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:16,121 - INFO - Frame 1400 | PERCLOS: 0.00 | Yaw: 8.8° | Alerts: 0
2025-11-24 17:35:16,127 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:16,284 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:16,443 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:16,580 - INFO - Frame 1402 | PERCLOS: 0.00 | Yaw: 9.2° | Alerts: 0
2025-11-24 17:35:16,585 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:16,731 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:16,889 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:17,043 - INFO - Frame 1404 | PERCLOS: 0.00 | Yaw: 8.8° | Alerts: 0
2025-11-24 17:35:17,050 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:17,200 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:17,351 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:17,368 - INFO - Frame 1406 | PERCLOS: 0.00 | Yaw: 9.0° | Alerts: 0
2025-11-24 17:35:17,510 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:17,674 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:17,847 - INFO - Frame 1408 | PERCLOS: 0.00 | Yaw: 8.9° | Alerts: 0
2025-11-24 17:35:17,848 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:18,009 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:18,159 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:18,315 - INFO - Frame 1410 | PERCLOS: 0.00 | Yaw: 8.5° | Alerts: 0
2025-11-24 17:35:18,319 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:18,471 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:18,620 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:18,636 - INFO - Frame 1412 | PERCLOS: 0.00 | Yaw: 8.3° | Alerts: 0
2025-11-24 17:35:18,780 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:18,941 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:19,094 - INFO - Frame 1414 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 0
2025-11-24 17:35:19,100 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:19,251 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:19,406 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:19,615 - INFO - Frame 1416 | PERCLOS: 0.00 | Yaw: -3.6° | Alerts: 0
2025-11-24 17:35:19,621 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:19,797 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:19,960 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:20,115 - INFO - Frame 1418 | PERCLOS: 0.60 | Yaw: -5.9° | Alerts: 1
2025-11-24 17:35:20,121 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:20,278 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:20,447 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:20,615 - INFO - Frame 1420 | PERCLOS: 0.61 | Yaw: -5.6° | Alerts: 1
2025-11-24 17:35:20,620 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:20,775 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:20,935 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:21,092 - INFO - Frame 1422 | PERCLOS: 0.71 | Yaw: -5.4° | Alerts: 1
2025-11-24 17:35:21,095 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:21,252 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:21,400 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:21,568 - INFO - Frame 1424 | PERCLOS: 0.65 | Yaw: -5.2° | Alerts: 1
2025-11-24 17:35:21,573 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:21,733 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:21,899 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:22,050 - INFO - Frame 1426 | PERCLOS: 0.50 | Yaw: -5.1° | Alerts: 1
2025-11-24 17:35:22,055 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:22,215 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:22,378 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:22,534 - INFO - Frame 1428 | PERCLOS: 0.00 | Yaw: -2.8° | Alerts: 0
2025-11-24 17:35:22,540 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:22,706 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:22,870 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:23,017 - INFO - Frame 1430 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 0
2025-11-24 17:35:23,020 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:23,179 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:23,327 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:23,492 - INFO - Frame 1432 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 0
2025-11-24 17:35:23,493 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:23,650 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:23,812 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:23,970 - INFO - Frame 1434 | PERCLOS: 0.00 | Yaw: 0.2° | Alerts: 0
2025-11-24 17:35:23,975 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:24,126 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:24,282 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:24,296 - INFO - Frame 1436 | PERCLOS: 0.00 | Yaw: -0.2° | Alerts: 0
2025-11-24 17:35:24,444 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:24,608 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:24,764 - INFO - Frame 1438 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 0
2025-11-24 17:35:24,770 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:24,921 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:25,073 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:25,238 - INFO - Frame 1440 | PERCLOS: 0.00 | Yaw: -0.8° | Alerts: 0
2025-11-24 17:35:25,241 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:25,400 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:25,552 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:25,570 - INFO - Frame 1442 | PERCLOS: 0.12 | Yaw: -0.6° | Alerts: 0
2025-11-24 17:35:25,709 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:25,865 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:26,026 - INFO - Frame 1444 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 0
2025-11-24 17:35:26,032 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:26,188 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:26,343 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:26,508 - INFO - Frame 1446 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 0
2025-11-24 17:35:26,512 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:26,655 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:26,811 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:26,828 - INFO - Frame 1448 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 0
2025-11-24 17:35:26,973 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:27,135 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:27,284 - INFO - Frame 1450 | PERCLOS: 0.11 | Yaw: -0.5° | Alerts: 0
2025-11-24 17:35:27,291 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:27,438 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:27,589 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:27,756 - INFO - Frame 1452 | PERCLOS: 0.20 | Yaw: -0.5° | Alerts: 0
2025-11-24 17:35:27,761 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:27,916 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:28,077 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:28,244 - INFO - Frame 1454 | PERCLOS: 0.22 | Yaw: -0.6° | Alerts: 0
2025-11-24 17:35:28,245 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:28,403 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:28,560 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:28,722 - INFO - Frame 1456 | PERCLOS: 0.27 | Yaw: -0.7° | Alerts: 0
2025-11-24 17:35:28,727 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:28,889 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:29,036 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:29,057 - INFO - Frame 1458 | PERCLOS: 0.11 | Yaw: -0.5° | Alerts: 0
2025-11-24 17:35:29,203 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:29,366 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:29,510 - INFO - Frame 1460 | PERCLOS: 0.49 | Yaw: -0.6° | Alerts: 1
2025-11-24 17:35:29,515 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:29,682 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:29,837 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:30,001 - INFO - Frame 1462 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 0
2025-11-24 17:35:30,007 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:30,166 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:30,328 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:30,501 - INFO - Frame 1464 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 0
2025-11-24 17:35:30,507 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:30,656 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:30,827 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:30,988 - INFO - Frame 1466 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 0
2025-11-24 17:35:30,992 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:31,144 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:31,306 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:31,319 - INFO - Frame 1468 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 0
2025-11-24 17:35:31,464 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:31,616 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:31,774 - INFO - Frame 1470 | PERCLOS: 0.01 | Yaw: -0.5° | Alerts: 0
2025-11-24 17:35:31,778 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:31,931 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:32,084 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:32,099 - INFO - Frame 1472 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 0
2025-11-24 17:35:32,237 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:32,381 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:32,539 - INFO - Frame 1474 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 0
2025-11-24 17:35:32,545 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:32,696 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:32,867 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:33,036 - INFO - Frame 1476 | PERCLOS: 0.00 | Yaw: -0.8° | Alerts: 0
2025-11-24 17:35:33,040 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:33,191 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:33,351 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:33,366 - INFO - Frame 1478 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 0
2025-11-24 17:35:33,510 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:33,672 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:33,829 - INFO - Frame 1480 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 0
2025-11-24 17:35:33,833 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:33,982 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:34,135 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:34,291 - INFO - Frame 1482 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 0
2025-11-24 17:35:34,296 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:34,451 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:34,625 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:34,806 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:34,820 - INFO - Frame 1484 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 0
2025-11-24 17:35:34,965 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:35,126 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:35,271 - INFO - Frame 1486 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 0
2025-11-24 17:35:35,277 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:35,431 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:35,597 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:35,765 - INFO - Frame 1488 | PERCLOS: 0.00 | Yaw: -0.9° | Alerts: 0
2025-11-24 17:35:35,769 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:35,925 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:36,081 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:36,101 - INFO - Frame 1490 | PERCLOS: 0.00 | Yaw: -0.8° | Alerts: 0
2025-11-24 17:35:36,236 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:36,390 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:36,548 - INFO - Frame 1492 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 0
2025-11-24 17:35:36,554 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:36,704 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:36,856 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:37,012 - INFO - Frame 1494 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 0
2025-11-24 17:35:37,016 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:37,169 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:37,338 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:37,352 - INFO - Frame 1496 | PERCLOS: 0.54 | Yaw: -0.3° | Alerts: 1
2025-11-24 17:35:37,498 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:37,661 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:37,822 - INFO - Frame 1498 | PERCLOS: 0.63 | Yaw: -0.4° | Alerts: 1
2025-11-24 17:35:37,825 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:37,970 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:38,139 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:38,161 - INFO - Frame 1500 | PERCLOS: 0.33 | Yaw: -0.4° | Alerts: 1
2025-11-24 17:35:38,305 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:38,465 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:38,625 - INFO - Frame 1502 | PERCLOS: 0.26 | Yaw: -0.2° | Alerts: 0
2025-11-24 17:35:38,629 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:38,779 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:38,936 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:38,950 - INFO - Frame 1504 | PERCLOS: 0.38 | Yaw: -0.4° | Alerts: 1
2025-11-24 17:35:39,087 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:39,254 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:39,408 - INFO - Frame 1506 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 0
2025-11-24 17:35:39,413 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:39,566 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:39,719 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:39,874 - INFO - Frame 1508 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 0
2025-11-24 17:35:39,880 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:40,024 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:40,192 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:40,208 - INFO - Frame 1510 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 0
2025-11-24 17:35:40,356 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:40,512 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:40,669 - INFO - Frame 1512 | PERCLOS: 0.10 | Yaw: -0.0° | Alerts: 0
2025-11-24 17:35:40,676 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:40,848 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:41,007 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:41,154 - INFO - Frame 1514 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 0
2025-11-24 17:35:41,156 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:41,311 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:41,466 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:41,627 - INFO - Frame 1516 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 0
2025-11-24 17:35:41,633 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:41,795 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:41,952 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:42,109 - INFO - Frame 1518 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 0
2025-11-24 17:35:42,114 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:42,270 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:42,434 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:42,592 - INFO - Frame 1520 | PERCLOS: 0.47 | Yaw: -0.9° | Alerts: 1
2025-11-24 17:35:42,596 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:42,751 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:42,912 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:43,073 - INFO - Frame 1522 | PERCLOS: 0.24 | Yaw: -1.6° | Alerts: 0
2025-11-24 17:35:43,077 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:43,238 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:43,398 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:43,414 - INFO - Frame 1524 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:35:43,554 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:43,714 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:43,876 - INFO - Frame 1526 | PERCLOS: 0.65 | Yaw: 1.1° | Alerts: 1
2025-11-24 17:35:43,879 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:44,035 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:44,191 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:44,343 - INFO - Frame 1528 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:35:44,347 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:44,503 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:44,654 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:44,670 - INFO - Frame 1530 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 0
2025-11-24 17:35:44,817 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:44,965 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:45,126 - INFO - Frame 1532 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 0
2025-11-24 17:35:45,132 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:45,291 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:45,445 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:45,612 - INFO - Frame 1534 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 0
2025-11-24 17:35:45,618 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:45,786 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:45,935 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:46,095 - INFO - Frame 1536 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 0
2025-11-24 17:35:46,097 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:46,250 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:46,409 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:46,429 - INFO - Frame 1538 | PERCLOS: 0.35 | Yaw: 4.3° | Alerts: 1
2025-11-24 17:35:46,561 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:46,715 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:46,874 - INFO - Frame 1540 | PERCLOS: 0.00 | Yaw: 5.1° | Alerts: 0
2025-11-24 17:35:46,876 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:47,036 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:47,190 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:47,344 - INFO - Frame 1542 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 0
2025-11-24 17:35:47,351 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:47,500 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:47,655 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:47,820 - INFO - Frame 1544 | PERCLOS: 0.37 | Yaw: 6.3° | Alerts: 1
2025-11-24 17:35:47,824 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:47,974 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:48,147 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:48,312 - INFO - Frame 1546 | PERCLOS: 0.00 | Yaw: 6.5° | Alerts: 0
2025-11-24 17:35:48,317 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:48,476 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:48,635 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:48,795 - INFO - Frame 1548 | PERCLOS: 0.00 | Yaw: 7.5° | Alerts: 0
2025-11-24 17:35:48,800 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:48,958 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:49,119 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:49,280 - INFO - Frame 1550 | PERCLOS: 0.00 | Yaw: 7.3° | Alerts: 0
2025-11-24 17:35:49,285 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:49,435 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:49,588 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:49,604 - INFO - Frame 1552 | PERCLOS: 0.00 | Yaw: 9.0° | Alerts: 0
2025-11-24 17:35:49,747 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:49,899 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:50,055 - INFO - Frame 1554 | PERCLOS: 0.00 | Yaw: 9.2° | Alerts: 0
2025-11-24 17:35:50,061 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:50,211 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:50,365 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:50,534 - INFO - Frame 1556 | PERCLOS: 0.00 | Yaw: 9.4° | Alerts: 0
2025-11-24 17:35:50,540 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:50,697 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:50,851 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:51,013 - INFO - Frame 1558 | PERCLOS: 0.10 | Yaw: 8.6° | Alerts: 0
2025-11-24 17:35:51,016 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:51,183 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:51,351 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:51,517 - INFO - Frame 1560 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 0
2025-11-24 17:35:51,521 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:51,679 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:51,828 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:51,989 - INFO - Frame 1562 | PERCLOS: 0.00 | Yaw: 4.1° | Alerts: 0
2025-11-24 17:35:51,991 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:52,146 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:52,304 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:52,452 - INFO - Frame 1564 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 0
2025-11-24 17:35:52,458 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:52,613 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:52,776 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:52,937 - INFO - Frame 1566 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 0
2025-11-24 17:35:52,937 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:53,106 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:53,262 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:53,282 - INFO - Frame 1568 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 0
2025-11-24 17:35:53,424 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:53,580 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:53,747 - INFO - Frame 1570 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 0
2025-11-24 17:35:53,753 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:53,907 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:54,062 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:54,216 - INFO - Frame 1572 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 0
2025-11-24 17:35:54,222 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:54,378 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:54,541 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:54,699 - INFO - Frame 1574 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 0
2025-11-24 17:35:54,702 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:54,860 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:55,004 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:55,160 - INFO - Frame 1576 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 0
2025-11-24 17:35:55,167 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:55,329 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:55,493 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:55,658 - INFO - Frame 1578 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 0
2025-11-24 17:35:55,666 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:55,846 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:56,013 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:56,155 - INFO - Frame 1580 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 0
2025-11-24 17:35:56,163 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:56,317 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:56,476 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:56,493 - INFO - Frame 1582 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 0
2025-11-24 17:35:56,616 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:35:56,944 - INFO - Frame 1584 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 0
2025-11-24 17:35:57,222 - INFO - Frame 1586 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 0
2025-11-24 17:35:57,500 - INFO - Frame 1588 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 0
2025-11-24 17:35:57,793 - INFO - Frame 1590 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 0
2025-11-24 17:35:58,074 - INFO - Frame 1592 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 0
2025-11-24 17:35:58,365 - INFO - Frame 1594 | PERCLOS: 0.36 | Yaw: 2.9° | Alerts: 1
2025-11-24 17:35:58,650 - INFO - Frame 1596 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 0
2025-11-24 17:35:58,860 - INFO - Frame 1598 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 0
2025-11-24 17:35:59,139 - INFO - Frame 1600 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 0
2025-11-24 17:35:59,422 - INFO - Frame 1602 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 0
2025-11-24 17:35:59,715 - INFO - Frame 1604 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 0
2025-11-24 17:35:59,924 - INFO - Frame 1606 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 0
2025-11-24 17:36:00,202 - INFO - Frame 1608 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 0
2025-11-24 17:36:00,500 - INFO - Frame 1610 | PERCLOS: 0.00 | Yaw: 0.2° | Alerts: 0
2025-11-24 17:36:00,791 - INFO - Frame 1612 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 0
2025-11-24 17:36:01,084 - INFO - Frame 1614 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 0
2025-11-24 17:36:01,367 - INFO - Frame 1616 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 0
2025-11-24 17:36:01,579 - INFO - Frame 1618 | PERCLOS: 0.00 | Yaw: -0.2° | Alerts: 0
2025-11-24 17:36:01,850 - INFO - Frame 1620 | PERCLOS: 0.00 | Yaw: -0.0° | Alerts: 0
2025-11-24 17:36:02,127 - INFO - Frame 1622 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 0
2025-11-24 17:36:02,402 - INFO - Frame 1624 | PERCLOS: 0.00 | Yaw: -0.0° | Alerts: 0
2025-11-24 17:36:02,693 - INFO - Frame 1626 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 0
2025-11-24 17:36:02,980 - INFO - Frame 1628 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 0
2025-11-24 17:36:03,261 - INFO - Frame 1630 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 0
2025-11-24 17:36:03,553 - INFO - Frame 1632 | PERCLOS: 0.00 | Yaw: 0.2° | Alerts: 0
2025-11-24 17:36:03,768 - INFO - Frame 1634 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 0
2025-11-24 17:36:04,040 - INFO - Frame 1636 | PERCLOS: 0.05 | Yaw: 0.1° | Alerts: 0
2025-11-24 17:36:04,248 - INFO - Frame 1638 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 0
2025-11-24 17:36:04,521 - INFO - Frame 1640 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 0
2025-11-24 17:36:04,743 - INFO - Frame 1642 | PERCLOS: 0.00 | Yaw: -0.0° | Alerts: 0
2025-11-24 17:36:05,000 - INFO - Frame 1644 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 0
2025-11-24 17:36:05,204 - INFO - Frame 1646 | PERCLOS: 0.00 | Yaw: 0.2° | Alerts: 0
2025-11-24 17:36:05,471 - INFO - Frame 1648 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 0
2025-11-24 17:36:05,763 - INFO - Frame 1650 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 0
2025-11-24 17:36:06,065 - INFO - Frame 1652 | PERCLOS: 0.00 | Yaw: 0.2° | Alerts: 0
2025-11-24 17:36:06,348 - INFO - Frame 1654 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 0
2025-11-24 17:36:06,631 - INFO - Frame 1656 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 0
2025-11-24 17:36:06,914 - INFO - Frame 1658 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 0
2025-11-24 17:36:07,185 - INFO - Frame 1660 | PERCLOS: 0.00 | Yaw: 0.2° | Alerts: 0
2025-11-24 17:36:07,475 - INFO - Frame 1662 | PERCLOS: 0.00 | Yaw: -0.0° | Alerts: 0
2025-11-24 17:36:07,764 - INFO - Frame 1664 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 0
2025-11-24 17:36:08,056 - INFO - Frame 1666 | PERCLOS: 0.00 | Yaw: -0.0° | Alerts: 0
2025-11-24 17:36:08,340 - INFO - Frame 1668 | PERCLOS: 0.00 | Yaw: -0.0° | Alerts: 0
2025-11-24 17:36:08,621 - INFO - Frame 1670 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 0
2025-11-24 17:36:08,894 - INFO - Frame 1672 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 0
2025-11-24 17:36:09,179 - INFO - Frame 1674 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 0
2025-11-24 17:36:09,462 - INFO - Frame 1676 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 0
2025-11-24 17:36:09,759 - INFO - Frame 1678 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 0
2025-11-24 17:36:10,062 - INFO - Frame 1680 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 0
2025-11-24 17:36:10,347 - INFO - Frame 1682 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 0
2025-11-24 17:36:10,615 - INFO - Frame 1684 | PERCLOS: 0.13 | Yaw: 3.6° | Alerts: 0
2025-11-24 17:36:10,905 - INFO - Frame 1686 | PERCLOS: 0.00 | Yaw: 6.2° | Alerts: 0
2025-11-24 17:36:11,175 - INFO - Frame 1688 | PERCLOS: 0.00 | Yaw: 6.7° | Alerts: 0
2025-11-24 17:36:11,447 - INFO - Frame 1690 | PERCLOS: 0.00 | Yaw: 6.6° | Alerts: 0
2025-11-24 17:36:11,729 - INFO - Frame 1692 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 0
2025-11-24 17:36:12,005 - INFO - Frame 1694 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 0
2025-11-24 17:36:12,278 - INFO - Frame 1696 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:36:12,558 - INFO - Frame 1698 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:36:12,712 - INFO - Frame 1700 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 0
2025-11-24 17:36:12,868 - INFO - Frame 1702 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 0
2025-11-24 17:36:12,897 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:12,995 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:13,095 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:13,185 - INFO - Frame 1704 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 0
2025-11-24 17:36:13,188 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:13,284 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:13,386 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:13,490 - INFO - Frame 1706 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 0
2025-11-24 17:36:13,493 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:13,590 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:13,690 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:13,783 - INFO - Frame 1708 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 0
2025-11-24 17:36:13,786 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:13,874 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:13,967 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:14,062 - INFO - Frame 1710 | PERCLOS: 0.57 | Yaw: -0.3° | Alerts: 1
2025-11-24 17:36:14,064 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:14,195 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:14,315 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:14,414 - INFO - Frame 1712 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:14,416 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:14,514 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:14,619 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:14,709 - INFO - Frame 1714 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 0
2025-11-24 17:36:14,710 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:14,798 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:14,886 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:14,981 - INFO - Frame 1716 | PERCLOS: 0.00 | Yaw: 5.2° | Alerts: 0
2025-11-24 17:36:14,983 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:15,076 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:15,174 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:15,194 - INFO - Frame 1718 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 0
2025-11-24 17:36:15,269 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:15,369 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:15,468 - INFO - Frame 1720 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 0
2025-11-24 17:36:15,471 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:15,569 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:15,667 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:15,763 - INFO - Frame 1722 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 0
2025-11-24 17:36:15,766 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:15,858 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:15,954 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:15,974 - INFO - Frame 1724 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 0
2025-11-24 17:36:16,049 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:16,142 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:16,238 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:16,259 - INFO - Frame 1726 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 0
2025-11-24 17:36:16,330 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:16,430 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:16,524 - INFO - Frame 1728 | PERCLOS: 0.10 | Yaw: -0.5° | Alerts: 0
2025-11-24 17:36:16,526 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:16,622 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:16,713 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:16,734 - INFO - Frame 1730 | PERCLOS: 0.13 | Yaw: -0.1° | Alerts: 0
2025-11-24 17:36:16,810 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:16,909 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:17,002 - INFO - Frame 1732 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:17,003 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:17,097 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:17,192 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:17,285 - INFO - Frame 1734 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:17,288 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:17,380 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:17,474 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:17,564 - INFO - Frame 1736 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:17,566 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:17,660 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:17,753 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:17,842 - INFO - Frame 1738 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:17,845 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:17,938 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:18,034 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:18,127 - INFO - Frame 1740 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:18,128 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:18,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:18,317 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:18,338 - INFO - Frame 1742 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:18,410 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:18,509 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:18,603 - INFO - Frame 1744 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:18,604 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:18,699 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:18,788 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:18,878 - INFO - Frame 1746 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:18,879 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:18,966 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:19,059 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:19,143 - INFO - Frame 1748 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:19,145 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:19,238 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:19,330 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:19,422 - INFO - Frame 1750 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:19,424 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:19,520 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:19,642 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:19,734 - INFO - Frame 1752 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:19,737 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:19,828 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:19,922 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:20,012 - INFO - Frame 1754 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:20,014 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:20,107 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:20,200 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:20,295 - INFO - Frame 1756 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:20,297 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:20,389 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:20,483 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:20,566 - INFO - Frame 1758 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:20,569 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:20,664 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:20,760 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:20,848 - INFO - Frame 1760 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:20,849 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:20,940 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:21,032 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:21,124 - INFO - Frame 1762 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:21,126 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:21,212 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:21,307 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:21,399 - INFO - Frame 1764 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:21,400 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:21,497 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:21,591 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:21,683 - INFO - Frame 1766 | PERCLOS: 0.18 | Yaw: 5.1° | Alerts: 0
2025-11-24 17:36:21,686 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:21,780 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:21,877 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:21,898 - INFO - Frame 1768 | PERCLOS: 0.27 | Yaw: 8.0° | Alerts: 0
2025-11-24 17:36:21,975 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:22,074 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:22,167 - INFO - Frame 1770 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:22,169 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:22,261 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:22,358 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:22,449 - INFO - Frame 1772 | PERCLOS: 0.27 | Yaw: 9.9° | Alerts: 0
2025-11-24 17:36:22,451 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:22,548 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:22,641 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:22,735 - INFO - Frame 1774 | PERCLOS: 0.39 | Yaw: 11.1° | Alerts: 1
2025-11-24 17:36:22,737 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:22,834 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:22,932 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:22,953 - INFO - Frame 1776 | PERCLOS: 0.33 | Yaw: 11.6° | Alerts: 1
2025-11-24 17:36:23,026 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:23,124 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:23,220 - INFO - Frame 1778 | PERCLOS: 0.11 | Yaw: 11.4° | Alerts: 0
2025-11-24 17:36:23,222 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:23,319 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:23,414 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:23,434 - INFO - Frame 1780 | PERCLOS: 0.27 | Yaw: 11.1° | Alerts: 0
2025-11-24 17:36:23,514 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:23,609 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:23,703 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:23,726 - INFO - Frame 1782 | PERCLOS: 0.17 | Yaw: 10.9° | Alerts: 0
2025-11-24 17:36:23,797 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:23,896 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:23,991 - INFO - Frame 1784 | PERCLOS: 0.24 | Yaw: 10.9° | Alerts: 0
2025-11-24 17:36:23,993 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:24,085 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:24,179 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:24,269 - INFO - Frame 1786 | PERCLOS: 0.00 | Yaw: 7.8° | Alerts: 0
2025-11-24 17:36:24,271 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:24,363 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:24,457 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:24,477 - INFO - Frame 1788 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 0
2025-11-24 17:36:24,551 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:24,648 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:24,743 - INFO - Frame 1790 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 0
2025-11-24 17:36:24,745 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:24,835 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:24,929 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:25,019 - INFO - Frame 1792 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 0
2025-11-24 17:36:25,021 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:25,113 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:25,206 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:25,290 - INFO - Frame 1794 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 0
2025-11-24 17:36:25,293 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:25,379 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:25,468 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:25,491 - INFO - Frame 1796 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 0
2025-11-24 17:36:25,565 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:25,659 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:25,757 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:25,778 - INFO - Frame 1798 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 0
2025-11-24 17:36:25,851 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:25,955 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:26,046 - INFO - Frame 1800 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 0
2025-11-24 17:36:26,048 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:26,143 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:26,236 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:26,328 - INFO - Frame 1802 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:36:26,330 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:26,423 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:26,511 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:26,627 - INFO - Frame 1804 | PERCLOS: 0.30 | Yaw: 4.3° | Alerts: 0
2025-11-24 17:36:26,629 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:26,722 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:26,814 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:26,904 - INFO - Frame 1806 | PERCLOS: 0.34 | Yaw: 8.5° | Alerts: 1
2025-11-24 17:36:26,906 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:26,998 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:27,095 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:27,114 - INFO - Frame 1808 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:27,192 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:27,291 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:27,385 - INFO - Frame 1810 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 0
2025-11-24 17:36:27,387 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:27,478 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:27,574 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:27,596 - INFO - Frame 1812 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 0
2025-11-24 17:36:27,669 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:27,768 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:27,861 - INFO - Frame 1814 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:36:27,863 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:27,955 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:28,048 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:28,132 - INFO - Frame 1816 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 0
2025-11-24 17:36:28,134 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:28,229 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:28,324 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:28,345 - INFO - Frame 1818 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 0
2025-11-24 17:36:28,419 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:28,510 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:28,595 - INFO - Frame 1820 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:28,597 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:28,682 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:28,773 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:28,863 - INFO - Frame 1822 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:28,865 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:28,956 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:29,045 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:29,131 - INFO - Frame 1824 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:29,132 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:29,219 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:29,313 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:29,403 - INFO - Frame 1826 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:29,405 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:29,496 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:29,584 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:29,669 - INFO - Frame 1828 | PERCLOS: 0.00 | Yaw: 10.5° | Alerts: 0
2025-11-24 17:36:29,671 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:29,756 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:29,849 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:29,870 - INFO - Frame 1830 | PERCLOS: 0.00 | Yaw: 6.2° | Alerts: 0
2025-11-24 17:36:29,940 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:30,030 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:30,120 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:30,141 - INFO - Frame 1832 | PERCLOS: 0.00 | Yaw: 6.7° | Alerts: 0
2025-11-24 17:36:30,212 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:30,314 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:30,415 - INFO - Frame 1834 | PERCLOS: 0.00 | Yaw: 8.7° | Alerts: 0
2025-11-24 17:36:30,418 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:30,528 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:30,620 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:30,640 - INFO - Frame 1836 | PERCLOS: 0.00 | Yaw: 7.9° | Alerts: 0
2025-11-24 17:36:30,729 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:30,833 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:30,931 - INFO - Frame 1838 | PERCLOS: 0.00 | Yaw: 8.1° | Alerts: 0
2025-11-24 17:36:30,933 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:31,035 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:31,132 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:31,154 - INFO - Frame 1840 | PERCLOS: 0.00 | Yaw: 8.4° | Alerts: 0
2025-11-24 17:36:31,226 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:31,323 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:31,414 - INFO - Frame 1842 | PERCLOS: 0.00 | Yaw: 8.8° | Alerts: 0
2025-11-24 17:36:31,417 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:31,510 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:31,608 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:31,693 - INFO - Frame 1844 | PERCLOS: 0.00 | Yaw: 8.8° | Alerts: 0
2025-11-24 17:36:31,695 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:31,781 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:31,869 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:31,890 - INFO - Frame 1846 | PERCLOS: 0.00 | Yaw: 8.7° | Alerts: 0
2025-11-24 17:36:31,963 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:32,062 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:32,180 - INFO - Frame 1848 | PERCLOS: 0.00 | Yaw: 9.2° | Alerts: 0
2025-11-24 17:36:32,183 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:32,277 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:32,367 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:32,387 - INFO - Frame 1850 | PERCLOS: 0.00 | Yaw: 9.3° | Alerts: 0
2025-11-24 17:36:32,453 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:32,546 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:32,641 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:32,662 - INFO - Frame 1852 | PERCLOS: 0.43 | Yaw: 10.4° | Alerts: 1
2025-11-24 17:36:32,737 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:32,835 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:32,924 - INFO - Frame 1854 | PERCLOS: 0.33 | Yaw: 10.5° | Alerts: 1
2025-11-24 17:36:32,924 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:33,012 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:33,108 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:33,127 - INFO - Frame 1856 | PERCLOS: 0.09 | Yaw: 11.2° | Alerts: 0
2025-11-24 17:36:33,199 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:33,296 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:33,387 - INFO - Frame 1858 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:33,389 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:33,480 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:33,575 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:33,664 - INFO - Frame 1860 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:33,666 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:33,757 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:33,848 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:33,938 - INFO - Frame 1862 | PERCLOS: 0.00 | Yaw: 9.7° | Alerts: 0
2025-11-24 17:36:33,940 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:34,032 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:34,126 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:34,148 - INFO - Frame 1864 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:34,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:34,318 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:34,410 - INFO - Frame 1866 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:34,412 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:34,504 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:34,592 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:34,613 - INFO - Frame 1868 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:34,687 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:34,778 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:34,871 - INFO - Frame 1870 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:34,872 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:34,963 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:35,058 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:35,080 - INFO - Frame 1872 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:35,153 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:35,245 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:35,337 - INFO - Frame 1874 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:35,339 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:35,432 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:35,524 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:35,614 - INFO - Frame 1876 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:35,616 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:35,705 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:35,801 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:35,892 - INFO - Frame 1878 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:36:35,894 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:35,985 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:36,074 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:36,096 - INFO - Frame 1880 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:36,163 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:36,256 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:36,343 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:36,365 - INFO - Frame 1882 | PERCLOS: 0.00 | Yaw: 10.7° | Alerts: 0
2025-11-24 17:36:36,438 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:36,536 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:36,627 - INFO - Frame 1884 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:36,628 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:36,720 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:36,812 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:36,904 - INFO - Frame 1886 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:36,906 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:36,992 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:37,079 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:37,169 - INFO - Frame 1888 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:37,171 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:37,262 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:37,358 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:37,448 - INFO - Frame 1890 | PERCLOS: 0.00 | Yaw: 12.6° | Alerts: 0
2025-11-24 17:36:37,451 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:37,535 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:37,622 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:37,706 - INFO - Frame 1892 | PERCLOS: 0.00 | Yaw: 12.7° | Alerts: 0
2025-11-24 17:36:37,709 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:37,794 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:37,883 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:37,974 - INFO - Frame 1894 | PERCLOS: 0.00 | Yaw: 12.8° | Alerts: 0
2025-11-24 17:36:37,975 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:38,066 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:38,161 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:38,182 - INFO - Frame 1896 | PERCLOS: 0.00 | Yaw: 12.9° | Alerts: 0
2025-11-24 17:36:38,250 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:38,346 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:38,438 - INFO - Frame 1898 | PERCLOS: 0.00 | Yaw: 14.3° | Alerts: 0
2025-11-24 17:36:38,440 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:38,528 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:38,614 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:38,707 - INFO - Frame 1900 | PERCLOS: 0.00 | Yaw: 12.6° | Alerts: 0
2025-11-24 17:36:38,708 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:38,800 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:38,893 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:38,977 - INFO - Frame 1902 | PERCLOS: 0.00 | Yaw: 13.2° | Alerts: 0
2025-11-24 17:36:38,980 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:39,065 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:39,151 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:39,235 - INFO - Frame 1904 | PERCLOS: 0.00 | Yaw: 12.8° | Alerts: 0
2025-11-24 17:36:39,238 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:39,323 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:39,409 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:39,500 - INFO - Frame 1906 | PERCLOS: 0.00 | Yaw: 13.1° | Alerts: 0
2025-11-24 17:36:39,502 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:39,592 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:39,686 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:39,704 - INFO - Frame 1908 | PERCLOS: 0.00 | Yaw: 12.7° | Alerts: 0
2025-11-24 17:36:39,778 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:39,874 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:39,968 - INFO - Frame 1910 | PERCLOS: 0.00 | Yaw: 10.0° | Alerts: 0
2025-11-24 17:36:39,970 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:40,062 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:40,154 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:40,238 - INFO - Frame 1912 | PERCLOS: 0.00 | Yaw: 8.7° | Alerts: 0
2025-11-24 17:36:40,240 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:40,325 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:40,414 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:40,434 - INFO - Frame 1914 | PERCLOS: 0.00 | Yaw: 8.6° | Alerts: 0
2025-11-24 17:36:40,507 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:40,593 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:40,688 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:40,709 - INFO - Frame 1916 | PERCLOS: 0.00 | Yaw: 8.7° | Alerts: 0
2025-11-24 17:36:40,780 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:40,877 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:40,968 - INFO - Frame 1918 | PERCLOS: 0.35 | Yaw: 9.4° | Alerts: 1
2025-11-24 17:36:40,970 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:41,063 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:41,157 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:41,249 - INFO - Frame 1920 | PERCLOS: 0.00 | Yaw: 10.1° | Alerts: 0
2025-11-24 17:36:41,251 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:41,343 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:41,435 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:41,525 - INFO - Frame 1922 | PERCLOS: 0.00 | Yaw: 11.1° | Alerts: 0
2025-11-24 17:36:41,527 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:41,618 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:41,710 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:41,796 - INFO - Frame 1924 | PERCLOS: 0.00 | Yaw: 12.8° | Alerts: 0
2025-11-24 17:36:41,798 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:41,889 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:41,978 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:41,999 - INFO - Frame 1926 | PERCLOS: 0.00 | Yaw: 13.2° | Alerts: 0
2025-11-24 17:36:42,073 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:42,171 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:42,261 - INFO - Frame 1928 | PERCLOS: 0.00 | Yaw: 12.5° | Alerts: 0
2025-11-24 17:36:42,263 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:42,355 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:42,449 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:42,469 - INFO - Frame 1930 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:42,570 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:42,669 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:42,760 - INFO - Frame 1932 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:42,763 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:42,854 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:42,947 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:43,038 - INFO - Frame 1934 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:43,040 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:43,131 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:43,219 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:43,303 - INFO - Frame 1936 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:43,305 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:43,390 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:43,476 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:43,562 - INFO - Frame 1938 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:43,564 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:43,650 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:43,740 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:43,830 - INFO - Frame 1940 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:43,831 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:43,916 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:44,002 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:44,087 - INFO - Frame 1942 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:44,088 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:44,173 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:44,262 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:44,347 - INFO - Frame 1944 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:44,349 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:44,441 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:44,534 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:44,623 - INFO - Frame 1946 | PERCLOS: 0.00 | Yaw: 13.6° | Alerts: 0
2025-11-24 17:36:44,625 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:44,718 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:44,813 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:44,833 - INFO - Frame 1948 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:44,906 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:45,004 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:45,095 - INFO - Frame 1950 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:45,097 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:45,183 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:45,275 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:45,365 - INFO - Frame 1952 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:36:45,367 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:45,459 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:45,549 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:45,569 - INFO - Frame 1954 | PERCLOS: 0.00 | Yaw: 15.0° | Alerts: 0
2025-11-24 17:36:45,636 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:45,733 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:45,821 - INFO - Frame 1956 | PERCLOS: 0.00 | Yaw: 9.9° | Alerts: 0
2025-11-24 17:36:45,822 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:45,908 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:45,996 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:46,082 - INFO - Frame 1958 | PERCLOS: 0.00 | Yaw: 8.2° | Alerts: 0
2025-11-24 17:36:46,084 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:46,170 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:46,258 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:46,280 - INFO - Frame 1960 | PERCLOS: 0.00 | Yaw: 7.4° | Alerts: 0
2025-11-24 17:36:46,353 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:46,453 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:46,539 - INFO - Frame 1962 | PERCLOS: 0.00 | Yaw: 6.8° | Alerts: 0
2025-11-24 17:36:46,541 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:46,628 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:46,725 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:46,816 - INFO - Frame 1964 | PERCLOS: 0.00 | Yaw: 7.6° | Alerts: 0
2025-11-24 17:36:46,818 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:46,913 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:47,007 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:47,100 - INFO - Frame 1966 | PERCLOS: 0.00 | Yaw: 8.0° | Alerts: 0
2025-11-24 17:36:47,102 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:47,195 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:47,286 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:47,305 - INFO - Frame 1968 | PERCLOS: 0.00 | Yaw: 9.0° | Alerts: 0
2025-11-24 17:36:47,372 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:47,472 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:47,556 - INFO - Frame 1970 | PERCLOS: 0.00 | Yaw: 8.7° | Alerts: 0
2025-11-24 17:36:47,558 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:47,644 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:47,734 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:47,754 - INFO - Frame 1972 | PERCLOS: 0.00 | Yaw: 9.1° | Alerts: 0
2025-11-24 17:36:47,820 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:47,912 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:48,003 - INFO - Frame 1974 | PERCLOS: 0.00 | Yaw: 9.4° | Alerts: 0
2025-11-24 17:36:48,005 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:48,089 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:48,181 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:48,271 - INFO - Frame 1976 | PERCLOS: 0.24 | Yaw: 9.2° | Alerts: 0
2025-11-24 17:36:48,273 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:48,365 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:48,460 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:48,478 - INFO - Frame 1978 | PERCLOS: 0.33 | Yaw: 9.6° | Alerts: 1
2025-11-24 17:36:48,553 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:48,651 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:36:48,743 - INFO - Frame 1980 | PERCLOS: 0.30 | Yaw: 9.0° | Alerts: 1
2025-11-24 17:38:06,250 - INFO - Loading models...
2025-11-24 17:38:06,269 - INFO - ✓ YOLO ONNX loaded
2025-11-24 17:38:06,305 - INFO - ✓ MediaPipe Face Mesh loaded
2025-11-24 17:38:06,312 - INFO - ✓ MediaPipe Pose loaded (for smoke & seatbelt)
2025-11-24 17:38:06,429 - INFO - ✓ Camera 0 opened successfully
2025-11-24 17:38:06,956 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:06,964 - INFO - Frame 0 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 0
2025-11-24 17:38:07,098 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:07,252 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:07,384 - INFO - Frame 2 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 0
2025-11-24 17:38:07,390 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:07,535 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:07,698 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:07,851 - INFO - Frame 4 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 0
2025-11-24 17:38:07,853 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:07,998 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:08,152 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:08,310 - INFO - Frame 6 | PERCLOS: 0.00 | Yaw: 5.2° | Alerts: 0
2025-11-24 17:38:08,311 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:08,465 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:08,623 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:08,781 - INFO - Frame 8 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 0
2025-11-24 17:38:08,788 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:08,924 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:09,072 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:09,220 - INFO - Frame 10 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:09,223 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:09,372 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:09,528 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:09,543 - INFO - Frame 12 | PERCLOS: 0.15 | Yaw: 7.4° | Alerts: 0
2025-11-24 17:38:09,681 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:09,832 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:09,977 - INFO - Frame 14 | PERCLOS: 0.00 | Yaw: 7.4° | Alerts: 0
2025-11-24 17:38:09,984 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:10,146 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:10,298 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:10,450 - INFO - Frame 16 | PERCLOS: 0.00 | Yaw: 6.9° | Alerts: 0
2025-11-24 17:38:10,456 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:10,603 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:10,749 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:10,909 - INFO - Frame 18 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 0
2025-11-24 17:38:10,913 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:11,060 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:11,213 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:11,231 - INFO - Frame 20 | PERCLOS: 0.00 | Yaw: 6.1° | Alerts: 0
2025-11-24 17:38:11,370 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:11,509 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:11,675 - INFO - Frame 22 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:11,681 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:11,863 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:12,016 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:12,173 - INFO - Frame 24 | PERCLOS: 0.19 | Yaw: 5.4° | Alerts: 0
2025-11-24 17:38:12,178 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:12,325 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:12,478 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:12,632 - INFO - Frame 26 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:12,637 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:12,780 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:12,931 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:12,948 - INFO - Frame 28 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 0
2025-11-24 17:38:13,086 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:13,237 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:13,389 - INFO - Frame 30 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 0
2025-11-24 17:38:13,395 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:13,548 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:13,701 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:13,851 - INFO - Frame 32 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 0
2025-11-24 17:38:13,858 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:14,009 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:14,165 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:14,322 - INFO - Frame 34 | PERCLOS: 0.15 | Yaw: 3.9° | Alerts: 0
2025-11-24 17:38:14,326 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:14,477 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:14,631 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:14,646 - INFO - Frame 36 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 0
2025-11-24 17:38:14,787 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:14,936 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:15,093 - INFO - Frame 38 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:15,096 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:15,243 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:15,398 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:15,416 - INFO - Frame 40 | PERCLOS: 0.00 | Yaw: 9.1° | Alerts: 0
2025-11-24 17:38:15,558 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:15,715 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:15,856 - INFO - Frame 42 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:15,859 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:16,011 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:16,165 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:16,314 - INFO - Frame 44 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:16,317 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:16,456 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:16,606 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:16,623 - INFO - Frame 46 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:16,767 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:16,918 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:16,951 - INFO - Frame 48 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:17,070 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:17,222 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:17,361 - INFO - Frame 50 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:17,363 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:17,501 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:17,653 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:17,811 - INFO - Frame 52 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:17,816 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:17,964 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:18,126 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:18,271 - INFO - Frame 54 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:18,273 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:18,423 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:18,580 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:18,732 - INFO - Frame 56 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:18,737 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:18,886 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:19,044 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:19,200 - INFO - Frame 58 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:19,201 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:19,355 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:19,506 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:19,702 - INFO - Frame 60 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:19,705 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:19,849 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:20,007 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:20,160 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:20,175 - INFO - Frame 62 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:20,311 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:20,474 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:20,627 - INFO - Frame 64 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 0
2025-11-24 17:38:20,630 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:20,783 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:20,935 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:21,092 - INFO - Frame 66 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:21,096 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:21,244 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:21,401 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:21,415 - INFO - Frame 68 | PERCLOS: 0.15 | Yaw: 3.7° | Alerts: 0
2025-11-24 17:38:21,564 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:21,709 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:21,810 - INFO - Frame 70 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 0
2025-11-24 17:38:21,873 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:22,020 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:22,173 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:22,192 - INFO - Frame 72 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 0
2025-11-24 17:38:22,328 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:22,484 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:22,644 - INFO - Frame 74 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 0
2025-11-24 17:38:22,649 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:22,804 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:22,956 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:23,113 - INFO - Frame 76 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 0
2025-11-24 17:38:23,119 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:23,275 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:23,432 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:23,578 - INFO - Frame 78 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 0
2025-11-24 17:38:23,582 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:23,737 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:23,888 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:23,906 - INFO - Frame 80 | PERCLOS: 0.47 | Yaw: 4.3° | Alerts: 1
2025-11-24 17:38:24,036 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:24,179 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:24,337 - INFO - Frame 82 | PERCLOS: 0.24 | Yaw: 3.8° | Alerts: 0
2025-11-24 17:38:24,342 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:24,497 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:24,659 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:24,810 - INFO - Frame 84 | PERCLOS: 0.11 | Yaw: 3.8° | Alerts: 0
2025-11-24 17:38:24,813 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:24,963 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:25,108 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:25,125 - INFO - Frame 86 | PERCLOS: 0.31 | Yaw: 3.8° | Alerts: 1
2025-11-24 17:38:25,269 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:25,413 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:25,563 - INFO - Frame 88 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 0
2025-11-24 17:38:25,568 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:25,714 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:25,866 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:26,022 - INFO - Frame 90 | PERCLOS: 0.13 | Yaw: 3.9° | Alerts: 0
2025-11-24 17:38:26,025 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:26,172 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:26,319 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:26,338 - INFO - Frame 92 | PERCLOS: 0.13 | Yaw: 3.8° | Alerts: 0
2025-11-24 17:38:26,465 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:26,610 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:26,767 - INFO - Frame 94 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 0
2025-11-24 17:38:26,772 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:26,928 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:27,061 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:27,210 - INFO - Frame 96 | PERCLOS: 0.32 | Yaw: 3.9° | Alerts: 1
2025-11-24 17:38:27,215 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:27,355 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:27,500 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:27,652 - INFO - Frame 98 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 0
2025-11-24 17:38:27,657 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:27,801 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:27,961 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:27,981 - INFO - Frame 100 | PERCLOS: 0.25 | Yaw: 3.7° | Alerts: 0
2025-11-24 17:38:28,116 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:28,274 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:28,420 - INFO - Frame 102 | PERCLOS: 0.33 | Yaw: 3.7° | Alerts: 1
2025-11-24 17:38:28,424 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:28,577 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:28,716 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:28,732 - INFO - Frame 104 | PERCLOS: 0.06 | Yaw: 3.8° | Alerts: 0
2025-11-24 17:38:28,866 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:29,021 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:29,176 - INFO - Frame 106 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 0
2025-11-24 17:38:29,181 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:29,333 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:29,499 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:29,657 - INFO - Frame 108 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 0
2025-11-24 17:38:29,661 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:29,813 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:29,950 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:29,963 - INFO - Frame 110 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 0
2025-11-24 17:38:30,112 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:30,255 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:30,412 - INFO - Frame 112 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 0
2025-11-24 17:38:30,416 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:30,562 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:30,709 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:30,725 - INFO - Frame 114 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 0
2025-11-24 17:38:30,864 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:31,019 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:31,173 - INFO - Frame 116 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 0
2025-11-24 17:38:31,177 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:31,326 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:31,475 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:31,493 - INFO - Frame 118 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 0
2025-11-24 17:38:31,626 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:31,782 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:31,938 - INFO - Frame 120 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 0
2025-11-24 17:38:31,942 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:32,089 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:32,244 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:32,261 - INFO - Frame 122 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 0
2025-11-24 17:38:32,397 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:32,556 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:32,709 - INFO - Frame 124 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 0
2025-11-24 17:38:32,715 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:32,870 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:33,021 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:33,176 - INFO - Frame 126 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 0
2025-11-24 17:38:33,180 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:33,333 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:33,480 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:33,496 - INFO - Frame 128 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:33,627 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:33,787 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:33,939 - INFO - Frame 130 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:33,943 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:34,091 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:34,238 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:34,403 - INFO - Frame 132 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:34,404 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:34,553 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:34,705 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:34,870 - INFO - Frame 134 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:34,871 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:35,012 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:35,165 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:35,318 - INFO - Frame 136 | PERCLOS: 0.30 | Yaw: 7.4° | Alerts: 0
2025-11-24 17:38:35,323 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:35,471 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:35,618 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:35,635 - INFO - Frame 138 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 0
2025-11-24 17:38:35,769 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:35,928 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:36,086 - INFO - Frame 140 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 0
2025-11-24 17:38:36,089 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:36,242 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:36,389 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:36,544 - INFO - Frame 142 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 0
2025-11-24 17:38:36,549 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:36,701 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:36,849 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:37,008 - INFO - Frame 144 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 0
2025-11-24 17:38:37,014 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:37,166 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:37,323 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:37,474 - INFO - Frame 146 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 0
2025-11-24 17:38:37,479 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:37,634 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:37,783 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:37,938 - INFO - Frame 148 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:37,942 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:38,089 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:38,237 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:38,254 - INFO - Frame 150 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 0
2025-11-24 17:38:38,390 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:38,545 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:38,694 - INFO - Frame 152 | PERCLOS: 0.00 | Yaw: -2.9° | Alerts: 0
2025-11-24 17:38:38,697 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:38,851 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:39,003 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:39,020 - INFO - Frame 154 | PERCLOS: 0.00 | Yaw: -3.2° | Alerts: 0
2025-11-24 17:38:39,161 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:39,308 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:39,467 - INFO - Frame 156 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 0
2025-11-24 17:38:39,473 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:39,624 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:39,779 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:39,937 - INFO - Frame 158 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 1
2025-11-24 17:38:39,937 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:40,089 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:40,242 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:40,394 - INFO - Frame 160 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 0
2025-11-24 17:38:40,397 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:40,541 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:40,683 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:40,835 - INFO - Frame 162 | PERCLOS: 0.17 | Yaw: 1.1° | Alerts: 1
2025-11-24 17:38:40,838 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:40,970 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:41,115 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:41,280 - INFO - Frame 164 | PERCLOS: 0.16 | Yaw: 0.8° | Alerts: 1
2025-11-24 17:38:41,280 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:41,429 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:41,575 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:41,738 - INFO - Frame 166 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 1
2025-11-24 17:38:41,738 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:41,878 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:42,030 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:42,192 - INFO - Frame 168 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 1
2025-11-24 17:38:42,192 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:42,352 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:42,502 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:42,665 - INFO - Frame 170 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 1
2025-11-24 17:38:42,665 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:42,822 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:42,971 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:43,133 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:43,133 - INFO - Frame 172 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 1
2025-11-24 17:38:43,286 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:43,435 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:43,583 - INFO - Frame 174 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 1
2025-11-24 17:38:43,587 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:43,738 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:43,896 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:43,912 - INFO - Frame 176 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 0
2025-11-24 17:38:44,047 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:44,200 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:44,353 - INFO - Frame 178 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 0
2025-11-24 17:38:44,357 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:44,505 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:44,658 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:44,679 - INFO - Frame 180 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 17:38:44,812 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:44,978 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:45,127 - INFO - Frame 182 | PERCLOS: 0.45 | Yaw: 2.2° | Alerts: 1
2025-11-24 17:38:45,133 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:45,292 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:45,447 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:45,603 - INFO - Frame 184 | PERCLOS: 0.00 | Yaw: -0.3° | Alerts: 0
2025-11-24 17:38:45,609 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:45,762 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:45,912 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:46,062 - INFO - Frame 186 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 0
2025-11-24 17:38:46,067 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:46,207 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:46,352 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:46,494 - INFO - Frame 188 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 0
2025-11-24 17:38:46,497 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:46,652 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:46,813 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:46,830 - INFO - Frame 190 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 0
2025-11-24 17:38:46,966 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:47,130 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:47,274 - INFO - Frame 192 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 0
2025-11-24 17:38:47,281 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:47,427 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:47,576 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:47,728 - INFO - Frame 194 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:47,733 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:47,885 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:48,039 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:48,204 - INFO - Frame 196 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:48,206 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:48,360 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:48,517 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:48,675 - INFO - Frame 198 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:48,678 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:48,823 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:48,973 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:48,995 - INFO - Frame 200 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:49,121 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:49,278 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:49,441 - INFO - Frame 202 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:49,445 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:49,597 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:49,755 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:49,909 - INFO - Frame 204 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:49,911 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:50,055 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:50,208 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:50,362 - INFO - Frame 206 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:50,368 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:50,521 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:50,670 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:50,825 - INFO - Frame 208 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:50,829 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:50,971 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:51,132 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:51,151 - INFO - Frame 210 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:51,287 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:51,440 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:51,597 - INFO - Frame 212 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:51,601 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:51,748 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:51,901 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:51,917 - INFO - Frame 214 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:52,052 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:52,200 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:52,355 - INFO - Frame 216 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:52,359 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:52,499 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:52,656 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:52,672 - INFO - Frame 218 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:52,806 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:52,971 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:53,117 - INFO - Frame 220 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:53,119 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:53,271 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:53,424 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:53,569 - INFO - Frame 222 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:53,574 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:53,727 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:53,877 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:54,032 - INFO - Frame 224 | PERCLOS: 0.00 | Yaw: 8.2° | Alerts: 0
2025-11-24 17:38:54,036 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:54,191 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:54,342 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:54,359 - INFO - Frame 226 | PERCLOS: 0.00 | Yaw: 6.3° | Alerts: 0
2025-11-24 17:38:54,497 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:54,647 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:54,802 - INFO - Frame 228 | PERCLOS: 0.00 | Yaw: 8.5° | Alerts: 0
2025-11-24 17:38:54,808 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:54,956 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:55,110 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:55,267 - INFO - Frame 230 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:55,272 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:55,417 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:55,577 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:55,729 - INFO - Frame 232 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:55,736 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:55,887 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:56,035 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:56,191 - INFO - Frame 234 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:56,197 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:56,346 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:56,493 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:56,646 - INFO - Frame 236 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:56,651 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:56,799 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:56,952 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:57,126 - INFO - Frame 238 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:57,128 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:57,277 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:57,430 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:57,581 - INFO - Frame 240 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:38:57,589 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:57,741 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:57,898 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:58,057 - INFO - Frame 242 | PERCLOS: 0.00 | Yaw: 8.1° | Alerts: 0
2025-11-24 17:38:58,062 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:58,219 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:58,369 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:58,529 - INFO - Frame 244 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 0
2025-11-24 17:38:58,534 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:58,689 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:58,849 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:59,001 - INFO - Frame 246 | PERCLOS: 0.00 | Yaw: 4.1° | Alerts: 0
2025-11-24 17:38:59,006 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:59,151 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:59,299 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:59,457 - INFO - Frame 248 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 0
2025-11-24 17:38:59,465 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:59,612 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:59,764 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:38:59,778 - INFO - Frame 250 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 0
2025-11-24 17:38:59,926 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:00,083 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:00,239 - INFO - Frame 252 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 0
2025-11-24 17:39:00,245 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:00,399 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:00,553 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:00,710 - INFO - Frame 254 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:00,715 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:00,858 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:01,013 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:01,171 - INFO - Frame 256 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:01,176 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:01,324 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:01,488 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:01,639 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:01,655 - INFO - Frame 258 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:01,780 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:01,940 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:02,088 - INFO - Frame 260 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:02,094 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:02,242 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:02,394 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:02,412 - INFO - Frame 262 | PERCLOS: 0.00 | Yaw: 9.6° | Alerts: 0
2025-11-24 17:39:02,554 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:02,703 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:02,858 - INFO - Frame 264 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:02,863 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:03,027 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:03,035 - ERROR - Task exception was never retrieved
future: <Task finished name='Task-24681' coro=<WebSocketProtocol13.write_message.<locals>.wrapper() done, defined at /home/tech4biz/work/tools/Driver_DSMS_ADAS/venv/lib/python3.12/site-packages/tornado/websocket.py:1111> exception=WebSocketClosedError()>
Traceback (most recent call last):
  File "/home/tech4biz/work/tools/Driver_DSMS_ADAS/venv/lib/python3.12/site-packages/tornado/websocket.py", line 1113, in wrapper
    await fut
tornado.iostream.StreamClosedError: Stream is closed

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/tech4biz/work/tools/Driver_DSMS_ADAS/venv/lib/python3.12/site-packages/tornado/websocket.py", line 1115, in wrapper
    raise WebSocketClosedError()
tornado.websocket.WebSocketClosedError
2025-11-24 17:39:03,204 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:03,295 - INFO - Frame 266 | PERCLOS: 0.00 | Yaw: 8.7° | Alerts: 0
2025-11-24 17:39:03,297 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:03,391 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:03,486 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:03,495 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:03,654 - INFO - Frame 268 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:03,658 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:03,658 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:03,808 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:03,810 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:03,949 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:03,949 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:03,966 - INFO - Frame 270 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:04,091 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:04,091 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:04,240 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:04,241 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:04,374 - INFO - Frame 272 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:04,378 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:04,378 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:04,537 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:04,537 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:04,697 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:04,698 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:04,711 - INFO - Frame 274 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:04,848 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:04,848 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:04,999 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:04,999 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:05,151 - INFO - Frame 276 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:05,155 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:05,156 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:05,307 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:05,307 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:05,453 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:05,454 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:05,467 - INFO - Frame 278 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:05,605 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:05,605 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:05,759 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:05,761 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:05,909 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:05,909 - INFO - Frame 280 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:05,914 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:06,056 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:06,056 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:06,212 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:06,212 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:06,227 - INFO - Frame 282 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:06,354 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:06,355 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:06,528 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:06,531 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:06,681 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:06,682 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:06,696 - INFO - Frame 284 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:06,839 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:06,840 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:06,983 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:06,983 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:07,128 - INFO - Frame 286 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:07,131 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:07,132 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:07,277 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:07,278 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:07,422 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:07,424 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:07,441 - INFO - Frame 288 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:07,588 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:07,590 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:07,739 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:07,740 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:07,775 - INFO - Frame 290 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:07,882 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:07,883 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:08,038 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:08,038 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:08,172 - INFO - Frame 292 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:08,176 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:08,177 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:08,336 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:08,340 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:08,486 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:08,487 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:08,501 - INFO - Frame 294 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:08,637 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:08,637 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:08,789 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:08,789 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:08,935 - INFO - Frame 296 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:08,938 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:08,938 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:09,088 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:09,088 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:09,232 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:09,232 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:09,246 - INFO - Frame 298 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:09,381 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:09,383 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:09,535 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:09,536 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:09,691 - INFO - Frame 300 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:09,691 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:09,693 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:09,836 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:09,837 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:09,989 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:09,990 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:10,001 - INFO - Frame 302 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:10,149 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:10,149 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:10,302 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:10,302 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:10,451 - INFO - Frame 304 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:10,453 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:10,453 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:10,597 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:10,605 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:10,756 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:10,756 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:10,770 - INFO - Frame 306 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:10,910 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:10,910 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:11,065 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:11,066 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:11,205 - INFO - Frame 308 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:11,208 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:11,208 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:11,358 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:11,358 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:11,518 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:11,519 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:11,531 - INFO - Frame 310 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:11,669 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:11,669 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:11,833 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:11,833 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:11,970 - INFO - Frame 312 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:11,973 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:11,975 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:12,127 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:12,130 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:12,272 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:12,272 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:12,300 - INFO - Frame 314 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:12,432 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:12,432 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:12,584 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:12,585 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:12,721 - INFO - Frame 316 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:12,725 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:12,725 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:12,867 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:12,870 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:13,011 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:13,012 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:13,025 - INFO - Frame 318 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:13,173 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:13,173 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:13,321 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:13,322 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:13,475 - INFO - Frame 320 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:13,477 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:13,480 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:13,623 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:13,623 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:13,785 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:13,785 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:13,800 - INFO - Frame 322 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:13,930 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:13,930 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:14,086 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:14,087 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:14,236 - INFO - Frame 324 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:14,239 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:14,239 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:14,393 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:14,393 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:14,541 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:14,542 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:14,556 - INFO - Frame 326 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:14,690 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:14,690 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:14,846 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:14,846 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:15,000 - INFO - Frame 328 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:15,003 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:15,004 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:15,170 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:15,171 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:15,322 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:15,322 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:15,335 - INFO - Frame 330 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:15,466 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:15,466 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:15,633 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:15,634 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:15,771 - INFO - Frame 332 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:15,774 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:15,774 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:15,923 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:15,924 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:16,078 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:16,080 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:16,093 - INFO - Frame 334 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:16,224 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:16,226 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:16,373 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:16,374 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:16,522 - INFO - Frame 336 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:16,524 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:16,524 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:16,675 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:16,676 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:16,828 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:16,828 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:16,843 - INFO - Frame 338 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:16,988 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:16,988 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:17,144 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:17,144 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:17,281 - INFO - Frame 340 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:17,285 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:17,285 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:17,446 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:17,446 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:17,590 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:17,590 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:17,604 - INFO - Frame 342 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:17,729 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:17,730 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:17,883 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:17,885 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:18,028 - INFO - Frame 344 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:18,034 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:18,036 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:18,178 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:18,178 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:18,328 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:18,329 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:18,343 - INFO - Frame 346 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:18,469 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:18,471 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:18,636 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:18,638 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:18,793 - INFO - Frame 348 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:18,794 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:18,794 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:18,942 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:18,946 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:19,104 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:19,104 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:19,117 - INFO - Frame 350 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:19,246 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:19,247 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:19,416 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:19,418 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:19,593 - INFO - Frame 352 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:19,594 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:19,594 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:19,744 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:19,745 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:19,900 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:19,901 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:19,912 - INFO - Frame 354 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:20,047 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:20,047 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:20,214 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:20,214 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:20,313 - INFO - Frame 356 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:20,370 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:20,370 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:20,523 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:20,524 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:20,681 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:20,682 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:20,695 - INFO - Frame 358 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:20,825 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:20,825 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:20,984 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:20,984 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:21,138 - INFO - Frame 360 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:21,142 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:21,142 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:21,291 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:21,291 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:21,443 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:21,443 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:21,458 - INFO - Frame 362 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:21,589 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:21,589 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:21,777 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:21,783 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:21,925 - INFO - Frame 364 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:21,927 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:21,928 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:22,072 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:22,073 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:22,223 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:22,223 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:22,238 - INFO - Frame 366 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:22,366 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:22,366 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:22,521 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:22,522 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:22,684 - INFO - Frame 368 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:22,686 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:22,686 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:22,829 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:22,830 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:22,974 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:22,974 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:22,990 - INFO - Frame 370 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:23,108 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:23,108 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:23,267 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:23,269 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:23,411 - INFO - Frame 372 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:23,413 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:23,413 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:23,571 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:23,573 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:23,733 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:23,733 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:23,748 - INFO - Frame 374 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:23,881 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:23,881 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:24,020 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:24,021 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:24,172 - INFO - Frame 376 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:24,175 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:24,175 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:24,322 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:24,323 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:24,472 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:24,473 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:24,488 - INFO - Frame 378 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:24,626 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:24,626 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:24,777 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:24,778 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:24,924 - INFO - Frame 380 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:24,926 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:24,927 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:25,088 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:25,089 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:25,233 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:25,233 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:25,246 - INFO - Frame 382 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:25,381 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:25,381 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:25,536 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:25,537 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:25,693 - INFO - Frame 384 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:25,697 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:25,697 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:25,846 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:25,847 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:26,004 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:26,005 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:26,020 - INFO - Frame 386 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:26,146 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:26,147 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:26,320 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:26,320 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:26,356 - INFO - Frame 388 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:26,469 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:26,469 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:26,617 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:26,618 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:26,757 - INFO - Frame 390 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:26,758 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:26,761 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:26,907 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:26,909 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:27,060 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:27,061 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:27,075 - INFO - Frame 392 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:27,214 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:27,216 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:27,373 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:27,376 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:27,410 - INFO - Frame 394 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:27,511 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:27,512 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:27,659 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:27,660 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:27,820 - INFO - Frame 396 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:27,822 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:27,823 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:27,964 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:27,964 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:28,127 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:28,132 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:28,147 - INFO - Frame 398 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:28,282 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:28,282 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:28,432 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:28,437 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:28,580 - INFO - Frame 400 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:28,582 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:28,582 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:28,741 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:28,741 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:28,897 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:28,898 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:28,911 - INFO - Frame 402 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:29,063 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:29,063 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:29,218 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:29,218 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:29,377 - INFO - Frame 404 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:29,380 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:29,381 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:29,521 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:29,524 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:29,673 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:29,677 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:29,692 - INFO - Frame 406 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:29,831 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:29,831 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:29,982 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:29,982 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:30,129 - INFO - Frame 408 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:30,132 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:30,132 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:30,289 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:30,289 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:30,468 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:30,468 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:30,480 - INFO - Frame 410 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:30,615 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:30,615 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:30,779 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:30,782 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:30,953 - INFO - Frame 412 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:30,957 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:30,957 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:31,114 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:31,118 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:31,263 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:31,264 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:31,277 - INFO - Frame 414 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:31,417 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:31,419 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:31,578 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:31,580 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:31,613 - INFO - Frame 416 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:31,731 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:31,731 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:31,891 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:31,892 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:32,038 - INFO - Frame 418 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:32,041 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:32,042 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:32,184 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:32,191 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:32,333 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:32,333 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:32,347 - INFO - Frame 420 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:32,495 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:32,495 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:32,638 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:32,639 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:32,673 - INFO - Frame 422 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:32,791 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:32,791 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:32,940 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:32,940 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:33,086 - INFO - Frame 424 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:33,089 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:33,091 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:33,248 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:33,249 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:33,394 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:33,395 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:33,412 - INFO - Frame 426 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:33,542 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:33,543 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:33,708 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:33,708 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:33,745 - INFO - Frame 428 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:33,858 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:33,858 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:34,024 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:34,024 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:34,179 - INFO - Frame 430 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:34,182 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:34,182 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:34,329 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:34,330 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:34,476 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:34,476 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:34,493 - INFO - Frame 432 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:34,643 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:34,643 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:34,798 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:34,800 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:34,946 - INFO - Frame 434 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:34,948 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:34,949 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:35,104 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:35,108 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:35,257 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:35,258 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:35,270 - INFO - Frame 436 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:35,414 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:35,414 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:35,586 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:35,587 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:35,745 - INFO - Frame 438 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:35,746 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:35,746 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:35,902 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:35,903 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:36,065 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:36,067 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:36,078 - INFO - Frame 440 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:36,234 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:36,234 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:36,388 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:36,393 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:36,543 - INFO - Frame 442 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:36,547 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:36,548 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:36,695 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:36,695 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:36,857 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:36,858 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:36,872 - INFO - Frame 444 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:37,006 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:37,006 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:37,165 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:37,168 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:37,325 - INFO - Frame 446 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:37,328 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:37,328 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:37,477 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:37,478 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:37,631 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:37,631 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:37,644 - INFO - Frame 448 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:37,789 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:37,789 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:37,947 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:37,948 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:38,091 - INFO - Frame 450 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:38,095 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:38,095 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:38,270 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:38,270 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:38,421 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:38,423 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:38,437 - INFO - Frame 452 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:38,593 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:38,594 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:38,776 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:38,777 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:38,945 - INFO - Frame 454 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:38,949 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:38,950 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:39,122 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:39,123 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:39,297 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:39,298 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:39,314 - INFO - Frame 456 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:39,478 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:39,482 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:39,645 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:39,648 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:39,799 - INFO - Frame 458 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:39,803 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:39,804 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:39,949 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:39,950 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:40,103 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:40,104 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:40,118 - INFO - Frame 460 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:40,246 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:40,247 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:40,406 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:40,407 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:40,566 - INFO - Frame 462 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:40,570 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:40,571 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:40,717 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:40,719 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:40,876 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:40,876 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:40,890 - INFO - Frame 464 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:41,023 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:41,024 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:41,171 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:41,171 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:41,314 - INFO - Frame 466 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:41,319 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:41,319 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:41,475 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:41,475 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:41,628 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:41,629 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:41,641 - INFO - Frame 468 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:41,787 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:41,788 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:41,944 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:41,954 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:42,093 - INFO - Frame 470 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:42,095 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:42,095 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:42,236 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:42,236 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:42,380 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:42,381 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:42,394 - INFO - Frame 472 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:42,536 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:42,536 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:42,692 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:42,692 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:42,831 - INFO - Frame 474 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:42,834 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:42,834 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:43,002 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:43,002 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:43,154 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:43,154 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:43,171 - INFO - Frame 476 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:43,307 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:43,307 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:43,461 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:43,462 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:43,613 - INFO - Frame 478 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:43,614 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:43,616 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:43,771 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:43,771 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:43,922 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:43,922 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:43,935 - INFO - Frame 480 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:44,073 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:44,073 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:44,225 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:44,226 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:44,375 - INFO - Frame 482 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:44,378 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:44,379 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:44,523 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:44,524 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:44,690 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:44,690 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:44,704 - INFO - Frame 484 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:44,844 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:44,844 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:44,992 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:44,995 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:45,143 - INFO - Frame 486 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:45,145 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:45,145 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:45,294 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:45,294 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:45,451 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:45,452 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:45,464 - INFO - Frame 488 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:45,595 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:45,595 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:45,755 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:45,757 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:45,912 - INFO - Frame 490 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:45,914 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:45,914 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:46,060 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:46,067 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:46,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:46,221 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:46,236 - INFO - Frame 492 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:46,377 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:46,378 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:46,541 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:46,541 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:46,683 - INFO - Frame 494 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:46,686 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:46,688 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:46,843 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:46,844 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:46,996 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:46,998 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:47,010 - INFO - Frame 496 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:47,136 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:47,137 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:47,290 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:47,290 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:47,437 - INFO - Frame 498 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:47,440 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:47,441 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:47,588 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:47,589 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:47,742 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:47,742 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:47,756 - INFO - Frame 500 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:47,912 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:47,914 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:48,066 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:48,067 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:48,223 - INFO - Frame 502 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:48,226 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:48,227 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:48,381 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:48,381 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:48,542 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:48,543 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:48,557 - INFO - Frame 504 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:48,700 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:48,701 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:48,853 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:48,853 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:48,994 - INFO - Frame 506 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:48,998 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:48,998 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:49,153 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:49,153 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:49,305 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:49,305 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:49,320 - INFO - Frame 508 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:49,459 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:49,463 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:49,606 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:49,607 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:49,640 - INFO - Frame 510 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:49,763 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:49,764 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:49,917 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:49,919 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:50,049 - INFO - Frame 512 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:50,051 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:50,051 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:50,201 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:50,201 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:50,357 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:50,357 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:50,372 - INFO - Frame 514 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:50,524 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:50,524 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:50,677 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:50,677 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:50,830 - INFO - Frame 516 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:50,830 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:50,831 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:50,972 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:50,973 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:51,128 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:51,131 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:51,144 - INFO - Frame 518 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:51,275 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:51,276 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:51,442 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:51,445 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:51,595 - INFO - Frame 520 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:51,596 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:51,596 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:51,741 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:51,744 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:51,889 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:51,889 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:51,901 - INFO - Frame 522 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:52,044 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:52,044 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:52,197 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:52,197 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:52,347 - INFO - Frame 524 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:52,349 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:52,351 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:52,484 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:52,484 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:52,642 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:52,642 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:52,657 - INFO - Frame 526 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:52,783 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:52,784 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:52,940 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:52,944 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:53,096 - INFO - Frame 528 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:53,099 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:53,100 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:53,247 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:53,247 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:53,420 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:53,421 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:53,436 - INFO - Frame 530 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:53,565 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:53,565 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:53,732 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:53,732 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:53,767 - INFO - Frame 532 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:53,881 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:53,881 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:54,029 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:54,029 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:54,174 - INFO - Frame 534 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:54,176 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:54,177 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:54,330 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:54,339 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:54,485 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:54,485 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:54,498 - INFO - Frame 536 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:54,631 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:54,632 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:54,792 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:54,796 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:54,936 - INFO - Frame 538 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:54,936 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:54,936 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:55,090 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:55,090 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:55,247 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:55,248 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:55,261 - INFO - Frame 540 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:55,407 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:55,409 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:55,552 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:55,556 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:55,697 - INFO - Frame 542 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:55,699 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:55,701 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:55,849 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:55,850 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:56,004 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:56,005 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:56,018 - INFO - Frame 544 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:56,146 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:56,146 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:56,309 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:56,309 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:56,451 - INFO - Frame 546 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:56,454 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:56,455 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:56,607 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:56,610 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:56,749 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:56,749 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:56,760 - INFO - Frame 548 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:56,902 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:56,902 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:57,066 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:57,067 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:57,101 - INFO - Frame 550 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:57,217 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:57,218 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:57,374 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:57,374 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:57,519 - INFO - Frame 552 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:57,523 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:57,523 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:57,667 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:57,668 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:57,830 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:57,830 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:57,843 - INFO - Frame 554 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:57,972 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:57,973 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:58,126 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:58,126 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:58,264 - INFO - Frame 556 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:58,268 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:58,268 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:58,427 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:58,428 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:58,572 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:58,572 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:58,588 - INFO - Frame 558 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:58,719 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:58,719 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:58,865 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:58,867 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:59,034 - INFO - Frame 560 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:59,037 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:59,040 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:59,186 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:59,187 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:59,339 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:59,339 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:59,356 - INFO - Frame 562 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:59,485 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:59,485 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:59,644 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:59,649 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:59,796 - INFO - Frame 564 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:39:59,799 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:59,799 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:59,947 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:39:59,947 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:00,094 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:00,095 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:00,107 - INFO - Frame 566 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:00,243 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:00,243 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:00,394 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:00,395 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:00,544 - INFO - Frame 568 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:00,545 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:00,549 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:00,702 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:00,702 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:00,866 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:00,867 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:00,884 - INFO - Frame 570 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:01,019 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:01,019 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:01,171 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:01,171 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:01,329 - INFO - Frame 572 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:01,331 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:01,332 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:01,477 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:01,478 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:01,627 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:01,628 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:01,642 - INFO - Frame 574 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:01,771 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:01,772 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:01,919 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:01,922 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:02,075 - INFO - Frame 576 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:02,079 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:02,079 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:02,225 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:02,225 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:02,373 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:02,373 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:02,387 - INFO - Frame 578 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:02,536 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:02,536 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:02,690 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:02,690 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:02,844 - INFO - Frame 580 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:02,848 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:02,848 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:02,996 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:02,997 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:03,157 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:03,158 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:03,171 - INFO - Frame 582 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:03,309 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:03,311 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:03,460 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:03,462 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:03,615 - INFO - Frame 584 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:03,617 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:03,620 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:03,767 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:03,767 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:03,918 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:03,919 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:03,949 - INFO - Frame 586 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:04,076 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:04,076 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:04,277 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:04,280 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:04,430 - INFO - Frame 588 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:04,432 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:04,434 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:04,565 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:04,567 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:04,714 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:04,716 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:04,728 - INFO - Frame 590 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:04,860 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:04,860 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:05,018 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:05,018 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:05,165 - INFO - Frame 592 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:05,167 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:05,168 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:05,312 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:05,312 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:05,471 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:05,473 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:05,485 - INFO - Frame 594 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:05,619 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:05,619 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:05,793 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:05,793 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:05,944 - INFO - Frame 596 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:05,944 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:05,944 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:06,088 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:06,088 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:06,252 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:06,252 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:06,265 - INFO - Frame 598 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:06,401 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:06,402 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:06,555 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:06,557 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:06,698 - INFO - Frame 600 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:06,699 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:06,700 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:06,835 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:06,836 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:06,993 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:06,993 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:07,025 - INFO - Frame 602 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:07,147 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:07,147 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:07,309 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:07,309 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:07,344 - INFO - Frame 604 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:07,458 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:07,458 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:07,608 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:07,610 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:07,764 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:07,764 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:07,778 - INFO - Frame 606 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:07,916 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:07,917 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:08,070 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:08,071 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:08,222 - INFO - Frame 608 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:08,225 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:08,226 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:08,377 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:08,377 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:08,522 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:08,522 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:08,540 - INFO - Frame 610 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:08,674 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:08,674 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:08,829 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:08,830 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:08,936 - INFO - Frame 612 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:08,993 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:08,994 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:09,144 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:09,145 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:09,291 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:09,292 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:09,305 - INFO - Frame 614 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:09,454 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:09,454 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:09,600 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:09,600 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:09,750 - INFO - Frame 616 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:09,754 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:09,754 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:09,905 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:09,907 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:10,053 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:10,054 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:10,068 - INFO - Frame 618 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:10,196 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:10,199 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:10,369 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:10,369 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:10,513 - INFO - Frame 620 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:10,515 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:10,516 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:10,652 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:10,653 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:10,810 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:10,810 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:10,828 - INFO - Frame 622 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:10,956 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:10,956 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:11,113 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:11,116 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:11,257 - INFO - Frame 624 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:11,261 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:11,262 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:11,413 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:11,413 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:11,562 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:11,563 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:11,577 - INFO - Frame 626 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:11,717 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:11,718 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:11,885 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:11,886 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:12,037 - INFO - Frame 628 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:12,040 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:12,041 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:12,185 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:12,186 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:12,345 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:12,346 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:12,364 - INFO - Frame 630 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:12,503 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:12,503 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:12,654 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:12,656 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:12,806 - INFO - Frame 632 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:12,808 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:12,809 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:12,959 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:12,959 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:13,106 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:13,107 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:13,137 - INFO - Frame 634 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:13,261 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:13,261 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:13,418 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:13,419 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:13,558 - INFO - Frame 636 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:13,560 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:13,562 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:13,710 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:13,711 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:13,860 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:13,860 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:13,874 - INFO - Frame 638 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:14,018 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:14,018 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:14,165 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:14,165 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:14,308 - INFO - Frame 640 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:14,309 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:14,311 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:14,462 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:14,462 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:14,625 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:14,626 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:14,640 - INFO - Frame 642 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:14,764 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:14,764 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:14,911 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:14,915 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:15,057 - INFO - Frame 644 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:15,061 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:15,061 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:15,211 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:15,212 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:15,358 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:15,361 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:15,376 - INFO - Frame 646 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:15,514 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:15,516 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:15,678 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:15,678 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:15,818 - INFO - Frame 648 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:15,823 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:15,823 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:15,971 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:15,971 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:16,132 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:16,132 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:16,146 - INFO - Frame 650 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:16,289 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:16,289 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:16,441 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:16,441 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:16,475 - INFO - Frame 652 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:16,586 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:16,587 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:16,746 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:16,747 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:16,889 - INFO - Frame 654 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:16,891 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:16,892 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:17,034 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:17,036 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:17,182 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:17,184 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:17,198 - INFO - Frame 656 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:17,325 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:17,326 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:17,483 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:17,483 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:17,631 - INFO - Frame 658 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:17,633 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:17,637 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:17,783 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:17,784 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:17,941 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:17,941 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:17,954 - INFO - Frame 660 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:18,101 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:18,101 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:18,257 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:18,260 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:18,408 - INFO - Frame 662 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:18,410 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:18,411 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:18,551 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:18,551 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:18,708 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:18,708 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:18,722 - INFO - Frame 664 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:18,885 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:18,885 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:19,034 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:19,034 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:19,183 - INFO - Frame 666 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:19,185 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:19,186 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:19,342 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:19,343 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:19,516 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:19,517 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:19,528 - INFO - Frame 668 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:19,670 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:19,674 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:19,831 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:19,836 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:19,980 - INFO - Frame 670 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:19,983 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:19,983 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:20,131 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:20,134 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:20,295 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:20,296 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:20,311 - INFO - Frame 672 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:20,449 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:20,450 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:20,611 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:20,612 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:20,646 - INFO - Frame 674 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:20,764 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:20,765 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:20,925 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:20,925 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:21,080 - INFO - Frame 676 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:21,082 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:21,083 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:21,229 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:21,231 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:21,383 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:21,383 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:21,396 - INFO - Frame 678 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:21,546 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:21,546 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:21,703 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:21,707 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:21,847 - INFO - Frame 680 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:21,850 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:21,850 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:22,002 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:22,003 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:22,158 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:22,160 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:22,174 - INFO - Frame 682 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:22,306 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:22,306 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:22,451 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:22,452 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:22,612 - INFO - Frame 684 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:22,616 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:22,616 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:22,756 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:22,757 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:22,911 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:22,915 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:22,929 - INFO - Frame 686 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:23,069 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:23,069 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:23,218 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:23,219 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:23,314 - INFO - Frame 688 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:23,378 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:23,378 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:23,521 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:23,521 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:23,672 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:23,673 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:23,686 - INFO - Frame 690 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:23,823 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:23,823 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:23,968 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:23,969 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:24,006 - INFO - Frame 692 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:24,120 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:24,121 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:24,287 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:24,288 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:24,427 - INFO - Frame 694 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:24,430 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:24,430 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:24,588 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:24,588 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:24,742 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:24,743 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:24,756 - INFO - Frame 696 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:24,890 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:24,894 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:25,043 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:25,043 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:25,080 - INFO - Frame 698 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:25,190 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:25,191 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:25,350 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:25,354 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:25,497 - INFO - Frame 700 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:25,499 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:25,499 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:25,655 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:25,655 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:25,807 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:25,807 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:25,822 - INFO - Frame 702 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:25,977 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:25,977 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:26,125 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:26,126 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:26,275 - INFO - Frame 704 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:26,279 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:26,279 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:26,427 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:26,428 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:26,567 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:26,567 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:26,581 - INFO - Frame 706 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:26,701 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:26,701 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:26,868 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:26,868 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:27,013 - INFO - Frame 708 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:27,016 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:27,016 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:27,180 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:27,180 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:27,336 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:27,336 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:27,353 - INFO - Frame 710 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:27,484 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:27,485 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:27,643 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:27,644 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:27,793 - INFO - Frame 712 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:27,796 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:27,797 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:27,946 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:27,946 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:28,095 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:28,095 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:28,110 - INFO - Frame 714 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:28,246 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:28,246 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:28,406 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:28,407 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:28,568 - INFO - Frame 716 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:28,570 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:28,571 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:28,715 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:28,715 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:28,871 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:28,872 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:28,888 - INFO - Frame 718 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:29,020 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:29,024 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:29,175 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:29,176 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:29,331 - INFO - Frame 720 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:29,334 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:29,335 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:29,482 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:29,482 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:29,630 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:29,630 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:29,644 - INFO - Frame 722 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:29,821 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:29,821 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:29,977 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:29,978 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:30,012 - INFO - Frame 724 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:30,132 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:30,132 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:30,286 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:30,286 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:30,382 - INFO - Frame 726 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:30,442 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:30,443 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:30,594 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:30,603 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:30,752 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:30,753 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:30,767 - INFO - Frame 728 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:30,900 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:30,900 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:31,064 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:31,068 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:31,217 - INFO - Frame 730 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:31,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:31,221 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:31,368 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:31,373 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:31,520 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:31,522 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:31,536 - INFO - Frame 732 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:31,679 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:31,680 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:31,836 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:31,836 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:31,873 - INFO - Frame 734 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:31,982 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:31,982 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:32,148 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:32,150 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:32,247 - INFO - Frame 736 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:32,304 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:32,305 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:32,440 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:32,442 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:32,581 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:32,583 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:32,596 - INFO - Frame 738 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:32,730 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:32,734 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:32,881 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:32,881 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:33,024 - INFO - Frame 740 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:33,028 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:33,029 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:33,186 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:33,189 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:33,343 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:33,348 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:33,359 - INFO - Frame 742 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:33,493 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:33,495 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:33,638 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:33,642 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:33,810 - INFO - Frame 744 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:33,812 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:33,812 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:33,956 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:33,956 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:34,111 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:34,111 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:34,126 - INFO - Frame 746 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:34,259 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:34,262 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:34,421 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:34,421 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:34,570 - INFO - Frame 748 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:34,571 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:34,572 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:34,730 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:34,733 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:34,883 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:34,883 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:34,897 - INFO - Frame 750 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:35,042 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:35,043 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:35,193 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:35,195 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:35,230 - INFO - Frame 752 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:35,360 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:35,360 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:35,516 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:35,516 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:35,664 - INFO - Frame 754 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:35,667 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:35,668 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:35,836 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:35,838 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:35,984 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:35,984 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:35,999 - INFO - Frame 756 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:36,129 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:36,129 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:36,285 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:36,286 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:36,438 - INFO - Frame 758 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:36,441 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:36,442 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:36,599 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:36,599 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:36,750 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:36,752 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:36,768 - INFO - Frame 760 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:36,911 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:36,912 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:37,059 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:37,062 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:37,203 - INFO - Frame 762 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:37,205 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:37,207 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:37,363 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:37,364 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:37,511 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:37,512 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:37,526 - INFO - Frame 764 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:37,651 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:37,651 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:37,801 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:37,805 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:37,946 - INFO - Frame 766 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:37,948 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:37,948 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:38,098 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:38,105 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:38,259 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:38,259 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:38,272 - INFO - Frame 768 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:38,427 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:38,429 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:38,586 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:38,588 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:38,623 - INFO - Frame 770 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:38,743 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:38,743 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:38,891 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:38,892 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:38,929 - INFO - Frame 772 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:39,046 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:39,047 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:39,196 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:39,197 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:39,361 - INFO - Frame 774 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:39,363 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:39,364 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:39,512 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:39,515 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:39,675 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:39,675 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:39,689 - INFO - Frame 776 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:39,819 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:39,819 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:39,964 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:39,964 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:40,132 - INFO - Frame 778 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:40,137 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:40,137 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:40,300 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:40,301 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:40,468 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:40,469 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:40,483 - INFO - Frame 780 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:40,613 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:40,614 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:40,760 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:40,760 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:40,914 - INFO - Frame 782 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:40,915 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:40,916 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:41,061 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:41,061 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:41,225 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:41,225 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:41,239 - INFO - Frame 784 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:41,380 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:41,381 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:41,529 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:41,534 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:41,664 - INFO - Frame 786 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:41,668 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:41,671 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:41,812 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:41,813 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:41,968 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:41,968 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:41,981 - INFO - Frame 788 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:42,109 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:42,109 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:42,272 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:42,272 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:42,422 - INFO - Frame 790 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:42,426 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:42,426 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:42,568 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:42,569 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:42,721 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:42,722 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:42,739 - INFO - Frame 792 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:42,872 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:42,873 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:43,027 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:43,029 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:43,171 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:43,171 - INFO - Frame 794 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:43,171 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:43,328 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:43,329 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:43,480 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:43,480 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:43,492 - INFO - Frame 796 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:43,631 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:43,631 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:43,779 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:43,779 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:43,932 - INFO - Frame 798 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:43,933 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:43,934 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:44,088 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:44,088 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:44,260 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:44,261 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:44,277 - INFO - Frame 800 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:44,450 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:44,454 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:44,603 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:44,603 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:44,744 - INFO - Frame 802 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:44,747 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:44,749 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:44,908 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:44,909 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:45,064 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:45,065 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:45,078 - INFO - Frame 804 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:45,225 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:45,227 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:45,363 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:45,366 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:45,515 - INFO - Frame 806 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:45,518 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:45,518 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:45,677 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:45,679 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:45,825 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:45,825 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:45,842 - INFO - Frame 808 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:45,975 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:45,976 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:46,149 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:46,150 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:46,299 - INFO - Frame 810 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:46,300 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:46,305 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:46,445 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:46,446 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:46,596 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:46,596 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:46,611 - INFO - Frame 812 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:46,745 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:46,747 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:46,910 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:46,910 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:47,050 - INFO - Frame 814 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:47,054 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:47,055 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:47,197 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:47,202 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:47,354 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:47,355 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:47,370 - INFO - Frame 816 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:47,522 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:47,524 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:47,683 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:47,684 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:47,840 - INFO - Frame 818 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:47,843 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:47,844 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:47,988 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:47,988 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:48,143 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:48,143 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:48,157 - INFO - Frame 820 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:48,284 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:48,287 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:48,437 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:48,440 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:48,584 - INFO - Frame 822 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:48,585 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:48,586 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:48,737 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:48,738 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:48,914 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:48,918 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:48,928 - INFO - Frame 824 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:49,059 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:49,060 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:49,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:49,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:49,361 - INFO - Frame 826 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:49,366 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:49,366 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:49,520 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:49,520 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:49,673 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:49,673 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:49,689 - INFO - Frame 828 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:49,829 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:49,829 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:49,995 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:49,995 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:50,131 - INFO - Frame 830 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:50,135 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:50,135 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:50,286 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:50,287 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:50,443 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:50,443 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:50,457 - INFO - Frame 832 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:50,595 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:50,596 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:50,761 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:50,763 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:50,910 - INFO - Frame 834 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:50,911 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:50,913 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:51,054 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:51,055 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:51,204 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:51,208 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:51,219 - INFO - Frame 836 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:51,360 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:51,360 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:51,531 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:51,537 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:51,681 - INFO - Frame 838 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:51,683 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:51,686 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:51,828 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:51,831 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:51,991 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:51,993 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:52,024 - INFO - Frame 840 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:52,141 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:52,142 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:52,292 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:52,292 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:52,329 - INFO - Frame 842 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:52,447 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:52,447 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:52,602 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:52,607 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:52,739 - INFO - Frame 844 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:52,742 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:52,743 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:52,897 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:52,897 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:53,055 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:53,056 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:53,069 - INFO - Frame 846 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:53,203 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:53,203 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:53,378 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:53,379 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:53,524 - INFO - Frame 848 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:53,526 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:53,527 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:53,673 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:53,673 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:53,825 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:53,825 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:53,839 - INFO - Frame 850 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:53,981 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:53,981 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:54,146 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:54,146 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:54,284 - INFO - Frame 852 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:54,286 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:54,288 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:54,437 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:54,438 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:54,606 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:54,606 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:54,620 - INFO - Frame 854 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:54,764 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:54,766 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:54,912 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:54,913 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:55,059 - INFO - Frame 856 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:55,061 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:55,063 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:55,202 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:55,203 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:55,365 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:55,365 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:55,378 - INFO - Frame 858 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:55,521 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:55,521 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:55,684 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:55,684 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:55,827 - INFO - Frame 860 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:55,827 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:55,828 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:55,981 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:55,983 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:56,127 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:56,127 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:56,143 - INFO - Frame 862 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:56,279 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:56,280 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:56,443 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:56,445 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:56,592 - INFO - Frame 864 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:56,595 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:56,596 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:56,744 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:56,746 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:56,902 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:56,904 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:56,918 - INFO - Frame 866 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:57,053 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:57,053 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:57,208 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:57,208 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:57,369 - INFO - Frame 868 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:57,372 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:57,373 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:57,522 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:57,523 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:57,684 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:57,684 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:57,698 - INFO - Frame 870 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:57,832 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:57,833 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:57,992 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:57,992 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:58,145 - INFO - Frame 872 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:58,146 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:58,147 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:58,306 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:58,311 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:58,457 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:58,461 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:58,472 - INFO - Frame 874 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:58,617 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:58,618 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:58,774 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:58,775 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:58,979 - INFO - Frame 876 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:58,981 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:58,982 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:59,136 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:59,141 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:59,291 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:59,291 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:59,306 - INFO - Frame 878 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:59,443 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:59,447 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:59,604 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:59,605 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:59,762 - INFO - Frame 880 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:40:59,766 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:59,766 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:59,928 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:40:59,929 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:00,078 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:00,079 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:00,094 - INFO - Frame 882 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:00,232 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:00,232 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:00,397 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:00,398 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:00,548 - INFO - Frame 884 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:00,553 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:00,553 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:00,711 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:00,711 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:00,866 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:00,866 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:00,878 - INFO - Frame 886 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:01,030 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:01,030 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:01,179 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:01,181 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:01,328 - INFO - Frame 888 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:01,330 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:01,331 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:01,481 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:01,481 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:01,649 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:01,649 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:01,663 - INFO - Frame 890 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:01,808 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:01,808 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:01,959 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:01,959 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:02,116 - INFO - Frame 892 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:02,120 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:02,121 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:02,263 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:02,264 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:02,415 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:02,415 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:02,429 - INFO - Frame 894 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:02,568 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:02,568 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:02,721 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:02,722 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:02,872 - INFO - Frame 896 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:02,875 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:02,878 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:03,056 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:03,057 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:03,210 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:03,212 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:03,225 - INFO - Frame 898 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:03,359 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:03,362 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:03,511 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:03,511 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:03,658 - INFO - Frame 900 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:03,660 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:03,661 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:03,829 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:03,830 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:03,982 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:03,985 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:03,999 - INFO - Frame 902 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:04,144 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:04,144 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:04,293 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:04,293 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:04,438 - INFO - Frame 904 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:04,442 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:04,444 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:04,590 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:04,592 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:04,758 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:04,758 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:04,774 - INFO - Frame 906 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:04,900 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:04,900 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:05,058 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:05,059 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:05,207 - INFO - Frame 908 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:05,211 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:05,211 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:05,369 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:05,370 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:05,523 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:05,524 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:05,552 - INFO - Frame 910 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:05,692 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:05,693 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:05,842 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:05,843 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:05,991 - INFO - Frame 912 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:05,992 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:05,992 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:06,151 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:06,151 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:06,305 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:06,306 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:06,320 - INFO - Frame 914 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:06,454 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:06,454 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:06,606 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:06,606 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:06,751 - INFO - Frame 916 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:06,755 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:06,756 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:06,909 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:06,910 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:07,064 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:07,066 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:07,078 - INFO - Frame 918 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:07,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:07,221 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:07,384 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:07,385 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:07,534 - INFO - Frame 920 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:07,536 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:07,536 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:07,694 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:07,694 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:07,861 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:07,862 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:07,875 - INFO - Frame 922 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:08,006 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:08,006 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:08,170 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:08,173 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:08,312 - INFO - Frame 924 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:08,315 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:08,316 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:08,475 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:08,477 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:08,623 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:08,623 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:08,638 - INFO - Frame 926 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:08,781 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:08,781 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:08,940 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:08,941 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:09,088 - INFO - Frame 928 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:09,092 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:09,093 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:09,237 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:09,237 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:09,391 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:09,395 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:09,407 - INFO - Frame 930 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:09,542 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:09,543 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:09,693 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:09,695 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:09,856 - INFO - Frame 932 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:09,859 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:09,862 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:10,011 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:10,012 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:10,166 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:10,167 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:10,180 - INFO - Frame 934 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:10,320 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:10,320 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:10,466 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:10,466 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:10,616 - INFO - Frame 936 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:10,618 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:10,621 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:10,772 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:10,773 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:10,942 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:10,942 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:10,958 - INFO - Frame 938 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:11,097 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:11,097 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:11,262 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:11,262 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:11,430 - INFO - Frame 940 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:11,431 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:11,431 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:11,594 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:11,594 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:11,751 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:11,751 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:11,765 - INFO - Frame 942 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:11,913 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:11,913 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:12,075 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:12,075 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:12,230 - INFO - Frame 944 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:12,234 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:12,236 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:12,375 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:12,378 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:12,536 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:12,536 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:12,549 - INFO - Frame 946 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:12,694 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:12,695 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:12,851 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:12,851 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:12,998 - INFO - Frame 948 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:13,000 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:13,000 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:13,144 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:13,145 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:13,300 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:13,300 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:13,313 - INFO - Frame 950 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:13,446 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:13,446 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:13,632 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:13,632 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:13,780 - INFO - Frame 952 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:13,781 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:13,782 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:13,935 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:13,935 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:14,097 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:14,099 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:14,113 - INFO - Frame 954 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:14,252 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:14,252 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:14,413 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:14,413 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:14,573 - INFO - Frame 956 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:14,574 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:14,574 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:14,722 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:14,723 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:14,898 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:14,898 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:14,931 - INFO - Frame 958 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:15,069 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:15,070 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:15,252 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:15,253 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:15,409 - INFO - Frame 960 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:15,412 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:15,412 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:15,560 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:15,565 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:15,720 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:15,721 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:15,749 - INFO - Frame 962 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:15,875 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:15,877 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:16,026 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:16,028 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:16,187 - INFO - Frame 964 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:16,193 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:16,193 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:16,328 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:16,329 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:16,473 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:16,476 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:16,491 - INFO - Frame 966 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:16,621 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:16,622 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:16,780 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:16,780 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:16,929 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:16,929 - INFO - Frame 968 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:16,929 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:17,086 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:17,088 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:17,243 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:17,243 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:17,257 - INFO - Frame 970 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:17,393 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:17,393 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:17,560 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:17,564 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:17,705 - INFO - Frame 972 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:17,706 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:17,706 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:17,861 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:17,862 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:18,023 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:18,028 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:18,040 - INFO - Frame 974 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:18,194 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:18,194 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:18,356 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:18,356 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:18,507 - INFO - Frame 976 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:18,509 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:18,509 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:18,659 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:18,659 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:18,813 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:18,813 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:18,829 - INFO - Frame 978 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:18,970 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:18,970 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:19,133 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:19,134 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:19,308 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:19,308 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:19,308 - INFO - Frame 980 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:19,475 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:19,476 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:19,677 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:19,695 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:19,704 - INFO - Frame 982 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:19,836 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:19,836 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:19,989 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:19,994 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:20,149 - INFO - Frame 984 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:20,152 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:20,152 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:20,303 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:20,304 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:20,456 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:20,458 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:20,472 - INFO - Frame 986 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:20,615 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:20,615 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:20,775 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:20,776 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:20,928 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:20,929 - INFO - Frame 988 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:20,931 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:21,076 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:21,077 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:21,238 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:21,238 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:21,252 - INFO - Frame 990 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:21,379 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:21,379 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:21,539 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:21,539 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:21,682 - INFO - Frame 992 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:21,685 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:21,685 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:21,839 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:21,842 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:21,994 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:21,994 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:22,008 - INFO - Frame 994 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:22,162 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:22,165 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:22,327 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:22,328 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:22,473 - INFO - Frame 996 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:22,475 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:22,475 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:22,626 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:22,627 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:22,779 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:22,780 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:22,796 - INFO - Frame 998 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:22,935 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:22,936 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:23,088 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:23,088 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:23,241 - INFO - Frame 1000 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:23,245 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:23,245 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:23,406 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:23,410 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:23,573 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:23,573 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:23,591 - INFO - Frame 1002 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:23,727 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:23,728 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:23,880 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:23,880 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:24,028 - INFO - Frame 1004 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:24,032 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:24,032 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:24,183 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:24,189 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:24,340 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:24,340 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:24,357 - INFO - Frame 1006 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:24,494 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:24,494 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:24,662 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:24,662 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:24,807 - INFO - Frame 1008 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:24,811 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:24,812 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:24,965 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:24,973 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:25,117 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:25,117 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:25,147 - INFO - Frame 1010 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:25,284 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:25,284 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:25,443 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:25,445 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:25,587 - INFO - Frame 1012 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:25,590 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:25,591 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:25,737 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:25,737 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:25,888 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:25,889 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:25,919 - INFO - Frame 1014 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:26,044 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:26,045 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:26,191 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:26,194 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:26,342 - INFO - Frame 1016 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:26,343 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:26,345 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:26,498 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:26,499 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:26,659 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:26,659 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:26,676 - INFO - Frame 1018 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:26,822 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:26,822 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:26,972 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:26,972 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:27,137 - INFO - Frame 1020 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:27,141 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:27,142 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:27,296 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:27,297 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:27,457 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:27,459 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:27,475 - INFO - Frame 1022 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:27,603 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:27,604 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:27,763 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:27,764 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:27,911 - INFO - Frame 1024 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:27,916 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:27,916 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:28,061 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:28,064 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:28,214 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:28,214 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:28,228 - INFO - Frame 1026 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:28,364 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:28,364 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:28,519 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:28,521 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:28,657 - INFO - Frame 1028 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:28,659 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:28,660 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:28,810 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:28,815 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:28,954 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:28,954 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:28,970 - INFO - Frame 1030 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:29,125 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:29,125 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:29,278 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:29,280 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:29,436 - INFO - Frame 1032 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:29,439 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:29,440 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:29,582 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:29,583 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:29,738 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:29,738 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:29,752 - INFO - Frame 1034 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:29,879 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:29,879 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:30,031 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:30,032 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:30,065 - INFO - Frame 1036 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:30,194 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:30,194 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:30,371 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:30,372 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:30,535 - INFO - Frame 1038 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:30,539 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:30,539 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:30,699 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:30,700 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:30,855 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:30,855 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:30,870 - INFO - Frame 1040 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:31,003 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:31,004 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:31,169 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:31,169 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:31,336 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:31,336 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:31,336 - INFO - Frame 1042 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:31,483 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:31,483 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:31,639 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:31,639 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:31,652 - INFO - Frame 1044 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:31,786 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:31,786 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:31,956 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:31,957 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:32,106 - INFO - Frame 1046 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:32,110 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:32,110 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:32,281 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:32,282 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:32,435 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:32,435 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:32,447 - INFO - Frame 1048 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:32,583 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:32,586 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:32,735 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:32,737 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:32,894 - INFO - Frame 1050 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:32,896 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:32,897 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:33,050 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:33,052 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:33,203 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:33,203 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:33,219 - INFO - Frame 1052 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:33,353 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:33,353 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:33,509 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:33,509 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:33,658 - INFO - Frame 1054 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:33,662 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:33,662 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:33,814 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:33,816 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:33,960 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:33,961 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:33,974 - INFO - Frame 1056 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:34,116 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:34,116 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:34,287 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:34,291 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:34,434 - INFO - Frame 1058 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:34,436 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:34,438 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:34,593 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:34,593 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:34,751 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:34,752 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:34,765 - INFO - Frame 1060 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:34,914 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:34,914 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:35,079 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:35,081 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:35,219 - INFO - Frame 1062 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:35,223 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:35,224 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:35,366 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:35,366 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:35,522 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:35,522 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:35,536 - INFO - Frame 1064 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:35,669 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:35,670 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:35,827 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:35,827 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:35,975 - INFO - Frame 1066 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:35,976 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:35,977 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:36,138 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:36,139 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:36,293 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:36,293 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:36,307 - INFO - Frame 1068 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:36,445 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:36,446 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:36,597 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:36,598 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:36,752 - INFO - Frame 1070 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:36,753 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:36,754 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:36,906 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:36,906 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:37,070 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:37,070 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:37,081 - INFO - Frame 1072 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:37,237 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:37,237 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:37,393 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:37,393 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:37,539 - INFO - Frame 1074 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:37,543 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:37,543 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:37,690 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:37,690 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:37,846 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:37,846 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:37,860 - INFO - Frame 1076 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:37,992 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:37,995 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:38,152 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:38,156 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:38,303 - INFO - Frame 1078 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:38,304 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:38,305 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:38,460 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:38,460 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:38,622 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:38,625 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:38,635 - INFO - Frame 1080 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:38,773 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:38,773 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:38,931 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:38,932 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:39,083 - INFO - Frame 1082 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:39,084 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:39,084 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:39,254 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:39,254 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:39,416 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:39,416 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:39,429 - INFO - Frame 1084 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:39,579 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:39,579 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:39,724 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:39,726 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:39,883 - INFO - Frame 1086 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:39,885 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:39,886 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:40,036 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:40,042 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:40,184 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:40,188 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:40,201 - INFO - Frame 1088 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:40,337 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:40,338 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:40,496 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:40,497 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:40,647 - INFO - Frame 1090 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:40,652 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:40,655 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:40,803 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:40,803 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:40,961 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:40,962 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:40,976 - INFO - Frame 1092 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:41,127 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:41,129 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:41,292 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:41,292 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:41,436 - INFO - Frame 1094 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:41,440 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:41,441 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:41,603 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:41,604 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:41,772 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:41,773 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:41,786 - INFO - Frame 1096 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:41,928 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:41,928 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:42,086 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:42,089 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:42,234 - INFO - Frame 1098 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:42,238 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:42,238 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:42,375 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:42,376 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:42,530 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:42,534 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:42,547 - INFO - Frame 1100 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:42,701 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:42,701 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:42,854 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:42,854 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:42,998 - INFO - Frame 1102 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:43,000 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:43,001 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:43,164 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:43,165 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:43,320 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:43,320 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:43,333 - INFO - Frame 1104 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:43,472 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:43,472 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:43,633 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:43,633 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:43,794 - INFO - Frame 1106 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:43,796 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:43,796 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:43,946 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:43,947 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:44,110 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:44,110 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:44,126 - INFO - Frame 1108 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:44,259 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:44,260 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:44,421 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:44,423 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:44,593 - INFO - Frame 1110 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:44,596 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:44,597 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:44,746 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:44,746 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:44,907 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:44,907 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:44,921 - INFO - Frame 1112 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:45,066 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:45,066 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:45,211 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:45,212 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:45,363 - INFO - Frame 1114 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:45,366 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:45,367 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:45,505 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:45,512 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:45,670 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:45,670 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:45,684 - INFO - Frame 1116 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:45,824 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:45,825 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:45,986 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:45,987 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:46,133 - INFO - Frame 1118 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:46,135 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:46,135 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:46,286 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:46,287 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:46,429 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:46,430 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:46,443 - INFO - Frame 1120 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:46,587 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:46,587 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:46,753 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:46,753 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:46,920 - INFO - Frame 1122 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:46,922 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:46,922 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:47,070 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:47,071 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:47,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:47,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:47,232 - INFO - Frame 1124 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:47,375 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:47,376 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:47,541 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:47,542 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:47,684 - INFO - Frame 1126 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:47,686 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:47,686 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:47,847 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:47,848 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:48,004 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:48,007 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:48,019 - INFO - Frame 1128 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:48,170 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:48,170 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:48,338 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:48,339 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:48,491 - INFO - Frame 1130 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:48,493 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:48,494 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:48,643 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:48,643 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:48,793 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:48,795 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:48,808 - INFO - Frame 1132 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:48,946 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:48,947 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:49,113 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:49,113 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:49,268 - INFO - Frame 1134 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:49,270 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:49,271 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:49,422 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:49,425 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:49,580 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:49,581 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:49,595 - INFO - Frame 1136 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:49,737 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:49,737 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:49,899 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:49,899 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:50,001 - INFO - Frame 1138 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:50,067 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:50,068 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:50,218 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:50,218 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:50,363 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:50,364 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:50,377 - INFO - Frame 1140 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:50,528 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:50,528 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:50,688 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:50,688 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:50,843 - INFO - Frame 1142 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:50,847 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:50,847 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:50,991 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:50,994 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:51,155 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:51,156 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:51,167 - INFO - Frame 1144 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:51,315 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:51,317 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:51,469 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:51,472 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:51,624 - INFO - Frame 1146 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:51,626 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:51,627 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:51,773 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:51,774 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:51,932 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:51,932 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:51,946 - INFO - Frame 1148 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:52,087 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:52,087 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:52,248 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:52,248 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:52,397 - INFO - Frame 1150 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:52,400 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:52,400 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:52,553 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:52,554 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:52,715 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:52,716 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:52,860 - INFO - Frame 1152 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:52,864 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:52,864 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:53,019 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:53,025 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:53,174 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:53,174 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:53,188 - INFO - Frame 1154 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:53,322 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:53,323 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:53,478 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:53,479 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:53,629 - INFO - Frame 1156 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:53,631 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:53,632 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:53,786 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:53,786 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:53,950 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:53,953 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:53,964 - INFO - Frame 1158 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:54,103 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:54,103 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:54,259 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:54,259 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:54,407 - INFO - Frame 1160 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:54,411 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:54,411 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:54,570 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:54,571 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:54,721 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:54,721 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:54,735 - INFO - Frame 1162 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:54,877 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:54,880 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:55,029 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:55,029 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:55,168 - INFO - Frame 1164 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:55,170 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:55,171 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:55,320 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:55,321 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:55,493 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:55,494 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:55,509 - INFO - Frame 1166 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:55,635 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:55,635 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:55,795 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:55,796 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:55,955 - INFO - Frame 1168 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:55,960 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:55,960 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:56,113 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:56,113 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:56,270 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:56,272 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:56,282 - INFO - Frame 1170 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:56,433 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:56,433 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:56,594 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:56,596 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:56,743 - INFO - Frame 1172 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:56,747 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:56,747 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:56,900 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:56,901 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:57,062 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:57,065 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:57,077 - INFO - Frame 1174 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:57,215 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:57,216 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:57,395 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:57,395 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:57,555 - INFO - Frame 1176 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:57,557 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:57,560 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:57,705 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:57,706 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:57,858 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:57,858 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:57,871 - INFO - Frame 1178 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:58,007 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:58,007 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:58,159 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:58,159 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:58,313 - INFO - Frame 1180 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:58,314 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:58,314 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:58,490 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:58,491 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:58,655 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:58,656 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:58,669 - INFO - Frame 1182 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:58,811 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:58,812 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:58,969 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:58,969 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:59,119 - INFO - Frame 1184 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:59,123 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:59,123 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:59,271 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:59,275 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:59,427 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:59,427 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:59,443 - INFO - Frame 1186 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:59,582 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:59,582 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:59,766 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:59,770 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:59,923 - INFO - Frame 1188 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:41:59,925 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:41:59,927 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:00,078 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:00,078 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:00,230 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:00,230 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:00,245 - INFO - Frame 1190 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:00,412 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:00,413 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:00,561 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:00,562 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:00,597 - INFO - Frame 1192 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:00,716 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:00,717 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:00,879 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:00,880 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:01,023 - INFO - Frame 1194 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:01,024 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:01,024 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:01,190 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:01,196 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:01,347 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:01,348 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:01,362 - INFO - Frame 1196 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:01,498 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:01,499 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:01,643 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:01,644 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:01,798 - INFO - Frame 1198 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:01,802 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:01,803 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:01,950 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:01,951 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:02,114 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:02,114 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:02,127 - INFO - Frame 1200 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:02,270 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:02,270 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:02,423 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:02,424 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:02,574 - INFO - Frame 1202 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:02,577 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:02,577 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:02,728 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:02,729 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:02,896 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:02,897 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:02,908 - INFO - Frame 1204 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:03,044 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:03,045 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:03,217 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:03,217 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:03,347 - INFO - Frame 1206 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:03,351 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:03,351 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:03,487 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:03,487 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:03,638 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:03,639 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:03,653 - INFO - Frame 1208 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:03,788 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:03,788 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:03,943 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:03,947 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:04,088 - INFO - Frame 1210 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:04,092 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:04,092 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:04,257 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:04,257 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:04,426 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:04,429 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:04,444 - INFO - Frame 1212 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:04,579 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:04,579 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:04,739 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:04,739 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:04,910 - INFO - Frame 1214 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:04,914 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:04,914 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:05,060 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:05,062 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:05,210 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:05,210 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:05,229 - INFO - Frame 1216 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:05,360 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:05,360 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:05,521 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:05,522 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:05,658 - INFO - Frame 1218 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:05,662 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:05,663 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:05,815 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:05,822 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:05,973 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:05,975 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:05,988 - INFO - Frame 1220 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:06,115 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:06,116 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:06,276 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:06,279 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:06,427 - INFO - Frame 1222 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:06,430 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:06,431 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:06,584 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:06,585 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:06,747 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:06,748 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:06,760 - INFO - Frame 1224 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:06,893 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:06,894 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:07,047 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:07,047 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:07,082 - INFO - Frame 1226 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:07,198 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:07,198 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:07,357 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:07,357 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:07,507 - INFO - Frame 1228 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:07,511 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:07,511 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:07,672 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:07,677 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:07,837 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:07,837 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:07,851 - INFO - Frame 1230 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:08,003 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:08,003 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:08,167 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:08,168 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:08,308 - INFO - Frame 1232 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:08,313 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:08,315 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:08,471 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:08,471 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:08,628 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:08,628 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:08,642 - INFO - Frame 1234 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:08,776 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:08,776 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:08,936 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:08,936 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:08,972 - INFO - Frame 1236 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:09,104 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:09,106 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:09,281 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:09,282 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:09,430 - INFO - Frame 1238 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:09,434 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:09,434 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:09,583 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:09,585 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:09,736 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:09,737 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:09,754 - INFO - Frame 1240 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:09,887 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:09,887 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:10,046 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:10,046 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:10,183 - INFO - Frame 1242 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:10,187 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:10,188 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:10,355 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:10,355 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:10,505 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:10,508 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:10,521 - INFO - Frame 1244 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:10,657 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:10,657 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:10,811 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:10,811 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:10,963 - INFO - Frame 1246 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:10,965 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:10,965 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:11,141 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:11,144 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:11,301 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:11,301 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:11,315 - INFO - Frame 1248 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:11,455 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:11,455 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:11,612 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:11,612 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:11,762 - INFO - Frame 1250 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:11,764 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:11,764 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:11,927 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:11,932 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:12,077 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:12,079 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:12,092 - INFO - Frame 1252 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:12,228 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:12,228 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:12,378 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:12,379 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:12,539 - INFO - Frame 1254 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:12,543 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:12,546 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:12,690 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:12,690 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:12,852 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:12,853 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:12,866 - INFO - Frame 1256 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:13,015 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:13,015 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:13,176 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:13,176 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:13,324 - INFO - Frame 1258 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:13,325 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:13,327 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:13,486 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:13,486 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:13,634 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:13,634 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:13,649 - INFO - Frame 1260 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:13,788 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:13,789 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:13,952 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:13,956 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:14,099 - INFO - Frame 1262 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:14,101 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:14,101 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:14,254 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:14,254 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:14,407 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:14,407 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:14,440 - INFO - Frame 1264 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:14,575 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:14,576 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:14,735 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:14,735 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:14,884 - INFO - Frame 1266 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:14,888 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:14,889 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:15,042 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:15,042 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:15,215 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:15,216 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:15,230 - INFO - Frame 1268 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:15,361 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:15,361 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:15,509 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:15,510 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:15,669 - INFO - Frame 1270 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:15,670 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:15,670 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:15,813 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:15,816 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:15,965 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:15,966 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:15,983 - INFO - Frame 1272 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:16,113 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:16,113 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:16,282 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:16,283 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:16,423 - INFO - Frame 1274 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:16,426 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:16,427 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:16,601 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:16,601 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:16,753 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:16,753 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:16,768 - INFO - Frame 1276 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:16,905 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:16,905 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:17,060 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:17,061 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:17,216 - INFO - Frame 1278 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:17,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:17,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:17,370 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:17,373 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:17,541 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:17,545 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:17,556 - INFO - Frame 1280 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:17,691 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:17,693 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:17,852 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:17,856 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:18,001 - INFO - Frame 1282 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:18,005 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:18,005 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:18,156 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:18,157 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:18,302 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:18,302 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:18,315 - INFO - Frame 1284 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:18,465 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:18,465 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:18,610 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:18,613 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:18,647 - INFO - Frame 1286 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:18,760 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:18,764 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:18,917 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:18,922 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:19,059 - INFO - Frame 1288 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:19,059 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:19,059 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:19,212 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:19,213 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:19,371 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:19,371 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:19,385 - INFO - Frame 1290 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:19,538 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:19,538 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:19,724 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:19,725 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:19,868 - INFO - Frame 1292 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:19,870 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:19,871 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:20,025 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:20,026 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:20,180 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:20,180 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:20,196 - INFO - Frame 1294 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:20,334 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:20,334 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:20,498 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:20,501 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:20,668 - INFO - Frame 1296 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:20,671 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:20,673 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:20,820 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:20,820 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:20,975 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:20,975 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:20,990 - INFO - Frame 1298 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:21,147 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:21,147 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:21,313 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:21,313 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:21,351 - INFO - Frame 1300 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:21,479 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:21,480 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:21,644 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:21,645 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:21,793 - INFO - Frame 1302 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:21,796 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:21,796 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:21,948 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:21,954 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:22,109 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:22,110 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:22,124 - INFO - Frame 1304 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:22,263 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:22,263 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:22,418 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:22,421 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:22,565 - INFO - Frame 1306 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:22,568 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:22,570 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:22,722 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:22,723 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:22,870 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:22,870 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:22,881 - INFO - Frame 1308 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:23,030 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:23,030 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:23,192 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:23,193 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:23,229 - INFO - Frame 1310 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:23,369 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:23,369 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:23,529 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:23,532 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:23,673 - INFO - Frame 1312 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:23,677 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:23,677 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:23,829 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:23,829 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:23,986 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:23,987 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:23,999 - INFO - Frame 1314 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:24,142 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:24,142 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:24,306 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:24,312 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:24,469 - INFO - Frame 1316 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:24,471 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:24,472 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:24,623 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:24,623 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:24,770 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:24,770 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:24,788 - INFO - Frame 1318 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:24,918 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:24,919 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:25,092 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:25,092 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:25,251 - INFO - Frame 1320 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:25,254 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:25,254 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:25,407 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:25,408 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:25,568 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:25,569 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:25,581 - INFO - Frame 1322 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:25,716 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:25,716 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:25,879 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:25,880 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:26,032 - INFO - Frame 1324 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:26,034 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:26,035 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:26,187 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:26,187 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:26,342 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:26,345 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:26,358 - INFO - Frame 1326 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:26,494 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:26,496 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:26,661 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:26,663 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:26,852 - INFO - Frame 1328 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:26,855 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:26,856 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:27,002 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:27,006 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:27,160 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:27,161 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:27,177 - INFO - Frame 1330 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:27,325 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:27,326 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:27,483 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:27,484 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:27,638 - INFO - Frame 1332 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:27,641 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:27,643 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:27,802 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:27,803 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:27,965 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:27,965 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:27,980 - INFO - Frame 1334 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:28,135 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:28,136 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:28,296 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:28,297 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:28,456 - INFO - Frame 1336 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:28,459 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:28,460 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:28,605 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:28,605 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:28,760 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:28,760 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:28,777 - INFO - Frame 1338 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:28,909 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:28,909 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:29,070 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:29,070 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:29,225 - INFO - Frame 1340 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:29,228 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:29,229 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:29,391 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:29,391 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:29,542 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:29,543 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:29,557 - INFO - Frame 1342 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:29,700 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:29,700 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:29,866 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:29,868 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:30,008 - INFO - Frame 1344 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:30,012 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:30,012 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:30,156 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:30,158 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:30,320 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:30,321 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:30,333 - INFO - Frame 1346 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:30,485 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:30,486 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:30,649 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:30,652 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:30,808 - INFO - Frame 1348 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:30,810 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:30,811 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:30,970 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:30,972 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:31,130 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:31,131 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:31,142 - INFO - Frame 1350 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:31,283 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:31,283 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:31,452 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:31,455 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:31,595 - INFO - Frame 1352 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:31,598 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:31,598 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:31,752 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:31,753 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:31,906 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:31,906 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:31,921 - INFO - Frame 1354 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:32,062 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:32,063 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:32,226 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:32,228 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:32,388 - INFO - Frame 1356 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:32,393 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:32,393 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:32,546 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:32,546 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:32,703 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:32,703 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:32,717 - INFO - Frame 1358 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:32,849 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:32,849 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:33,027 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:33,028 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:33,181 - INFO - Frame 1360 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:33,182 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:33,183 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:33,334 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:33,335 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:33,493 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:33,494 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:33,507 - INFO - Frame 1362 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:33,652 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:33,652 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:33,821 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:33,822 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:33,972 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:33,973 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:33,994 - INFO - Frame 1364 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:34,125 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:34,125 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:34,282 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:34,283 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:34,432 - INFO - Frame 1366 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:34,435 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:34,436 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:34,585 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:34,586 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:34,736 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:34,741 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:34,757 - INFO - Frame 1368 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:34,888 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:34,888 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:35,048 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:35,048 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:35,211 - INFO - Frame 1370 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:35,214 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:35,217 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:35,368 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:35,369 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:35,524 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:35,524 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:35,543 - INFO - Frame 1372 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:35,674 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:35,674 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:35,841 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:35,841 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:35,988 - INFO - Frame 1374 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:35,989 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:35,990 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:36,132 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:36,136 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:36,307 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:36,310 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:36,329 - INFO - Frame 1376 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:36,487 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:36,488 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:36,665 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:36,665 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:36,839 - INFO - Frame 1378 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:36,843 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:36,844 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:36,998 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:37,002 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:37,153 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:37,153 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:37,172 - INFO - Frame 1380 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:37,304 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:37,304 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:37,474 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:37,475 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:37,630 - INFO - Frame 1382 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:37,633 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:37,635 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:37,786 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:37,786 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:37,945 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:37,946 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:37,965 - INFO - Frame 1384 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:38,106 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:38,110 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:38,264 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:38,264 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:38,420 - INFO - Frame 1386 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:38,424 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:38,425 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:38,578 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:38,584 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:38,740 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:38,741 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:38,761 - INFO - Frame 1388 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:38,901 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:38,901 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:39,064 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:39,065 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:39,218 - INFO - Frame 1390 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:39,222 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:39,223 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:39,373 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:39,374 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:39,550 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:39,554 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:39,569 - INFO - Frame 1392 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:39,717 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:39,717 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:39,886 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:39,886 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:40,042 - INFO - Frame 1394 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:40,044 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:40,046 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:40,197 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:40,198 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:40,365 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:40,365 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:40,384 - INFO - Frame 1396 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:40,512 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:40,514 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:40,667 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:40,670 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:40,834 - INFO - Frame 1398 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:40,839 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:40,839 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:40,989 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:40,990 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:41,152 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:41,152 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:41,171 - INFO - Frame 1400 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:41,304 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:41,304 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:41,465 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:41,466 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:41,637 - INFO - Frame 1402 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:41,639 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:41,641 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:41,804 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:41,807 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:41,956 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:41,956 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:41,976 - INFO - Frame 1404 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:42,115 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:42,115 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:42,279 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:42,279 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:42,448 - INFO - Frame 1406 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:42,450 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:42,452 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:42,605 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:42,608 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:42,756 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:42,757 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:42,777 - INFO - Frame 1408 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:42,918 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:42,918 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:43,072 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:43,074 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:43,229 - INFO - Frame 1410 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:43,234 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:43,235 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:43,395 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:43,402 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:43,552 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:43,553 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:43,568 - INFO - Frame 1412 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:43,705 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:43,705 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:43,865 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:43,869 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:44,035 - INFO - Frame 1414 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:44,039 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:44,039 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:44,200 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:44,202 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:44,354 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:44,355 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:44,369 - INFO - Frame 1416 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:44,517 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:44,518 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:44,672 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:44,672 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:44,827 - INFO - Frame 1418 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:44,831 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:44,831 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:44,980 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:44,981 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:45,139 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:45,139 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:45,159 - INFO - Frame 1420 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:45,303 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:45,304 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:45,455 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:45,455 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:45,627 - INFO - Frame 1422 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:45,629 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:45,629 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:45,789 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:45,794 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:45,938 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:45,938 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:45,958 - INFO - Frame 1424 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:46,088 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:46,089 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:46,248 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:46,248 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:46,402 - INFO - Frame 1426 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:46,406 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:46,406 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:46,560 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:46,561 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:46,738 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:46,738 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:46,757 - INFO - Frame 1428 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:46,886 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:46,889 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:47,032 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:47,036 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:47,186 - INFO - Frame 1430 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:47,189 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:47,191 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:47,333 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:47,334 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:47,490 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:47,492 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:47,512 - INFO - Frame 1432 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:47,644 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:47,644 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:47,797 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:47,797 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:47,958 - INFO - Frame 1434 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:47,961 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:47,962 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:48,105 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:48,106 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:48,264 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:48,264 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:48,284 - INFO - Frame 1436 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:48,411 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:48,411 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:48,577 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:48,577 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:48,745 - INFO - Frame 1438 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:48,746 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:48,746 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:48,898 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:48,898 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:49,056 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:49,056 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:49,075 - INFO - Frame 1440 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:49,202 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:49,203 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:49,378 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:49,378 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:49,555 - INFO - Frame 1442 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:49,557 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:49,561 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:49,715 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:49,720 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:49,874 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:49,875 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:49,892 - INFO - Frame 1444 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:50,021 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:50,022 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:50,168 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:50,168 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:50,310 - INFO - Frame 1446 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:50,314 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:50,314 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:50,470 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:50,471 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:50,626 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:50,627 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:50,646 - INFO - Frame 1448 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:50,778 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:50,778 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:50,942 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:50,945 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:51,104 - INFO - Frame 1450 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:51,105 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:51,107 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:51,262 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:51,262 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:51,429 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:51,432 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:51,449 - INFO - Frame 1452 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:51,573 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:51,573 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:51,720 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:51,722 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:51,887 - INFO - Frame 1454 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:51,891 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:51,894 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:52,060 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:52,061 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:52,219 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:52,219 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:52,238 - INFO - Frame 1456 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:52,366 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:52,366 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:52,532 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:52,533 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:52,678 - INFO - Frame 1458 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:52,680 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:52,680 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:52,835 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:52,835 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:52,989 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:52,989 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:53,008 - INFO - Frame 1460 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:53,134 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:53,135 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:53,307 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:53,308 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:53,469 - INFO - Frame 1462 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:53,473 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:53,474 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:53,631 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:53,631 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:53,803 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:53,804 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:53,823 - INFO - Frame 1464 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:53,960 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:53,961 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:54,130 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:54,132 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:54,307 - INFO - Frame 1466 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:54,311 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:54,314 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:54,474 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:54,475 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:54,636 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:54,637 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:54,653 - INFO - Frame 1468 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:54,789 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:54,790 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:54,949 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:54,949 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:55,114 - INFO - Frame 1470 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:55,116 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:55,117 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:55,285 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:55,285 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:55,456 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:55,456 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:55,469 - INFO - Frame 1472 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:55,634 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:55,635 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:55,806 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:55,807 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:55,965 - INFO - Frame 1474 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:55,970 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:55,971 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:56,109 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:56,109 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:56,268 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:56,269 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:56,287 - INFO - Frame 1476 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:56,425 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:56,425 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:56,581 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:56,581 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:56,751 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:56,755 - INFO - Frame 1478 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:56,755 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:56,918 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:56,919 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:57,077 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:57,077 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:57,214 - INFO - Frame 1480 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:57,218 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:57,218 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:57,364 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:57,364 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:57,520 - INFO - Frame 1482 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:57,520 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:57,521 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:57,682 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:57,683 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:57,841 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:57,842 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:57,863 - INFO - Frame 1484 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:58,009 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:58,009 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:58,176 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:58,178 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:58,333 - INFO - Frame 1486 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:58,336 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:58,337 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:58,492 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:58,493 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:58,651 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:58,652 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:58,796 - INFO - Frame 1488 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:58,799 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:58,800 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:58,958 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:58,958 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:59,115 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:59,116 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:59,136 - INFO - Frame 1490 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:59,266 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:59,268 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:59,432 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:59,433 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:59,590 - INFO - Frame 1492 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:42:59,593 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:59,593 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:59,751 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:59,752 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:59,909 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:59,909 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:42:59,931 - INFO - Frame 1494 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:00,066 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:00,068 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:00,233 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:00,234 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:00,394 - INFO - Frame 1496 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:00,397 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:00,398 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:00,557 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:00,557 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:00,715 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:00,715 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:00,732 - INFO - Frame 1498 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:00,864 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:00,864 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:01,024 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:01,025 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:01,178 - INFO - Frame 1500 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:01,181 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:01,181 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:01,323 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:01,323 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:01,498 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:01,499 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:01,521 - INFO - Frame 1502 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:01,677 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:01,677 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:01,829 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:01,832 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:01,978 - INFO - Frame 1504 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:01,981 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:01,982 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:02,128 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:02,130 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:02,289 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:02,290 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:02,308 - INFO - Frame 1506 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:02,435 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:02,436 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:02,593 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:02,594 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:02,750 - INFO - Frame 1508 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:02,754 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:02,756 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:02,903 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:02,904 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:03,068 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:03,068 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:03,085 - INFO - Frame 1510 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:03,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:03,225 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:03,381 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:03,384 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:03,534 - INFO - Frame 1512 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:03,535 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:03,539 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:03,686 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:03,689 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:03,858 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:03,859 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:03,878 - INFO - Frame 1514 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:04,023 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:04,023 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:04,178 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:04,179 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:04,345 - INFO - Frame 1516 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:04,348 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:04,349 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:04,511 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:04,514 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:04,683 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:04,686 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:04,847 - INFO - Frame 1518 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:04,851 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:04,852 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:05,013 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:05,014 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:05,172 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:05,172 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:05,191 - INFO - Frame 1520 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:05,332 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:05,332 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:05,483 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:05,483 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:05,633 - INFO - Frame 1522 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:05,633 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:05,636 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:05,778 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:05,779 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:05,952 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:05,952 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:05,970 - INFO - Frame 1524 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:06,126 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:06,127 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:06,296 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:06,297 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:06,455 - INFO - Frame 1526 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:06,457 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:06,457 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:06,601 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:06,603 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:06,753 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:06,758 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:06,774 - INFO - Frame 1528 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:06,940 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:06,940 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:07,090 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:07,090 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:07,236 - INFO - Frame 1530 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:07,236 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:07,239 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:07,395 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:07,395 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:07,565 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:07,565 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:07,582 - INFO - Frame 1532 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:07,719 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:07,719 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:07,900 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:07,900 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:08,058 - INFO - Frame 1534 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:08,061 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:08,062 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:08,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:08,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:08,380 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:08,381 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:08,400 - INFO - Frame 1536 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:08,539 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:08,539 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:08,694 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:08,695 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:08,844 - INFO - Frame 1538 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:08,848 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:08,848 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:09,011 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:09,012 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:09,182 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:09,183 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:09,199 - INFO - Frame 1540 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:09,342 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:09,343 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:09,506 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:09,507 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:09,661 - INFO - Frame 1542 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:09,664 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:09,664 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:09,822 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:09,823 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:09,979 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:09,979 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:09,998 - INFO - Frame 1544 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:10,132 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:10,133 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:10,293 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:10,294 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:10,445 - INFO - Frame 1546 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:10,448 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:10,448 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:10,599 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:10,600 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:10,764 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:10,764 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:10,784 - INFO - Frame 1548 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:10,908 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:10,909 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:11,054 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:11,056 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:11,201 - INFO - Frame 1550 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:11,203 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:11,204 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:11,352 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:11,354 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:11,521 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:11,521 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:11,541 - INFO - Frame 1552 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:11,675 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:11,675 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:11,840 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:11,840 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:12,000 - INFO - Frame 1554 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:12,002 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:12,004 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:12,161 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:12,164 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:12,324 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:12,327 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:12,344 - INFO - Frame 1556 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:12,491 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:12,491 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:12,660 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:12,662 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:12,819 - INFO - Frame 1558 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:12,820 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:12,826 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:12,966 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:12,970 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:13,132 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:13,138 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:13,151 - INFO - Frame 1560 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:13,294 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:13,295 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:13,458 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:13,458 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:13,599 - INFO - Frame 1562 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:13,604 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:13,605 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:13,756 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:13,756 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:13,920 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:13,920 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:13,933 - INFO - Frame 1564 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:14,063 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:14,064 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:14,213 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:14,214 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:14,366 - INFO - Frame 1566 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:14,370 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:14,371 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:14,534 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:14,534 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:14,689 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:14,691 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:14,704 - INFO - Frame 1568 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:14,840 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:14,840 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:14,997 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:14,999 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:15,147 - INFO - Frame 1570 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:15,151 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:15,151 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:15,303 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:15,303 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:15,465 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:15,467 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:15,481 - INFO - Frame 1572 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:15,612 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:15,612 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:15,771 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:15,772 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:15,863 - INFO - Frame 1574 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:15,921 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:15,921 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:16,064 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:16,064 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:16,213 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:16,217 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:16,228 - INFO - Frame 1576 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:16,369 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:16,369 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:16,519 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:16,521 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:16,667 - INFO - Frame 1578 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:16,669 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:16,669 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:16,822 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:16,823 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:16,980 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:16,980 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:16,995 - INFO - Frame 1580 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:17,149 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:17,150 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:17,304 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:17,304 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:17,476 - INFO - Frame 1582 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:17,476 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:17,480 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:17,641 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:17,642 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:17,798 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:17,799 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:17,812 - INFO - Frame 1584 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:17,953 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:17,954 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:18,107 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:18,108 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:18,270 - INFO - Frame 1586 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:18,272 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:18,273 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:18,450 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:18,453 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:18,627 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:18,627 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:18,643 - INFO - Frame 1588 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:18,805 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:18,809 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:18,980 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:18,980 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:19,153 - INFO - Frame 1590 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:19,158 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:19,159 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:19,312 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:19,314 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:19,482 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:19,483 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:19,496 - INFO - Frame 1592 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:19,678 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:19,682 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:19,839 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:19,840 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:19,982 - INFO - Frame 1594 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:19,983 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:19,985 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:20,131 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:20,132 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:20,291 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:20,292 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:20,307 - INFO - Frame 1596 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:20,440 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:20,440 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:20,599 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:20,599 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:20,755 - INFO - Frame 1598 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:20,757 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:20,757 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:20,915 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:20,915 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:21,071 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:21,073 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:21,086 - INFO - Frame 1600 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:21,232 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:21,234 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:21,401 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:21,403 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:21,563 - INFO - Frame 1602 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:21,566 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:21,567 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:21,723 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:21,724 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:21,893 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:21,893 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:21,908 - INFO - Frame 1604 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:22,036 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:22,036 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:22,204 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:22,204 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:22,304 - INFO - Frame 1606 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:22,369 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:22,370 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:22,533 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:22,533 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:22,701 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:22,701 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:22,713 - INFO - Frame 1608 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:22,847 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:22,847 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:23,008 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:23,008 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:23,156 - INFO - Frame 1610 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:23,159 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:23,159 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:23,309 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:23,314 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:23,479 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:23,480 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:23,495 - INFO - Frame 1612 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:23,643 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:23,645 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:23,810 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:23,815 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:23,960 - INFO - Frame 1614 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:23,963 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:23,963 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:24,137 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:24,141 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:24,293 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:24,293 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:24,309 - INFO - Frame 1616 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:24,446 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:24,446 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:24,614 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:24,617 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:24,762 - INFO - Frame 1618 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:24,767 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:24,767 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:24,915 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:24,916 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:25,065 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:25,068 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:25,079 - INFO - Frame 1620 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:25,214 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:25,214 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:25,380 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:25,381 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:25,543 - INFO - Frame 1622 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:25,546 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:25,546 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:25,703 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:25,704 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:25,852 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:25,852 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:25,865 - INFO - Frame 1624 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:26,001 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:26,001 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:26,158 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:26,159 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:26,310 - INFO - Frame 1626 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:26,314 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:26,314 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:26,460 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:26,461 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:26,610 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:26,610 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:26,624 - INFO - Frame 1628 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:26,775 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:26,775 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:26,923 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:26,924 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:27,073 - INFO - Frame 1630 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:27,075 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:27,076 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:27,231 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:27,232 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:27,391 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:27,391 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:27,404 - INFO - Frame 1632 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:27,534 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:27,534 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:27,687 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:27,687 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:27,724 - INFO - Frame 1634 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:27,847 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:27,847 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:28,011 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:28,012 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:28,179 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:28,179 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:28,196 - INFO - Frame 1636 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:28,325 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:28,325 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:28,474 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:28,479 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:28,622 - INFO - Frame 1638 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:28,624 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:28,625 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:28,791 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:28,792 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:28,959 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:28,960 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:28,975 - INFO - Frame 1640 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:29,124 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:29,125 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:29,299 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:29,299 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:29,460 - INFO - Frame 1642 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:29,463 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:29,467 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:29,642 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:29,645 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:29,800 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:29,801 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:29,814 - INFO - Frame 1644 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:29,975 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:29,976 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:30,129 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:30,130 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:30,279 - INFO - Frame 1646 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:30,282 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:30,283 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:30,442 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:30,443 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:30,600 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:30,600 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:30,613 - INFO - Frame 1648 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:30,763 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:30,763 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:30,918 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:30,919 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:31,060 - INFO - Frame 1650 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:31,063 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:31,064 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:31,202 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:31,202 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:31,344 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:31,346 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:31,359 - INFO - Frame 1652 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:31,499 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:31,499 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:31,661 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:31,664 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:31,821 - INFO - Frame 1654 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:31,823 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:31,823 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:31,971 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:31,973 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:32,128 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:32,129 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:32,160 - INFO - Frame 1656 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:32,285 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:32,285 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:32,464 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:32,464 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:32,619 - INFO - Frame 1658 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:32,624 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:32,624 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:32,772 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:32,772 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:32,926 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:32,926 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:32,941 - INFO - Frame 1660 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:33,070 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:33,073 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:33,228 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:33,228 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:33,379 - INFO - Frame 1662 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:33,381 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:33,381 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:33,532 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:33,534 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:33,692 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:33,692 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:33,706 - INFO - Frame 1664 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:33,876 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:33,876 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:34,035 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:34,040 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:34,187 - INFO - Frame 1666 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:34,188 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:34,189 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:34,357 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:34,358 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:34,524 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:34,525 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:34,539 - INFO - Frame 1668 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:34,664 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:34,665 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:34,817 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:34,818 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:34,959 - INFO - Frame 1670 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:34,963 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:34,963 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:35,106 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:35,107 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:35,259 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:35,260 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:35,276 - INFO - Frame 1672 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:35,409 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:35,409 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:35,568 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:35,573 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:35,712 - INFO - Frame 1674 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:35,716 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:35,717 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:35,861 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:35,861 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:36,020 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:36,021 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:36,034 - INFO - Frame 1676 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:36,176 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:36,179 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:36,333 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:36,333 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:36,466 - INFO - Frame 1678 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:36,470 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:36,471 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:36,631 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:36,635 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:36,795 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:36,798 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:36,810 - INFO - Frame 1680 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:36,950 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:36,951 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:37,115 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:37,115 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:37,275 - INFO - Frame 1682 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:37,276 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:37,277 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:37,435 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:37,436 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:37,599 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:37,599 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:37,613 - INFO - Frame 1684 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:37,748 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:37,748 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:37,917 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:37,917 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:38,088 - INFO - Frame 1686 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:38,091 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:38,091 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:38,259 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:38,259 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:38,432 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:38,432 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:38,447 - INFO - Frame 1688 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:38,603 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:38,604 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:38,782 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:38,783 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:38,956 - INFO - Frame 1690 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:38,958 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:38,962 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:39,122 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:39,128 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:39,297 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:39,297 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:39,312 - INFO - Frame 1692 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:39,462 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:39,463 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:39,629 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:39,630 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:39,666 - INFO - Frame 1694 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:39,795 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:39,796 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:39,949 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:39,950 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:40,112 - INFO - Frame 1696 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:40,112 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:40,113 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:40,261 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:40,261 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:40,415 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:40,416 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:40,430 - INFO - Frame 1698 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:40,576 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:40,580 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:40,739 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:40,743 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:40,885 - INFO - Frame 1700 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:40,888 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:40,889 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:41,050 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:41,050 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:41,213 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:41,214 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:41,227 - INFO - Frame 1702 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:41,367 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:41,368 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:41,534 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:41,537 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:41,685 - INFO - Frame 1704 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:41,687 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:41,688 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:41,842 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:41,842 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:41,999 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:42,001 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:42,019 - INFO - Frame 1706 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:42,151 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:42,151 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:42,307 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:42,311 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:42,461 - INFO - Frame 1708 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:42,464 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:42,467 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:42,613 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:42,615 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:42,777 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:42,779 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:42,797 - INFO - Frame 1710 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:42,934 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:42,935 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:43,097 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:43,097 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:43,268 - INFO - Frame 1712 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:43,272 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:43,273 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:43,445 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:43,445 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:43,601 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:43,602 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:43,624 - INFO - Frame 1714 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:43,753 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:43,753 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:43,919 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:43,919 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:44,087 - INFO - Frame 1716 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:44,091 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:44,093 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:44,252 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:44,258 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:44,418 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:44,419 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:44,440 - INFO - Frame 1718 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:44,574 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:44,574 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:44,731 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:44,731 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:44,888 - INFO - Frame 1720 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:44,892 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:44,892 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:45,051 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:45,052 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:45,209 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:45,210 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:45,231 - INFO - Frame 1722 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:45,378 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:45,378 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:45,533 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:45,533 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:45,689 - INFO - Frame 1724 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:45,693 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:45,695 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:45,844 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:45,844 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:46,003 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:46,006 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:46,022 - INFO - Frame 1726 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:46,184 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:46,184 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:46,354 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:46,354 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:46,505 - INFO - Frame 1728 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:46,505 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:46,506 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:46,667 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:46,668 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:46,840 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:46,840 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:46,861 - INFO - Frame 1730 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:47,012 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:47,013 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:47,168 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:47,169 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:47,318 - INFO - Frame 1732 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:47,322 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:47,325 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:47,471 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:47,474 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:47,632 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:47,633 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:47,651 - INFO - Frame 1734 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:47,780 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:47,782 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:47,948 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:47,950 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:48,104 - INFO - Frame 1736 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:48,105 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:48,106 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:48,255 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:48,256 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:48,407 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:48,408 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:48,428 - INFO - Frame 1738 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:48,558 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:48,559 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:48,719 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:48,720 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:48,871 - INFO - Frame 1740 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:48,875 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:48,875 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:49,029 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:49,030 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:49,195 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:49,195 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:49,216 - INFO - Frame 1742 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:49,358 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:49,359 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:49,525 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:49,526 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:49,675 - INFO - Frame 1744 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:49,679 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:49,679 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:49,861 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:49,862 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:50,030 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:50,030 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:50,048 - INFO - Frame 1746 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:50,190 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:50,195 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:50,353 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:50,353 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:50,507 - INFO - Frame 1748 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:50,509 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:50,513 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:50,662 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:50,662 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:50,822 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:50,823 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:50,839 - INFO - Frame 1750 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:50,976 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:50,976 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:51,129 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:51,129 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:51,288 - INFO - Frame 1752 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:51,292 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:51,293 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:51,446 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:51,447 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:51,613 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:51,614 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:51,633 - INFO - Frame 1754 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:51,789 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:51,789 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:51,949 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:51,950 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:52,097 - INFO - Frame 1756 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:52,100 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:52,105 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:52,259 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:52,259 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:52,417 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:52,418 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:52,436 - INFO - Frame 1758 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:52,574 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:52,574 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:52,749 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:52,753 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:52,914 - INFO - Frame 1760 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:52,915 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:52,915 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:53,076 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:53,076 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:53,245 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:53,245 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:53,265 - INFO - Frame 1762 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:53,402 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:53,403 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:53,557 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:53,557 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:53,704 - INFO - Frame 1764 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:53,709 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:53,709 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:53,853 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:53,854 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:54,018 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:54,020 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:54,038 - INFO - Frame 1766 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:54,197 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:54,198 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:54,369 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:54,370 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:54,526 - INFO - Frame 1768 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:54,530 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:54,531 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:54,693 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:54,693 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:54,852 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:54,854 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:54,873 - INFO - Frame 1770 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:55,021 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:55,021 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:55,180 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:55,180 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:55,326 - INFO - Frame 1772 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:55,327 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:55,329 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:55,476 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:55,477 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:55,634 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:55,635 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:55,649 - INFO - Frame 1774 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:55,799 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:55,800 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:55,982 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:55,984 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:56,144 - INFO - Frame 1776 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:56,146 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:56,147 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:56,316 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:56,318 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:56,495 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:56,495 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:56,515 - INFO - Frame 1778 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:56,676 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:56,677 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:56,849 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:56,849 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:57,019 - INFO - Frame 1780 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:57,024 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:57,024 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:57,203 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:57,203 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:57,372 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:57,373 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:57,390 - INFO - Frame 1782 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:57,525 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:57,526 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:57,680 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:57,681 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:57,834 - INFO - Frame 1784 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:57,839 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:57,839 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:57,990 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:57,991 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:58,146 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:58,146 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:58,164 - INFO - Frame 1786 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:58,309 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:58,309 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:58,481 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:58,481 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:58,628 - INFO - Frame 1788 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:58,631 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:58,631 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:58,789 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:58,791 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:58,944 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:58,944 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:58,964 - INFO - Frame 1790 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:59,102 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:59,102 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:59,272 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:59,273 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:59,430 - INFO - Frame 1792 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:59,430 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:59,430 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:59,586 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:59,588 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:59,754 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:59,755 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:59,776 - INFO - Frame 1794 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:43:59,907 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:43:59,907 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:00,068 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:00,072 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:00,223 - INFO - Frame 1796 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:00,227 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:00,227 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:00,382 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:00,383 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:00,537 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:00,537 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:00,553 - INFO - Frame 1798 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:00,687 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:00,687 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:00,870 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:00,870 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:01,020 - INFO - Frame 1800 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:01,023 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:01,027 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:01,174 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:01,175 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:01,343 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:01,343 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:01,364 - INFO - Frame 1802 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:01,495 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:01,498 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:01,661 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:01,661 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:01,832 - INFO - Frame 1804 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:01,836 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:01,836 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:02,003 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:02,007 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:02,177 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:02,177 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:02,199 - INFO - Frame 1806 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:02,355 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:02,358 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:02,531 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:02,534 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:02,679 - INFO - Frame 1808 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:02,682 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:02,683 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:02,828 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:02,830 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:02,998 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:03,000 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:03,022 - INFO - Frame 1810 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:03,151 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:03,151 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:03,314 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:03,314 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:03,467 - INFO - Frame 1812 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:03,470 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:03,471 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:03,624 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:03,624 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:03,779 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:03,779 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:03,801 - INFO - Frame 1814 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:03,946 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:03,947 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:04,129 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:04,131 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:04,311 - INFO - Frame 1816 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:04,314 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:04,314 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:04,478 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:04,483 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:04,640 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:04,640 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:04,792 - INFO - Frame 1818 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:04,796 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:04,796 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:04,952 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:04,954 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:05,110 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:05,110 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:05,130 - INFO - Frame 1820 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:05,269 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:05,270 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:05,442 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:05,443 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:05,639 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:05,639 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:05,659 - INFO - Frame 1822 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:05,810 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:05,810 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:05,963 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:05,964 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:06,111 - INFO - Frame 1824 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:06,115 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:06,115 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:06,267 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:06,268 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:06,426 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:06,426 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:06,446 - INFO - Frame 1826 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:06,584 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:06,584 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:06,752 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:06,753 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:06,907 - INFO - Frame 1828 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:06,910 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:06,911 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:07,068 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:07,070 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:07,227 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:07,228 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:07,247 - INFO - Frame 1830 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:07,387 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:07,387 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:07,534 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:07,534 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:07,693 - INFO - Frame 1832 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:07,696 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:07,701 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:07,854 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:07,855 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:08,013 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:08,013 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:08,031 - INFO - Frame 1834 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:08,171 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:08,175 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:08,342 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:08,343 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:08,513 - INFO - Frame 1836 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:08,516 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:08,516 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:08,671 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:08,671 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:08,833 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:08,834 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:08,854 - INFO - Frame 1838 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:08,991 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:08,992 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:09,153 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:09,153 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:09,318 - INFO - Frame 1840 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:09,320 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:09,321 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:09,496 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:09,496 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:09,675 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:09,676 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:09,697 - INFO - Frame 1842 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:09,833 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:09,835 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:10,010 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:10,010 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:10,157 - INFO - Frame 1844 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:10,159 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:10,163 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:10,305 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:10,305 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:10,463 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:10,463 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:10,482 - INFO - Frame 1846 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:10,620 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:10,624 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:10,785 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:10,785 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:10,940 - INFO - Frame 1848 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:10,942 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:10,946 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:11,105 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:11,106 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:11,261 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:11,261 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:11,278 - INFO - Frame 1850 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:11,414 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:11,415 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:11,580 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:11,580 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:11,729 - INFO - Frame 1852 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:11,729 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:11,731 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:11,876 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:11,876 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:12,056 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:12,056 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:12,077 - INFO - Frame 1854 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:12,219 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:12,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:12,394 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:12,396 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:12,436 - INFO - Frame 1856 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:12,560 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:12,563 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:12,717 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:12,718 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:12,855 - INFO - Frame 1858 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:12,857 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:12,858 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:13,011 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:13,011 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:13,175 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:13,175 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:13,188 - INFO - Frame 1860 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:13,331 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:13,331 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:13,495 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:13,495 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:13,632 - INFO - Frame 1862 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:13,635 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:13,635 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:13,798 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:13,802 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:13,979 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:13,979 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:13,994 - INFO - Frame 1864 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:14,149 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:14,149 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:14,316 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:14,316 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:14,479 - INFO - Frame 1866 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:14,481 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:14,482 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:14,623 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:14,623 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:14,782 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:14,782 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:14,796 - INFO - Frame 1868 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:14,933 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:14,933 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:15,087 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:15,089 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:15,237 - INFO - Frame 1870 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:15,241 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:15,244 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:15,409 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:15,410 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:15,578 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:15,587 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:15,590 - INFO - Frame 1872 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:15,739 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:15,741 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:15,904 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:15,905 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:15,941 - INFO - Frame 1874 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:16,064 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:16,067 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:16,221 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:16,221 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:16,373 - INFO - Frame 1876 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:16,376 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:16,377 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:16,536 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:16,537 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:16,693 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:16,694 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:16,708 - INFO - Frame 1878 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:16,834 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:16,834 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:16,988 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:16,989 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:17,026 - INFO - Frame 1880 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:17,131 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:17,131 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:17,280 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:17,280 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:17,445 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:17,446 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:17,461 - INFO - Frame 1882 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:17,591 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:17,591 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:17,767 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:17,768 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:17,927 - INFO - Frame 1884 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:17,929 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:17,930 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:18,082 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:18,083 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:18,234 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:18,234 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:18,246 - INFO - Frame 1886 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:18,384 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:18,388 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:18,551 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:18,552 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:18,713 - INFO - Frame 1888 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:18,714 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:18,714 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:18,892 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:18,894 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:19,066 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:19,066 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:19,079 - INFO - Frame 1890 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:19,251 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:19,253 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:19,457 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:19,459 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:19,622 - INFO - Frame 1892 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:19,624 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:19,625 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:19,783 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:19,784 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:19,952 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:19,954 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:19,967 - INFO - Frame 1894 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:20,123 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:20,123 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:20,277 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:20,279 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:20,443 - INFO - Frame 1896 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:20,445 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:20,447 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:20,600 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:20,601 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:20,765 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:20,768 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:20,780 - INFO - Frame 1898 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:20,916 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:20,921 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:21,081 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:21,081 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:21,288 - INFO - Frame 1900 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:21,292 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:21,292 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:21,459 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:21,459 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:21,618 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:21,618 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:21,631 - INFO - Frame 1902 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:21,789 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:21,789 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:21,971 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:21,972 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:22,135 - INFO - Frame 1904 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:22,138 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:22,138 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:22,301 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:22,301 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:22,461 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:22,463 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:22,490 - INFO - Frame 1906 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:22,619 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:22,620 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:22,783 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:22,787 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:22,940 - INFO - Frame 1908 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:22,942 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:22,943 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:23,094 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:23,098 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:23,260 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:23,261 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:23,274 - INFO - Frame 1910 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:23,415 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:23,415 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:23,579 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:23,580 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:23,731 - INFO - Frame 1912 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:23,735 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:23,736 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:23,897 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:23,897 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:24,056 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:24,056 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:24,068 - INFO - Frame 1914 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:24,203 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:24,203 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:24,354 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:24,354 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:24,514 - INFO - Frame 1916 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:24,518 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:24,519 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:24,691 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:24,692 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:24,844 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:24,845 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:24,857 - INFO - Frame 1918 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:25,000 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:25,001 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:25,161 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:25,161 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:25,198 - INFO - Frame 1920 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:25,310 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:25,311 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:25,477 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:25,478 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:25,638 - INFO - Frame 1922 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:25,641 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:25,642 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:25,787 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:25,788 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:25,954 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:25,954 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:25,973 - INFO - Frame 1924 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:26,127 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:26,128 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:26,294 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:26,294 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:26,453 - INFO - Frame 1926 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:26,457 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:26,457 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:26,617 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:26,621 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:26,797 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:26,798 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:26,813 - INFO - Frame 1928 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:26,954 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:26,955 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:27,115 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:27,117 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:27,151 - INFO - Frame 1930 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:27,278 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:27,281 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:27,430 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:27,431 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:27,584 - INFO - Frame 1932 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:27,587 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:27,587 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:27,758 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:27,758 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:27,920 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:27,924 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:27,935 - INFO - Frame 1934 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:28,075 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:28,076 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:28,236 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:28,239 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:28,389 - INFO - Frame 1936 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:28,392 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:28,392 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:28,545 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:28,546 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:28,721 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:28,721 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:28,734 - INFO - Frame 1938 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:28,896 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:28,896 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:29,063 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:29,064 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:29,231 - INFO - Frame 1940 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:29,235 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:29,236 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:29,404 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:29,405 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:29,575 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:29,576 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:29,608 - INFO - Frame 1942 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:29,724 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:29,724 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:29,892 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:29,892 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:30,037 - INFO - Frame 1944 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:30,037 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:30,038 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:30,190 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:30,191 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:30,349 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:30,350 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:30,363 - INFO - Frame 1946 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:30,499 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:30,499 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:30,664 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:30,665 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:30,815 - INFO - Frame 1948 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:30,819 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:30,819 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:30,970 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:30,971 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:31,133 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:31,136 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:31,148 - INFO - Frame 1950 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:31,287 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:31,289 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:31,444 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:31,445 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:31,600 - INFO - Frame 1952 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:31,601 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:31,602 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:31,752 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:31,757 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:31,926 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:31,927 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:31,941 - INFO - Frame 1954 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:32,098 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:32,098 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:32,271 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:32,271 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:32,446 - INFO - Frame 1956 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:32,447 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:32,450 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:32,633 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:32,637 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:32,799 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:32,800 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:32,814 - INFO - Frame 1958 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:32,958 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:32,958 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:33,120 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:33,121 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:33,272 - INFO - Frame 1960 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:33,275 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:33,276 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:33,436 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:33,436 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:33,580 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:33,582 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:33,593 - INFO - Frame 1962 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:33,730 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:33,733 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:33,884 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:33,884 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:33,919 - INFO - Frame 1964 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:34,038 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:34,040 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:34,195 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:34,195 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:34,342 - INFO - Frame 1966 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:34,345 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:34,345 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:34,524 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:34,529 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:34,701 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:34,703 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:34,717 - INFO - Frame 1968 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:34,854 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:34,856 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:35,021 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:35,024 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:35,175 - INFO - Frame 1970 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:35,176 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:35,177 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:35,317 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:35,318 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:35,466 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:35,469 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:35,480 - INFO - Frame 1972 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:35,618 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:35,618 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:35,782 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:35,784 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:35,945 - INFO - Frame 1974 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:35,947 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:35,948 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:36,152 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:36,158 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:36,321 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:36,322 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:36,335 - INFO - Frame 1976 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:36,493 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:36,493 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:36,669 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:36,670 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:36,832 - INFO - Frame 1978 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:36,833 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:36,834 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:36,998 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:37,002 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:37,150 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:37,151 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:37,164 - INFO - Frame 1980 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:37,307 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:37,308 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:37,458 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:37,458 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:37,605 - INFO - Frame 1982 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:37,609 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:37,609 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:37,774 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:37,778 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:37,928 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:37,929 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:37,944 - INFO - Frame 1984 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:38,082 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:38,083 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:38,249 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:38,250 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:38,394 - INFO - Frame 1986 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:38,395 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:38,398 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:38,552 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:38,553 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:38,704 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:38,705 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:38,716 - INFO - Frame 1988 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:38,849 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:38,849 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:39,023 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:39,024 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:39,182 - INFO - Frame 1990 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:39,184 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:39,184 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:39,337 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:39,343 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:39,504 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:39,506 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:39,518 - INFO - Frame 1992 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:39,649 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:39,649 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:39,819 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:39,819 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:39,991 - INFO - Frame 1994 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:39,994 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:39,994 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:40,157 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:40,160 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:40,327 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:40,328 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:40,344 - INFO - Frame 1996 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:40,503 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:40,503 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:40,673 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:40,674 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:40,808 - INFO - Frame 1998 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:40,811 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:40,814 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:40,963 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:40,964 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:41,123 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:41,124 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:41,139 - INFO - Frame 2000 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:41,283 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:41,284 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:41,459 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:41,460 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:41,622 - INFO - Frame 2002 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:41,625 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:41,625 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:41,775 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:41,778 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:41,939 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:41,941 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:41,954 - INFO - Frame 2004 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:42,095 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:42,097 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:42,249 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:42,249 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:42,401 - INFO - Frame 2006 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:42,405 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:42,405 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:42,555 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:42,555 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:42,708 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:42,708 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:42,724 - INFO - Frame 2008 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:42,879 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:42,879 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:43,053 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:43,057 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:43,205 - INFO - Frame 2010 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:43,208 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:43,209 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:43,362 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:43,364 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:43,533 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:43,533 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:43,546 - INFO - Frame 2012 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:43,697 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:43,701 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:43,866 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:43,868 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:44,026 - INFO - Frame 2014 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:44,028 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:44,029 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:44,181 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:44,182 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:44,338 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:44,338 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:44,351 - INFO - Frame 2016 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:44,504 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:44,505 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:44,664 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:44,665 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:44,821 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:44,821 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:44,822 - INFO - Frame 2018 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:44,967 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:44,967 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:45,129 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:45,129 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:45,287 - INFO - Frame 2020 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:45,290 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:45,291 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:45,444 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:45,444 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:45,608 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:45,608 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:45,620 - INFO - Frame 2022 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:45,775 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:45,775 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:45,947 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:45,948 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:46,122 - INFO - Frame 2024 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:46,123 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:46,124 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:46,281 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:46,282 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:46,450 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:46,450 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:46,464 - INFO - Frame 2026 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:46,617 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:46,623 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:46,794 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:46,796 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:46,962 - INFO - Frame 2028 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:46,963 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:46,965 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:47,139 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:47,139 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:47,316 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:47,316 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:47,332 - INFO - Frame 2030 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:47,462 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:47,463 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:47,622 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:47,622 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:47,659 - INFO - Frame 2032 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:47,780 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:47,780 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:47,945 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:47,945 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:48,097 - INFO - Frame 2034 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:48,099 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:48,099 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:48,246 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:48,247 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:48,408 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:48,410 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:48,423 - INFO - Frame 2036 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:48,552 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:48,552 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:48,711 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:48,712 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:48,865 - INFO - Frame 2038 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:48,868 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:48,868 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:49,025 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:49,026 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:49,183 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:49,183 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:49,196 - INFO - Frame 2040 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:49,341 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:49,341 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:49,515 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:49,515 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:49,552 - INFO - Frame 2042 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:49,676 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:49,676 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:49,826 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:49,826 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:49,982 - INFO - Frame 2044 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:49,983 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:49,983 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:50,130 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:50,130 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:50,293 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:50,293 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:50,307 - INFO - Frame 2046 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:50,459 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:50,461 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:50,609 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:50,609 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:50,776 - INFO - Frame 2048 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:50,781 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:50,783 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:50,960 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:50,962 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:51,135 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:51,135 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:51,149 - INFO - Frame 2050 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:51,300 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:51,301 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:51,469 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:51,469 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:51,628 - INFO - Frame 2052 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:51,629 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:51,630 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:51,784 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:51,789 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:51,952 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:51,953 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:51,966 - INFO - Frame 2054 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:52,145 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:52,146 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:52,309 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:52,309 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:52,470 - INFO - Frame 2056 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:52,471 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:52,473 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:52,621 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:52,621 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:52,778 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:52,778 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:52,794 - INFO - Frame 2058 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:52,925 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:52,925 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:53,083 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:53,083 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:53,229 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:53,229 - INFO - Frame 2060 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:53,231 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:53,368 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:53,369 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:53,522 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:53,522 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:53,680 - INFO - Frame 2062 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:53,683 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:53,684 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:53,843 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:53,843 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:54,009 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:54,010 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:54,024 - INFO - Frame 2064 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:54,164 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:54,165 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:54,324 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:54,327 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:54,486 - INFO - Frame 2066 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:54,487 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:54,487 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:54,635 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:54,635 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:54,790 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:54,793 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:54,806 - INFO - Frame 2068 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:54,942 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:54,942 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:55,103 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:55,105 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:55,262 - INFO - Frame 2070 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:55,266 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:55,267 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:55,430 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:55,431 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:55,608 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:55,608 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:55,623 - INFO - Frame 2072 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:55,759 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:55,759 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:55,925 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:55,925 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:56,093 - INFO - Frame 2074 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:56,094 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:56,095 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:56,253 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:56,254 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:56,425 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:56,426 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:56,442 - INFO - Frame 2076 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:56,595 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:56,595 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:56,762 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:56,762 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:56,920 - INFO - Frame 2078 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:56,924 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:56,924 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:57,078 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:57,078 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:57,235 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:57,236 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:57,249 - INFO - Frame 2080 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:57,385 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:57,385 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:57,545 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:57,548 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:57,697 - INFO - Frame 2082 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:57,699 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:57,700 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:57,855 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:57,856 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:58,014 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:58,019 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:58,028 - INFO - Frame 2084 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:58,176 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:58,176 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:58,334 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:58,334 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:58,484 - INFO - Frame 2086 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:58,484 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:58,486 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:58,636 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:58,641 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:58,797 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:58,802 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:58,811 - INFO - Frame 2088 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:58,959 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:58,960 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:59,143 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:59,143 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:59,296 - INFO - Frame 2090 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:59,297 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:59,302 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:59,461 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:59,467 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:59,622 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:59,623 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:59,640 - INFO - Frame 2092 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:44:59,790 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:59,792 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:59,971 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:44:59,972 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:00,131 - INFO - Frame 2094 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:00,132 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:00,135 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:00,298 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:00,299 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:00,478 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:00,478 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:00,492 - INFO - Frame 2096 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:00,649 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:00,650 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:00,818 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:00,822 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:00,984 - INFO - Frame 2098 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:00,985 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:00,985 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:01,151 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:01,151 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:01,332 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:01,333 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:01,346 - INFO - Frame 2100 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:01,489 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:01,490 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:01,658 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:01,658 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:01,695 - INFO - Frame 2102 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:01,827 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:01,827 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:01,982 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:01,983 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:02,139 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:02,139 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:02,152 - INFO - Frame 2104 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:02,298 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:02,298 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:02,464 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:02,467 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:02,613 - INFO - Frame 2106 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:02,616 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:02,616 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:02,776 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:02,776 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:02,944 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:02,945 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:02,958 - INFO - Frame 2108 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:03,089 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:03,093 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:03,240 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:03,246 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:03,395 - INFO - Frame 2110 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:03,397 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:03,398 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:03,549 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:03,555 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:03,710 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:03,710 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:03,724 - INFO - Frame 2112 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:03,855 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:03,856 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:04,020 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:04,020 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:04,178 - INFO - Frame 2114 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:04,180 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:04,182 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:04,348 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:04,350 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:04,529 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:04,530 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:04,543 - INFO - Frame 2116 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:04,679 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:04,679 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:04,837 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:04,837 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:04,987 - INFO - Frame 2118 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:04,991 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:04,992 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:05,146 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:05,147 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:05,299 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:05,299 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:05,314 - INFO - Frame 2120 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:05,448 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:05,449 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:05,611 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:05,612 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:05,771 - INFO - Frame 2122 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:05,774 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:05,774 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:05,919 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:05,921 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:06,079 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:06,079 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:06,094 - INFO - Frame 2124 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:06,228 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:06,229 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:06,395 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:06,396 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:06,563 - INFO - Frame 2126 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:06,566 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:06,567 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:06,714 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:06,714 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:06,889 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:06,889 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:06,904 - INFO - Frame 2128 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:07,062 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:07,062 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:07,234 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:07,234 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:07,398 - INFO - Frame 2130 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:07,399 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:07,400 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:07,569 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:07,570 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:07,774 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:07,774 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:07,788 - INFO - Frame 2132 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:07,931 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:07,931 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:08,097 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:08,097 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:08,257 - INFO - Frame 2134 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:08,260 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:08,262 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:08,416 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:08,416 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:08,573 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:08,574 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:08,591 - INFO - Frame 2136 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:08,735 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:08,735 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:08,896 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:08,899 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:09,047 - INFO - Frame 2138 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:09,050 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:09,050 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:09,192 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:09,193 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:09,342 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:09,342 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:09,356 - INFO - Frame 2140 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:09,494 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:09,494 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:09,649 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:09,651 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:09,800 - INFO - Frame 2142 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:09,802 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:09,802 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:09,973 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:09,978 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:10,141 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:10,147 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:10,157 - INFO - Frame 2144 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:10,306 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:10,307 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:10,467 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:10,468 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:10,626 - INFO - Frame 2146 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:10,630 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:10,630 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:10,777 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:10,778 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:10,934 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:10,934 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:10,950 - INFO - Frame 2148 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:11,102 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:11,105 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:11,281 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:11,281 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:11,432 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:11,432 - INFO - Frame 2150 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:11,433 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:11,600 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:11,602 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:11,767 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:11,772 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:11,784 - INFO - Frame 2152 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:11,933 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:11,933 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:12,092 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:12,092 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:12,245 - INFO - Frame 2154 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:12,249 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:12,249 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:12,396 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:12,396 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:12,547 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:12,547 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:12,561 - INFO - Frame 2156 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:12,693 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:12,694 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:12,855 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:12,856 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:13,007 - INFO - Frame 2158 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:13,010 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:13,011 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:13,159 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:13,162 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:13,322 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:13,322 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:13,338 - INFO - Frame 2160 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:13,478 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:13,478 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:13,639 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:13,640 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:13,794 - INFO - Frame 2162 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:13,795 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:13,796 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:13,946 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:13,950 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:14,120 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:14,120 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:14,148 - INFO - Frame 2164 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:14,295 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:14,295 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:14,455 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:14,456 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:14,608 - INFO - Frame 2166 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:14,610 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:14,611 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:14,764 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:14,764 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:14,927 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:14,928 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:14,942 - INFO - Frame 2168 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:15,088 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:15,089 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:15,246 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:15,246 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:15,386 - INFO - Frame 2170 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:15,390 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:15,390 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:15,544 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:15,545 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:15,703 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:15,703 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:15,717 - INFO - Frame 2172 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:15,867 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:15,869 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:16,037 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:16,037 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:16,200 - INFO - Frame 2174 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:16,203 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:16,204 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:16,379 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:16,380 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:16,560 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:16,560 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:16,577 - INFO - Frame 2176 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:16,729 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:16,729 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:16,888 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:16,891 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:17,048 - INFO - Frame 2178 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:17,052 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:17,052 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:17,202 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:17,205 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:17,360 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:17,361 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:17,375 - INFO - Frame 2180 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:17,510 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:17,511 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:17,681 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:17,681 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:17,826 - INFO - Frame 2182 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:17,829 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:17,830 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:17,986 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:17,987 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:18,146 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:18,146 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:18,163 - INFO - Frame 2184 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:18,304 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:18,304 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:18,462 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:18,466 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:18,603 - INFO - Frame 2186 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:18,607 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:18,608 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:18,763 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:18,765 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:18,940 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:18,940 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:18,953 - INFO - Frame 2188 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:19,095 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:19,095 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:19,259 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:19,262 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:19,410 - INFO - Frame 2190 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:19,412 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:19,413 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:19,564 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:19,565 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:19,783 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:19,784 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:19,801 - INFO - Frame 2192 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:19,938 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:19,939 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:20,094 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:20,094 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:20,244 - INFO - Frame 2194 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:20,246 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:20,250 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:20,406 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:20,406 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:20,561 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:20,561 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:20,575 - INFO - Frame 2196 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:20,715 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:20,716 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:20,868 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:20,869 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:21,028 - INFO - Frame 2198 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:21,030 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:21,033 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:21,180 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:21,180 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:21,335 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:21,335 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:21,352 - INFO - Frame 2200 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:21,510 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:21,512 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:21,693 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:21,694 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:21,846 - INFO - Frame 2202 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:21,851 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:21,851 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:22,004 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:22,007 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:22,167 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:22,168 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:22,181 - INFO - Frame 2204 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:22,315 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:22,316 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:22,483 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:22,483 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:22,640 - INFO - Frame 2206 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:22,643 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:22,644 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:22,801 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:22,804 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:22,957 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:22,959 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:22,970 - INFO - Frame 2208 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:23,133 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:23,133 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:23,304 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:23,304 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:23,464 - INFO - Frame 2210 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:23,466 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:23,466 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:23,638 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:23,640 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:23,811 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:23,812 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:23,828 - INFO - Frame 2212 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:23,978 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:23,978 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:24,148 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:24,148 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:24,304 - INFO - Frame 2214 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:24,304 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:24,305 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:24,461 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:24,462 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:24,619 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:24,620 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:24,633 - INFO - Frame 2216 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:24,786 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:24,786 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:24,946 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:24,946 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:24,982 - INFO - Frame 2218 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:25,091 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:25,091 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:25,259 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:25,259 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:25,422 - INFO - Frame 2220 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:25,424 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:25,424 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:25,571 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:25,571 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:25,735 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:25,735 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:25,749 - INFO - Frame 2222 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:25,881 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:25,881 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:26,037 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:26,039 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:26,072 - INFO - Frame 2224 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:26,195 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:26,195 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:26,363 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:26,363 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:26,528 - INFO - Frame 2226 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:26,528 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:26,528 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:26,703 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:26,704 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:26,862 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:26,862 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:26,876 - INFO - Frame 2228 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:27,016 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:27,017 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:27,183 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:27,184 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:27,342 - INFO - Frame 2230 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:27,344 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:27,346 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:27,514 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:27,516 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:27,689 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:27,689 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:27,703 - INFO - Frame 2232 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:27,862 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:27,863 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:28,037 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:28,037 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:28,071 - INFO - Frame 2234 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:28,210 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:28,210 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:28,379 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:28,379 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:28,411 - INFO - Frame 2236 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:28,537 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:28,537 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:28,694 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:28,695 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:28,843 - INFO - Frame 2238 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:28,846 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:28,849 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:29,014 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:29,014 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:29,172 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:29,173 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:29,187 - INFO - Frame 2240 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:29,320 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:29,322 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:29,481 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:29,482 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:29,627 - INFO - Frame 2242 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:29,631 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:29,631 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:29,784 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:29,784 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:29,935 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:29,935 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:29,948 - INFO - Frame 2244 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:30,092 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:30,093 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:30,257 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:30,258 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:30,410 - INFO - Frame 2246 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:30,411 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:30,411 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:30,560 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:30,562 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:30,738 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:30,738 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:30,751 - INFO - Frame 2248 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:30,907 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:30,907 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:31,075 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:31,076 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:31,227 - INFO - Frame 2250 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:31,231 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:31,232 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:31,407 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:31,409 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:31,587 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:31,587 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:31,600 - INFO - Frame 2252 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:31,756 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:31,757 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:31,940 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:31,940 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:32,110 - INFO - Frame 2254 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:32,112 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:32,112 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:32,291 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:32,293 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:32,474 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:32,474 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:32,489 - INFO - Frame 2256 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:32,645 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:32,645 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:32,825 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:32,827 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:32,997 - INFO - Frame 2258 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:32,998 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:33,002 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:33,154 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:33,159 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:33,307 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:33,307 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:33,324 - INFO - Frame 2260 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:33,463 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:33,463 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:33,618 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:33,618 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:33,770 - INFO - Frame 2262 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:33,774 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:33,775 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:33,935 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:33,935 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:34,088 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:34,088 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:34,103 - INFO - Frame 2264 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:34,237 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:34,239 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:34,397 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:34,398 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:34,552 - INFO - Frame 2266 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:34,557 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:34,558 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:34,751 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:34,752 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:34,910 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:34,912 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:34,925 - INFO - Frame 2268 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:35,063 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:35,064 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:35,226 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:35,226 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:35,388 - INFO - Frame 2270 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:35,390 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:35,390 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:35,556 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:35,561 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:35,731 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:35,734 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:35,746 - INFO - Frame 2272 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:35,886 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:35,886 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:36,044 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:36,044 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:36,197 - INFO - Frame 2274 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:36,202 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:36,202 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:36,359 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:36,359 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:36,518 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:36,520 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:36,530 - INFO - Frame 2276 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:36,683 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:36,684 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:36,844 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:36,846 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:37,018 - INFO - Frame 2278 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:37,019 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:37,019 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:37,186 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:37,187 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:37,354 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:37,355 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:37,368 - INFO - Frame 2280 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:37,504 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:37,505 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:37,662 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:37,662 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:37,817 - INFO - Frame 2282 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:37,819 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:37,819 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:37,976 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:37,977 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:38,141 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:38,141 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:38,155 - INFO - Frame 2284 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:38,301 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:38,301 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:38,476 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:38,478 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:38,655 - INFO - Frame 2286 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:38,657 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:38,658 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:38,831 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:38,831 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:39,001 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:39,001 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:39,014 - INFO - Frame 2288 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:39,161 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:39,162 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:39,320 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:39,320 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:39,477 - INFO - Frame 2290 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:39,479 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:39,479 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:39,635 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:39,637 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:39,785 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:39,785 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:39,798 - INFO - Frame 2292 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:39,932 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:39,933 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:40,097 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:40,098 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:40,257 - INFO - Frame 2294 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:40,260 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:40,260 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:40,408 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:40,408 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:40,574 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:40,574 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:40,589 - INFO - Frame 2296 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:40,725 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:40,725 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:40,885 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:40,886 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:41,042 - INFO - Frame 2298 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:41,045 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:41,046 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:41,203 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:41,204 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:41,370 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:41,370 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:41,383 - INFO - Frame 2300 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:41,529 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:41,534 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:41,709 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:41,709 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:41,853 - INFO - Frame 2302 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:41,855 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:41,855 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:42,003 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:42,004 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:42,147 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:42,148 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:42,161 - INFO - Frame 2304 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:42,308 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:42,308 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:42,470 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:42,471 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:42,508 - INFO - Frame 2306 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:42,626 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:42,626 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:42,790 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:42,795 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:42,956 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:42,956 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:42,970 - INFO - Frame 2308 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:43,104 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:43,104 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:43,260 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:43,261 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:43,414 - INFO - Frame 2310 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:43,415 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:43,417 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:43,559 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:43,559 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:43,717 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:43,717 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:43,730 - INFO - Frame 2312 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:43,872 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:43,874 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:44,037 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:44,037 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:44,196 - INFO - Frame 2314 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:44,198 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:44,199 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:44,356 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:44,358 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:44,525 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:44,526 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:44,540 - INFO - Frame 2316 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:44,694 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:44,695 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:44,862 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:44,862 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:45,013 - INFO - Frame 2318 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:45,016 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:45,020 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:45,166 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:45,173 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:45,326 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:45,326 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:45,340 - INFO - Frame 2320 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:45,491 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:45,491 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:45,666 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:45,669 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:45,807 - INFO - Frame 2322 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:45,811 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:45,811 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:45,963 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:45,965 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:46,127 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:46,129 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:46,140 - INFO - Frame 2324 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:46,283 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:46,283 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:46,442 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:46,442 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:46,590 - INFO - Frame 2326 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:46,592 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:46,592 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:46,753 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:46,754 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:46,918 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:46,919 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:46,933 - INFO - Frame 2328 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:47,070 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:47,070 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:47,232 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:47,234 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:47,375 - INFO - Frame 2330 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:47,376 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:47,376 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:47,530 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:47,530 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:47,679 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:47,679 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:47,695 - INFO - Frame 2332 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:47,838 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:47,839 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:48,000 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:48,000 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:48,152 - INFO - Frame 2334 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:48,155 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:48,155 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:48,320 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:48,320 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:48,477 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:48,478 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:48,492 - INFO - Frame 2336 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:48,628 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:48,629 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:48,787 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:48,787 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:48,934 - INFO - Frame 2338 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:48,939 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:48,939 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:49,110 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:49,112 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:49,264 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:49,265 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:49,295 - INFO - Frame 2340 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:49,429 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:49,432 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:49,591 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:49,591 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:49,752 - INFO - Frame 2342 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:49,756 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:49,757 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:49,917 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:49,918 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:50,069 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:50,069 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:50,082 - INFO - Frame 2344 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:50,203 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:50,272 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:50,433 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:50,436 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:50,447 - INFO - Frame 2346 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:50,589 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:50,589 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:50,758 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:50,759 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:50,910 - INFO - Frame 2348 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:50,913 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:50,913 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:51,061 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:51,061 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:51,224 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:51,224 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:51,237 - INFO - Frame 2350 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:51,380 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:51,380 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:51,539 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:51,542 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:51,691 - INFO - Frame 2352 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:51,693 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:51,693 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:51,842 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:51,843 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:52,017 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:52,017 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:52,031 - INFO - Frame 2354 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:52,193 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:52,194 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:52,359 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:52,359 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:52,395 - INFO - Frame 2356 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:52,517 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:52,518 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:52,680 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:52,680 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:52,845 - INFO - Frame 2358 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:52,846 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:52,846 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:53,007 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:53,009 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:53,177 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:53,182 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:53,324 - INFO - Frame 2360 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:53,328 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:53,329 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:53,488 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:53,489 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:53,661 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:53,663 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:53,676 - INFO - Frame 2362 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:53,829 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:53,829 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:53,987 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:53,988 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:54,145 - INFO - Frame 2364 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:54,148 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:54,148 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:54,298 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:54,298 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:54,465 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:54,468 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:54,498 - INFO - Frame 2366 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:54,630 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:54,631 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:54,798 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:54,799 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:54,832 - INFO - Frame 2368 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:54,948 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:54,949 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:55,105 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:55,105 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:55,263 - INFO - Frame 2370 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:55,266 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:55,266 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:55,425 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:55,426 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:55,588 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:55,589 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:55,602 - INFO - Frame 2372 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:55,750 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:55,751 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:55,913 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:55,913 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:56,065 - INFO - Frame 2374 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:56,069 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:56,069 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:56,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:56,221 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:56,381 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:56,386 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:56,395 - INFO - Frame 2376 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:56,545 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:56,546 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:56,717 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:56,717 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:56,863 - INFO - Frame 2378 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:56,866 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:56,867 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:57,022 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:57,022 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:57,169 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:57,170 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:57,186 - INFO - Frame 2380 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:57,331 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:57,331 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:57,509 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:57,509 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:57,547 - INFO - Frame 2382 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:57,680 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:57,681 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:57,846 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:57,847 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:58,020 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:58,021 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:58,036 - INFO - Frame 2384 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:58,184 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:58,187 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:58,339 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:58,339 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:58,494 - INFO - Frame 2386 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:58,497 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:58,497 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:58,658 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:58,658 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:58,822 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:58,824 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:58,836 - INFO - Frame 2388 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:58,979 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:58,981 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:59,140 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:59,141 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:59,293 - INFO - Frame 2390 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:59,296 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:59,297 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:59,449 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:59,451 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:59,599 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:59,599 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:59,612 - INFO - Frame 2392 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:45:59,744 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:59,745 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:59,898 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:45:59,899 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:00,049 - INFO - Frame 2394 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:00,055 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:00,055 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:00,201 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:00,206 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:00,351 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:00,352 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:00,365 - INFO - Frame 2396 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:00,512 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:00,512 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:00,683 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:00,685 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:00,869 - INFO - Frame 2398 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:00,871 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:00,873 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:01,028 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:01,028 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:01,185 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:01,186 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:01,198 - INFO - Frame 2400 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:01,353 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:01,353 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:01,524 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:01,526 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:01,682 - INFO - Frame 2402 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:01,685 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:01,686 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:01,842 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:01,843 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:02,002 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:02,002 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:02,015 - INFO - Frame 2404 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:02,154 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:02,154 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:02,314 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:02,315 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:02,473 - INFO - Frame 2406 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:02,475 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:02,476 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:02,637 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:02,641 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:02,796 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:02,799 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:02,813 - INFO - Frame 2408 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:02,963 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:02,963 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:03,124 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:03,125 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:03,268 - INFO - Frame 2410 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:03,273 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:03,274 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:03,431 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:03,433 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:03,590 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:03,590 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:03,604 - INFO - Frame 2412 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:03,756 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:03,763 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:03,922 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:03,923 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:04,029 - INFO - Frame 2414 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:04,097 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:04,099 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:04,274 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:04,274 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:04,430 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:04,431 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:04,446 - INFO - Frame 2416 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:04,585 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:04,585 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:04,755 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:04,755 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:04,908 - INFO - Frame 2418 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:04,910 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:04,911 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:05,075 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:05,076 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:05,244 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:05,245 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:05,258 - INFO - Frame 2420 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:05,412 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:05,412 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:05,584 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:05,585 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:05,734 - INFO - Frame 2422 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:05,737 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:05,740 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:05,896 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:05,896 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:06,095 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:06,095 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:06,128 - INFO - Frame 2424 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:06,244 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:06,244 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:06,416 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:06,416 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:06,570 - INFO - Frame 2426 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:06,574 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:06,575 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:06,737 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:06,740 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:06,890 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:06,893 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:06,906 - INFO - Frame 2428 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:07,048 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:07,048 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:07,212 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:07,214 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:07,249 - INFO - Frame 2430 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:07,371 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:07,371 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:07,524 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:07,524 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:07,672 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:07,673 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:07,687 - INFO - Frame 2432 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:07,821 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:07,821 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:07,988 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:07,990 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:08,137 - INFO - Frame 2434 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:08,138 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:08,141 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:08,307 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:08,309 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:08,487 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:08,490 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:08,505 - INFO - Frame 2436 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:08,643 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:08,643 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:08,792 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:08,793 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:08,944 - INFO - Frame 2438 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:08,946 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:08,946 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:09,100 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:09,101 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:09,268 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:09,268 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:09,283 - INFO - Frame 2440 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:09,424 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:09,426 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:09,595 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:09,596 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:09,751 - INFO - Frame 2442 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:09,754 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:09,758 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:09,905 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:09,906 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:10,066 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:10,067 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:10,083 - INFO - Frame 2444 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:10,226 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:10,226 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:10,389 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:10,389 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:10,547 - INFO - Frame 2446 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:10,548 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:10,549 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:10,711 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:10,714 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:10,877 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:10,880 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:10,893 - INFO - Frame 2448 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:11,055 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:11,057 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:11,232 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:11,235 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:11,399 - INFO - Frame 2450 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:11,403 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:11,403 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:11,555 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:11,556 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:11,717 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:11,720 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:11,731 - INFO - Frame 2452 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:11,877 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:11,877 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:12,038 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:12,038 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:12,183 - INFO - Frame 2454 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:12,184 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:12,185 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:12,342 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:12,347 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:12,513 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:12,513 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:12,527 - INFO - Frame 2456 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:12,671 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:12,671 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:12,839 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:12,839 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:12,990 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:12,991 - INFO - Frame 2458 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:12,992 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:13,138 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:13,142 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:13,298 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:13,299 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:13,313 - INFO - Frame 2460 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:13,463 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:13,463 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:13,616 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:13,617 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:13,764 - INFO - Frame 2462 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:13,767 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:13,768 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:13,927 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:13,928 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:14,096 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:14,096 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:14,113 - INFO - Frame 2464 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:14,277 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:14,278 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:14,458 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:14,458 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:14,634 - INFO - Frame 2466 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:14,635 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:14,637 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:14,795 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:14,795 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:14,964 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:14,965 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:14,981 - INFO - Frame 2468 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:15,123 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:15,125 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:15,280 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:15,280 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:15,438 - INFO - Frame 2470 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:15,440 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:15,440 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:15,595 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:15,598 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:15,752 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:15,757 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:15,766 - INFO - Frame 2472 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:15,916 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:15,917 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:16,072 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:16,073 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:16,223 - INFO - Frame 2474 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:16,227 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:16,227 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:16,391 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:16,392 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:16,555 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:16,555 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:16,569 - INFO - Frame 2476 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:16,721 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:16,722 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:16,885 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:16,886 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:16,922 - INFO - Frame 2478 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:17,041 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:17,042 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:17,202 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:17,202 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:17,356 - INFO - Frame 2480 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:17,359 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:17,359 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:17,506 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:17,506 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:17,678 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:17,678 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:17,694 - INFO - Frame 2482 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:17,851 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:17,852 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:18,011 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:18,011 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:18,162 - INFO - Frame 2484 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:18,165 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:18,166 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:18,316 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:18,323 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:18,473 - INFO - Frame 2486 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:18,477 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:18,477 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:18,631 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:18,632 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:18,781 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:18,781 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:18,795 - INFO - Frame 2488 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:18,929 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:18,930 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:19,088 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:19,088 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:19,238 - INFO - Frame 2490 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:19,242 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:19,242 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:19,390 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:19,394 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:19,555 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:19,556 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:19,570 - INFO - Frame 2492 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:19,779 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:19,779 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:19,939 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:19,942 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:20,090 - INFO - Frame 2494 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:20,094 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:20,094 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:20,245 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:20,246 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:20,419 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:20,420 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:20,435 - INFO - Frame 2496 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:20,600 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:20,603 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:20,791 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:20,793 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:20,962 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:20,962 - INFO - Frame 2498 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:20,963 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:21,118 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:21,118 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:21,292 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:21,293 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:21,306 - INFO - Frame 2500 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:21,453 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:21,453 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:21,620 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:21,620 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:21,768 - INFO - Frame 2502 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:21,771 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:21,771 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:21,927 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:21,931 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:22,101 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:22,101 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:22,114 - INFO - Frame 2504 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:22,260 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:22,260 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:22,421 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:22,421 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:22,580 - INFO - Frame 2506 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:22,582 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:22,582 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:22,737 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:22,742 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:22,906 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:22,909 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:22,924 - INFO - Frame 2508 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:23,056 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:23,056 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:23,214 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:23,215 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:23,367 - INFO - Frame 2510 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:23,371 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:23,372 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:23,540 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:23,541 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:23,701 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:23,701 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:23,714 - INFO - Frame 2512 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:23,878 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:23,880 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:24,050 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:24,050 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:24,211 - INFO - Frame 2514 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:24,213 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:24,214 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:24,374 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:24,374 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:24,553 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:24,556 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:24,567 - INFO - Frame 2516 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:24,711 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:24,712 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:24,871 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:24,872 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:25,031 - INFO - Frame 2518 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:25,031 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:25,031 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:25,189 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:25,190 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:25,350 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:25,350 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:25,367 - INFO - Frame 2520 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:25,505 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:25,506 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:25,675 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:25,676 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:25,822 - INFO - Frame 2522 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:25,826 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:25,826 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:25,978 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:25,980 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:26,147 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:26,148 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:26,163 - INFO - Frame 2524 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:26,302 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:26,302 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:26,464 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:26,467 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:26,612 - INFO - Frame 2526 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:26,616 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:26,617 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:26,780 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:26,786 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:26,938 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:26,938 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:26,953 - INFO - Frame 2528 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:27,108 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:27,108 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:27,288 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:27,289 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:27,455 - INFO - Frame 2530 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:27,455 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:27,455 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:27,621 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:27,622 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:27,794 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:27,794 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:27,809 - INFO - Frame 2532 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:27,950 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:27,950 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:28,115 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:28,117 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:28,211 - INFO - Frame 2534 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:28,268 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:28,271 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:28,411 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:28,411 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:28,570 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:28,571 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:28,584 - INFO - Frame 2536 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:28,731 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:28,731 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:28,888 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:28,888 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:29,041 - INFO - Frame 2538 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:29,046 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:29,046 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:29,207 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:29,207 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:29,358 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:29,360 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:29,372 - INFO - Frame 2540 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:29,519 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:29,520 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:29,689 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:29,690 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:29,837 - INFO - Frame 2542 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:29,837 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:29,838 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:29,992 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:29,994 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:30,148 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:30,148 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:30,163 - INFO - Frame 2544 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:30,305 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:30,305 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:30,483 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:30,485 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:30,659 - INFO - Frame 2546 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:30,662 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:30,662 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:30,839 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:30,839 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:31,016 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:31,016 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:31,030 - INFO - Frame 2548 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:31,201 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:31,202 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:31,360 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:31,360 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:31,510 - INFO - Frame 2550 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:31,514 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:31,515 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:31,666 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:31,668 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:31,830 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:31,831 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:31,845 - INFO - Frame 2552 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:31,997 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:31,998 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:32,161 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:32,162 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:32,313 - INFO - Frame 2554 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:32,315 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:32,315 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:32,479 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:32,480 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:32,637 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:32,637 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:32,651 - INFO - Frame 2556 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:32,795 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:32,796 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:32,964 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:32,964 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:33,115 - INFO - Frame 2558 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:33,119 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:33,119 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:33,276 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:33,279 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:33,439 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:33,440 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:33,467 - INFO - Frame 2560 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:33,600 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:33,600 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:33,763 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:33,763 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:33,932 - INFO - Frame 2562 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:33,935 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:33,936 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:34,113 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:34,117 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:34,282 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:34,285 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:34,297 - INFO - Frame 2564 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:34,464 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:34,464 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:34,642 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:34,642 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:34,802 - INFO - Frame 2566 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:34,806 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:34,806 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:34,955 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:34,958 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:35,116 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:35,117 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:35,131 - INFO - Frame 2568 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:35,275 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:35,275 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:35,431 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:35,433 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:35,582 - INFO - Frame 2570 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:35,586 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:35,586 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:35,735 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:35,738 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:35,903 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:35,903 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:35,917 - INFO - Frame 2572 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:36,066 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:36,066 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:36,228 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:36,228 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:36,382 - INFO - Frame 2574 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:36,384 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:36,386 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:36,533 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:36,533 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:36,694 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:36,695 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:36,710 - INFO - Frame 2576 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:36,854 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:36,855 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:37,021 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:37,022 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:37,188 - INFO - Frame 2578 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:37,194 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:37,194 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:37,375 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:37,379 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:37,544 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:37,544 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:37,575 - INFO - Frame 2580 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:37,724 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:37,725 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:37,905 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:37,906 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:38,066 - INFO - Frame 2582 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:38,070 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:38,070 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:38,221 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:38,223 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:38,381 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:38,381 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:38,395 - INFO - Frame 2584 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:38,541 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:38,541 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:38,704 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:38,704 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:38,852 - INFO - Frame 2586 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:38,856 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:38,856 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:39,007 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:39,008 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:39,169 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:39,172 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:39,182 - INFO - Frame 2588 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:39,322 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:39,323 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:39,496 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:39,496 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:39,650 - INFO - Frame 2590 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:39,653 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:39,654 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:39,804 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:39,808 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:39,961 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:39,961 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:39,977 - INFO - Frame 2592 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:40,126 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:40,127 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:40,292 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:40,293 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:40,328 - INFO - Frame 2594 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:40,452 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:40,455 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:40,617 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:40,617 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:40,785 - INFO - Frame 2596 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:40,788 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:40,789 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:40,965 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:40,965 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:41,141 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:41,145 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:41,157 - INFO - Frame 2598 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:41,314 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:41,314 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:41,488 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:41,488 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:41,666 - INFO - Frame 2600 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:41,668 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:41,668 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:41,840 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:41,840 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:42,023 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:42,025 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:42,037 - INFO - Frame 2602 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:42,197 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:42,197 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:42,369 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:42,374 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:42,524 - INFO - Frame 2604 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:42,528 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:42,528 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:42,669 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:42,674 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:42,826 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:42,829 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:42,841 - INFO - Frame 2606 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:42,978 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:42,980 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:43,141 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:43,142 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:43,297 - INFO - Frame 2608 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:43,298 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:43,302 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:43,448 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:43,449 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:43,604 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:43,606 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:43,617 - INFO - Frame 2610 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:43,774 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:43,774 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:43,938 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:43,939 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:44,096 - INFO - Frame 2612 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:44,098 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:44,099 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:44,256 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:44,257 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:44,413 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:44,413 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:44,436 - INFO - Frame 2614 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:44,561 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:44,563 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:44,723 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:44,724 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:44,896 - INFO - Frame 2616 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:44,897 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:44,900 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:45,057 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:45,058 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:45,228 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:45,228 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:45,243 - INFO - Frame 2618 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:45,395 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:45,396 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:45,574 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:45,576 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:45,731 - INFO - Frame 2620 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:45,735 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:45,736 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:45,887 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:45,888 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:46,040 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:46,041 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:46,055 - INFO - Frame 2622 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:46,199 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:46,199 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:46,359 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:46,359 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:46,516 - INFO - Frame 2624 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:46,521 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:46,521 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:46,686 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:46,687 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:46,843 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:46,843 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:46,858 - INFO - Frame 2626 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:47,003 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:47,003 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:47,161 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:47,162 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:47,321 - INFO - Frame 2628 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:47,322 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:47,323 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:47,478 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:47,478 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:47,639 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:47,639 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:47,654 - INFO - Frame 2630 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:47,797 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:47,797 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:47,962 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:47,962 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:48,145 - INFO - Frame 2632 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:48,146 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:48,149 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:48,316 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:48,316 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:48,502 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:48,502 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:48,515 - INFO - Frame 2634 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:48,653 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:48,657 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:48,810 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:48,810 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:48,960 - INFO - Frame 2636 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:48,961 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:48,962 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:49,119 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:49,119 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:49,290 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:49,290 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:49,303 - INFO - Frame 2638 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:49,450 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:49,454 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:49,622 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:49,623 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:49,779 - INFO - Frame 2640 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:49,782 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:49,783 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:49,938 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:49,941 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:50,103 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:50,104 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:50,117 - INFO - Frame 2642 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:50,260 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:50,260 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:50,417 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:50,421 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:50,571 - INFO - Frame 2644 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:50,573 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:50,574 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:50,734 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:50,738 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:50,895 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:50,896 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:50,909 - INFO - Frame 2646 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:51,049 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:51,049 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:51,225 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:51,226 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:51,389 - INFO - Frame 2648 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:51,391 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:51,392 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:51,563 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:51,567 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:51,729 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:51,730 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:51,745 - INFO - Frame 2650 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:51,905 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:51,906 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:52,079 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:52,080 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:52,255 - INFO - Frame 2652 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:52,259 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:52,261 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:52,429 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:52,430 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:52,600 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:52,600 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:52,613 - INFO - Frame 2654 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:52,760 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:52,762 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:52,924 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:52,924 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:53,073 - INFO - Frame 2656 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:53,076 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:53,078 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:53,240 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:53,240 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:53,399 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:53,405 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:53,430 - INFO - Frame 2658 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:53,558 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:53,559 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:53,721 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:53,722 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:53,868 - INFO - Frame 2660 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:53,871 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:53,871 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:54,033 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:54,033 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:54,201 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:54,202 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:54,215 - INFO - Frame 2662 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:54,360 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:54,361 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:54,529 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:54,531 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:54,686 - INFO - Frame 2664 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:54,689 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:54,689 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:54,848 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:54,848 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:55,011 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:55,011 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:55,028 - INFO - Frame 2666 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:55,182 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:55,182 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:55,351 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:55,354 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:55,518 - INFO - Frame 2668 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:55,522 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:55,522 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:55,690 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:55,691 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:55,872 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:55,872 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:55,885 - INFO - Frame 2670 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:56,035 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:56,035 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:56,204 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:56,205 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:56,378 - INFO - Frame 2672 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:56,380 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:56,380 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:56,538 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:56,538 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:56,695 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:56,695 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:56,708 - INFO - Frame 2674 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:56,854 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:56,854 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:57,022 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:57,024 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:57,174 - INFO - Frame 2676 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:57,177 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:57,177 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:57,328 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:57,328 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:57,477 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:57,477 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:57,491 - INFO - Frame 2678 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:57,627 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:57,629 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:57,791 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:57,792 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:57,831 - INFO - Frame 2680 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:57,950 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:57,950 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:58,106 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:58,106 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:58,250 - INFO - Frame 2682 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:58,252 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:58,254 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:58,407 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:58,407 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:58,557 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:58,558 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:58,571 - INFO - Frame 2684 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:58,710 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:58,711 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:58,875 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:58,878 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:59,042 - INFO - Frame 2686 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:59,044 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:59,045 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:59,210 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:59,210 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:59,388 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:59,388 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:59,400 - INFO - Frame 2688 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:59,550 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:59,551 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:59,722 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:59,723 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:59,896 - INFO - Frame 2690 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:46:59,897 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:46:59,901 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:00,069 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:00,069 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:00,246 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:00,247 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:00,261 - INFO - Frame 2692 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:00,402 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:00,403 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:00,556 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:00,556 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:00,709 - INFO - Frame 2694 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:00,712 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:00,712 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:00,871 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:00,871 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:01,019 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:01,019 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:01,033 - INFO - Frame 2696 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:01,182 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:01,183 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:01,344 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:01,344 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:01,505 - INFO - Frame 2698 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:01,507 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:01,507 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:01,646 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:01,649 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:01,803 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:01,807 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:01,820 - INFO - Frame 2700 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:01,971 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:01,971 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:02,130 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:02,134 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:02,283 - INFO - Frame 2702 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:02,285 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:02,286 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:02,436 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:02,436 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:02,596 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:02,597 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:02,610 - INFO - Frame 2704 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:02,748 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:02,748 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:02,932 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:02,934 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:03,115 - INFO - Frame 2706 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:03,116 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:03,116 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:03,282 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:03,282 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:03,462 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:03,464 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:03,477 - INFO - Frame 2708 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:03,638 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:03,639 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:03,820 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:03,820 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:03,990 - INFO - Frame 2710 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:03,993 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:03,993 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:04,171 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:04,171 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:04,340 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:04,340 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:04,356 - INFO - Frame 2712 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:04,525 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:04,526 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:04,711 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:04,711 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:04,747 - INFO - Frame 2714 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:04,883 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:04,884 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:05,050 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:05,051 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:05,205 - INFO - Frame 2716 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:05,209 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:05,209 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:05,375 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:05,376 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:05,538 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:05,540 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:05,554 - INFO - Frame 2718 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:05,706 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:05,708 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:05,867 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:05,869 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:06,024 - INFO - Frame 2720 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:06,026 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:06,027 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:06,185 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:06,185 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:06,354 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:06,354 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:06,367 - INFO - Frame 2722 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:06,505 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:06,505 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:06,699 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:06,701 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:06,853 - INFO - Frame 2724 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:06,856 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:06,857 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:07,009 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:07,010 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:07,180 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:07,181 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:07,195 - INFO - Frame 2726 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:07,341 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:07,341 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:07,516 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:07,518 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:07,698 - INFO - Frame 2728 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:07,698 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:07,699 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:07,852 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:07,853 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:08,017 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:08,017 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:08,030 - INFO - Frame 2730 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:08,206 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:08,206 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:08,386 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:08,388 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:08,555 - INFO - Frame 2732 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:08,559 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:08,559 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:08,723 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:08,728 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:08,875 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:08,880 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:08,893 - INFO - Frame 2734 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:09,039 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:09,039 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:09,206 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:09,206 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:09,361 - INFO - Frame 2736 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:09,365 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:09,365 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:09,528 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:09,529 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:09,688 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:09,689 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:09,701 - INFO - Frame 2738 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:09,838 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:09,838 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:10,001 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:10,001 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:10,148 - INFO - Frame 2740 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:10,150 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:10,150 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:10,299 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:10,300 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:10,457 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:10,458 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:10,471 - INFO - Frame 2742 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:10,625 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:10,626 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:10,781 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:10,783 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:10,944 - INFO - Frame 2744 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:10,945 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:10,945 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:11,109 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:11,109 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:11,270 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:11,271 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:11,283 - INFO - Frame 2746 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:11,422 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:11,423 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:11,607 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:11,609 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:11,784 - INFO - Frame 2748 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:11,785 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:11,786 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:11,956 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:11,960 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:12,143 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:12,147 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:12,158 - INFO - Frame 2750 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:12,309 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:12,309 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:12,481 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:12,481 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:12,633 - INFO - Frame 2752 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:12,637 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:12,638 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:12,799 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:12,800 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:12,953 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:12,957 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:12,967 - INFO - Frame 2754 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:13,107 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:13,109 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:13,268 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:13,270 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:13,416 - INFO - Frame 2756 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:13,420 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:13,420 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:13,570 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:13,576 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:13,730 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:13,734 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:13,746 - INFO - Frame 2758 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:13,895 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:13,896 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:14,060 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:14,060 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:14,227 - INFO - Frame 2760 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:14,231 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:14,234 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:14,403 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:14,403 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:14,559 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:14,561 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:14,574 - INFO - Frame 2762 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:14,713 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:14,714 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:14,883 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:14,883 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:15,041 - INFO - Frame 2764 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:15,044 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:15,044 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:15,201 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:15,206 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:15,358 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:15,360 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:15,372 - INFO - Frame 2766 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:15,511 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:15,511 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:15,672 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:15,672 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:15,822 - INFO - Frame 2768 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:15,826 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:15,826 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:15,987 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:15,988 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:16,146 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:16,147 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:16,160 - INFO - Frame 2770 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:16,311 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:16,311 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:16,469 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:16,469 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:16,623 - INFO - Frame 2772 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:16,625 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:16,625 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:16,794 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:16,798 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:16,954 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:16,954 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:16,968 - INFO - Frame 2774 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:17,099 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:17,100 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:17,267 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:17,268 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:17,423 - INFO - Frame 2776 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:17,426 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:17,427 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:17,602 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:17,602 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:17,762 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:17,762 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:17,775 - INFO - Frame 2778 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:17,916 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:17,916 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:18,087 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:18,087 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:18,124 - INFO - Frame 2780 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:18,257 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:18,259 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:18,424 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:18,425 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:18,596 - INFO - Frame 2782 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:18,599 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:18,599 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:18,766 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:18,770 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:18,935 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:18,935 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:18,952 - INFO - Frame 2784 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:19,099 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:19,099 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:19,265 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:19,268 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:19,407 - INFO - Frame 2786 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:19,410 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:19,411 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:19,574 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:19,574 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:19,791 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:19,792 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:19,809 - INFO - Frame 2788 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:19,952 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:19,953 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:20,117 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:20,118 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:20,276 - INFO - Frame 2790 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:20,279 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:20,280 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:20,445 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:20,447 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:20,608 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:20,608 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:20,622 - INFO - Frame 2792 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:20,768 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:20,771 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:20,935 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:20,935 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:21,078 - INFO - Frame 2794 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:21,078 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:21,079 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:21,233 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:21,238 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:21,397 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:21,397 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:21,429 - INFO - Frame 2796 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:21,560 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:21,560 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:21,739 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:21,739 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:21,901 - INFO - Frame 2798 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:21,904 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:21,905 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:22,078 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:22,080 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:22,249 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:22,251 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:22,262 - INFO - Frame 2800 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:22,413 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:22,413 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:22,581 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:22,581 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:22,749 - INFO - Frame 2802 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:22,753 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:22,754 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:22,936 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:22,936 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:23,101 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:23,102 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:23,118 - INFO - Frame 2804 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:23,257 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:23,257 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:23,429 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:23,431 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:23,577 - INFO - Frame 2806 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:23,580 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:23,580 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:23,741 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:23,741 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:23,912 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:23,912 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:23,926 - INFO - Frame 2808 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:24,075 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:24,076 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:24,240 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:24,240 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:24,404 - INFO - Frame 2810 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:24,407 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:24,407 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:24,557 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:24,559 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:24,728 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:24,728 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:24,746 - INFO - Frame 2812 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:24,886 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:24,886 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:25,055 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:25,056 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:25,220 - INFO - Frame 2814 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:25,224 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:25,227 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:25,391 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:25,392 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:25,568 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:25,569 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:25,579 - INFO - Frame 2816 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:25,723 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:25,723 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:25,879 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:25,881 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:26,050 - INFO - Frame 2818 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:26,050 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:26,052 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:26,209 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:26,210 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:26,377 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:26,377 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:26,396 - INFO - Frame 2820 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:26,539 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:26,543 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:26,709 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:26,710 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:26,862 - INFO - Frame 2822 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:26,865 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:26,865 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:27,027 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:27,027 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:27,190 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:27,190 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:27,212 - INFO - Frame 2824 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:27,345 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:27,346 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:27,507 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:27,509 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:27,667 - INFO - Frame 2826 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:27,671 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:27,672 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:27,828 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:27,828 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:27,996 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:27,997 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:28,016 - INFO - Frame 2828 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:28,163 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:28,163 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:28,325 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:28,327 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:28,482 - INFO - Frame 2830 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:28,486 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:28,487 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:28,649 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:28,653 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:28,818 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:28,819 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:28,838 - INFO - Frame 2832 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:28,985 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:28,987 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:29,171 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:29,172 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:29,343 - INFO - Frame 2834 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:29,344 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:29,345 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:29,519 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:29,520 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:29,694 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:29,695 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:29,715 - INFO - Frame 2836 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:29,871 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:29,871 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:30,061 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:30,062 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:30,210 - INFO - Frame 2838 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:30,212 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:30,217 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:30,373 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:30,374 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:30,531 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:30,532 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:30,550 - INFO - Frame 2840 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:30,687 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:30,688 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:30,845 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:30,849 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:31,011 - INFO - Frame 2842 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:31,014 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:31,014 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:31,169 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:31,169 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:31,322 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:31,322 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:31,338 - INFO - Frame 2844 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:31,479 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:31,479 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:31,639 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:31,640 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:31,788 - INFO - Frame 2846 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:31,790 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:31,792 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:31,975 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:31,975 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:32,134 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:32,140 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:32,156 - INFO - Frame 2848 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:32,299 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:32,300 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:32,465 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:32,465 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:32,627 - INFO - Frame 2850 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:32,629 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:32,631 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:32,784 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:32,786 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:32,954 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:32,958 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:32,974 - INFO - Frame 2852 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:33,131 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:33,131 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:33,305 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:33,306 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:33,454 - INFO - Frame 2854 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:33,458 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:33,458 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:33,618 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:33,619 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:33,782 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:33,782 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:33,805 - INFO - Frame 2856 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:33,939 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:33,941 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:34,111 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:34,112 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:34,277 - INFO - Frame 2858 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:34,277 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:34,278 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:34,453 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:34,453 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:34,635 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:34,637 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:34,654 - INFO - Frame 2860 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:34,806 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:34,808 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:34,983 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:34,987 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:35,136 - INFO - Frame 2862 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:35,136 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:35,140 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:35,294 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:35,296 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:35,462 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:35,464 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:35,484 - INFO - Frame 2864 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:35,630 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:35,631 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:35,795 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:35,795 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:35,953 - INFO - Frame 2866 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:35,955 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:35,955 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:36,112 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:36,112 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:36,276 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:36,276 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:36,297 - INFO - Frame 2868 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:36,443 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:36,444 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:36,602 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:36,603 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:36,757 - INFO - Frame 2870 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:36,758 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:36,758 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:36,907 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:36,908 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:37,078 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:37,080 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:37,097 - INFO - Frame 2872 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:37,248 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:37,249 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:37,400 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:37,400 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:37,561 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:37,562 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:37,581 - INFO - Frame 2874 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:37,722 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:37,722 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:37,908 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:37,910 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:38,080 - INFO - Frame 2876 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:38,081 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:38,083 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:38,255 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:38,257 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:38,420 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:38,421 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:38,579 - INFO - Frame 2878 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:38,581 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:38,582 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:38,732 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:38,732 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:38,895 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:38,896 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:38,914 - INFO - Frame 2880 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:39,063 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:39,063 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:39,239 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:39,239 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:39,412 - INFO - Frame 2882 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:39,412 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:39,416 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:39,578 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:39,580 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:39,739 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:39,739 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:39,897 - INFO - Frame 2884 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:39,899 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:39,900 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:40,063 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:40,065 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:40,217 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:40,218 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:40,239 - INFO - Frame 2886 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:40,378 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:40,380 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:40,549 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:40,552 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:40,706 - INFO - Frame 2888 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:40,709 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:40,710 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:40,864 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:40,866 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:41,043 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:41,044 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:41,060 - INFO - Frame 2890 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:41,203 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:41,203 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:41,371 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:41,372 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:41,529 - INFO - Frame 2892 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:41,531 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:41,531 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:41,685 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:41,686 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:41,848 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:41,848 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:41,871 - INFO - Frame 2894 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:42,012 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:42,012 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:42,183 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:42,185 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:42,333 - INFO - Frame 2896 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:42,336 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:42,337 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:42,512 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:42,514 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:42,694 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:42,694 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:42,713 - INFO - Frame 2898 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:42,850 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:42,854 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:43,003 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:43,003 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:43,162 - INFO - Frame 2900 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:43,166 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:43,166 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:43,315 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:43,318 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:43,485 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:43,485 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:43,505 - INFO - Frame 2902 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:43,657 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:43,658 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:43,833 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:43,835 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:43,991 - INFO - Frame 2904 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:43,995 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:43,995 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:44,154 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:44,155 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:44,319 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:44,320 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:44,337 - INFO - Frame 2906 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:44,473 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:44,476 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:44,631 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:44,632 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:44,787 - INFO - Frame 2908 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:44,788 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:44,789 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:44,945 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:44,945 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:45,104 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:45,106 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:45,122 - INFO - Frame 2910 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:45,266 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:45,268 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:45,435 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:45,437 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:45,598 - INFO - Frame 2912 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:45,602 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:45,602 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:45,753 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:45,753 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:45,920 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:45,920 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:45,937 - INFO - Frame 2914 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:46,078 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:46,078 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:46,241 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:46,243 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:46,398 - INFO - Frame 2916 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:46,401 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:46,401 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:46,548 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:46,548 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:46,718 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:46,719 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:46,734 - INFO - Frame 2918 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:46,885 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:46,885 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:47,062 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:47,063 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:47,232 - INFO - Frame 2920 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:47,234 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:47,234 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:47,407 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:47,407 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:47,586 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:47,587 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:47,605 - INFO - Frame 2922 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:47,755 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:47,755 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:47,935 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:47,937 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:48,098 - INFO - Frame 2924 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:48,102 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:48,102 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:48,285 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:48,289 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:48,470 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:48,470 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:48,492 - INFO - Frame 2926 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:48,623 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:48,623 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:48,782 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:48,785 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:48,945 - INFO - Frame 2928 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:48,948 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:48,950 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:49,112 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:49,117 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:49,277 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:49,277 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:49,293 - INFO - Frame 2930 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:49,429 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:49,431 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:49,599 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:49,600 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:49,756 - INFO - Frame 2932 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:49,757 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:49,757 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:49,901 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:49,903 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:50,063 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:50,064 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:50,221 - INFO - Frame 2934 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:50,224 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:50,225 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:50,378 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:50,379 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:50,548 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:50,549 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:50,569 - INFO - Frame 2936 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:50,713 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:50,713 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:50,871 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:50,873 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:51,023 - INFO - Frame 2938 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:51,027 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:51,027 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:51,202 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:51,206 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:51,368 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:51,372 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:51,387 - INFO - Frame 2940 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:51,541 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:51,543 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:51,713 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:51,714 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:51,895 - INFO - Frame 2942 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:51,901 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:51,903 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:52,074 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:52,077 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:52,257 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:52,257 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:52,275 - INFO - Frame 2944 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:52,420 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:52,420 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:52,587 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:52,587 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:52,751 - INFO - Frame 2946 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:52,755 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:52,755 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:52,917 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:52,917 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:53,083 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:53,084 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:53,103 - INFO - Frame 2948 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:53,248 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:53,248 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:53,414 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:53,414 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:53,576 - INFO - Frame 2950 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:53,579 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:53,581 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:53,738 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:53,738 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:53,891 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:53,893 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:53,911 - INFO - Frame 2952 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:54,048 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:54,048 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:54,218 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:54,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:54,372 - INFO - Frame 2954 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:54,377 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:54,377 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:54,533 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:54,534 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:54,689 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:54,691 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:54,711 - INFO - Frame 2956 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:54,846 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:54,846 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:54,999 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:54,999 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:55,161 - INFO - Frame 2958 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:55,163 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:55,164 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:55,335 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:55,337 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:55,507 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:55,511 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:55,528 - INFO - Frame 2960 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:55,689 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:55,689 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:55,866 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:55,871 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:56,051 - INFO - Frame 2962 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:56,056 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:56,056 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:56,216 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:56,221 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:56,388 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:56,389 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:56,408 - INFO - Frame 2964 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:56,546 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:56,547 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:56,700 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:56,702 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:56,854 - INFO - Frame 2966 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:56,858 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:56,859 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:57,021 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:57,023 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:57,186 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:57,186 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:57,205 - INFO - Frame 2968 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:57,337 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:57,337 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:57,501 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:57,502 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:57,661 - INFO - Frame 2970 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:57,663 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:57,663 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:57,830 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:57,833 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:57,989 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:57,989 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:58,009 - INFO - Frame 2972 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:58,155 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:58,156 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:58,323 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:58,323 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:58,482 - INFO - Frame 2974 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:58,486 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:58,487 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:58,649 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:58,650 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:58,828 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:58,830 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:58,848 - INFO - Frame 2976 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:58,997 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:58,999 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:59,177 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:59,178 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:59,343 - INFO - Frame 2978 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:59,347 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:59,347 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:59,517 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:59,517 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:59,674 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:59,677 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:59,694 - INFO - Frame 2980 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:47:59,828 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:59,829 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:59,982 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:47:59,983 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:00,142 - INFO - Frame 2982 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:00,146 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:00,148 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:00,307 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:00,307 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:00,462 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:00,463 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:00,614 - INFO - Frame 2984 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:00,618 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:00,618 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:00,779 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:00,779 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:00,950 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:00,954 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:00,969 - INFO - Frame 2986 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:01,108 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:01,109 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:01,277 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:01,278 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:01,440 - INFO - Frame 2988 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:01,442 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:01,443 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:01,603 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:01,604 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:01,761 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:01,763 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:01,781 - INFO - Frame 2990 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:01,916 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:01,920 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:02,079 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:02,079 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:02,233 - INFO - Frame 2992 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:02,236 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:02,239 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:02,407 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:02,408 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:02,592 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:02,593 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:02,612 - INFO - Frame 2994 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:02,751 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:02,752 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:02,927 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:02,929 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:03,087 - INFO - Frame 2996 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:03,091 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:03,091 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:03,245 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:03,247 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:03,409 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:03,412 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:03,430 - INFO - Frame 2998 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:03,575 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:03,575 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:03,744 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:03,744 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:03,924 - INFO - Frame 3000 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:03,928 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:03,931 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:04,098 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:04,098 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:04,308 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:04,308 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:04,486 - INFO - Frame 3002 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:04,490 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:04,490 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:04,648 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:04,648 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:04,812 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:04,812 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:04,829 - INFO - Frame 3004 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:04,972 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:04,973 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:05,146 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:05,146 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:05,300 - INFO - Frame 3006 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:05,303 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:05,305 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:05,465 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:05,465 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:05,632 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:05,634 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:05,652 - INFO - Frame 3008 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:05,789 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:05,791 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:05,955 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:05,955 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:06,115 - INFO - Frame 3010 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:06,118 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:06,122 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:06,273 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:06,273 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:06,438 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:06,440 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:06,459 - INFO - Frame 3012 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:06,600 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:06,600 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:06,760 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:06,763 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:06,926 - INFO - Frame 3014 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:06,928 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:06,930 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:07,087 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:07,088 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:07,255 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:07,255 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:07,275 - INFO - Frame 3016 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:07,415 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:07,416 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:07,576 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:07,577 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:07,745 - INFO - Frame 3018 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:07,749 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:07,749 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:07,907 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:07,910 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:08,077 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:08,077 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:08,097 - INFO - Frame 3020 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:08,246 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:08,249 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:08,403 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:08,405 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:08,566 - INFO - Frame 3022 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:08,568 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:08,568 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:08,729 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:08,729 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:08,880 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:08,880 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:08,899 - INFO - Frame 3024 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:09,038 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:09,039 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:09,193 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:09,193 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:09,360 - INFO - Frame 3026 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:09,362 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:09,362 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:09,522 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:09,522 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:09,677 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:09,679 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:09,694 - INFO - Frame 3028 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:09,848 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:09,849 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:10,018 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:10,019 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:10,184 - INFO - Frame 3030 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:10,189 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:10,189 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:10,372 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:10,372 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:10,545 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:10,545 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:10,565 - INFO - Frame 3032 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:10,708 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:10,708 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:10,881 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:10,882 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:11,045 - INFO - Frame 3034 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:11,049 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:11,049 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:11,213 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:11,214 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:11,385 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:11,386 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:11,408 - INFO - Frame 3036 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:11,550 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:11,551 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:11,723 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:11,724 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:11,880 - INFO - Frame 3038 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:11,884 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:11,884 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:12,047 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:12,049 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:12,211 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:12,211 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:12,231 - INFO - Frame 3040 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:12,370 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:12,370 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:12,543 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:12,545 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:12,702 - INFO - Frame 3042 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:12,706 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:12,707 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:12,870 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:12,871 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:13,038 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:13,038 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:13,059 - INFO - Frame 3044 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:13,195 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:13,195 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:13,361 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:13,361 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:13,519 - INFO - Frame 3046 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:13,523 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:13,524 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:13,681 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:13,681 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:13,848 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:13,849 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:13,862 - INFO - Frame 3048 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:14,020 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:14,021 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:14,203 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:14,204 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:14,361 - INFO - Frame 3050 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:14,363 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:14,364 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:14,524 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:14,526 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:14,693 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:14,694 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:14,709 - INFO - Frame 3052 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:14,846 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:14,846 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:15,016 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:15,017 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:15,177 - INFO - Frame 3054 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:15,178 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:15,178 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:15,339 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:15,339 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:15,500 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:15,501 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:15,514 - INFO - Frame 3056 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:15,668 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:15,668 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:15,836 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:15,837 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:15,997 - INFO - Frame 3058 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:15,998 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:15,999 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:16,158 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:16,158 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:16,327 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:16,328 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:16,341 - INFO - Frame 3060 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:16,479 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:16,480 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:16,641 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:16,642 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:16,796 - INFO - Frame 3062 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:16,800 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:16,800 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:16,943 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:16,948 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:17,107 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:17,110 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:17,123 - INFO - Frame 3064 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:17,255 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:17,255 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:17,413 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:17,413 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:17,567 - INFO - Frame 3066 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:17,569 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:17,570 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:17,729 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:17,729 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:17,899 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:17,899 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:17,915 - INFO - Frame 3068 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:18,062 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:18,062 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:18,229 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:18,229 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:18,390 - INFO - Frame 3070 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:18,392 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:18,393 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:18,557 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:18,557 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:18,737 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:18,737 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:18,750 - INFO - Frame 3072 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:18,914 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:18,914 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:19,080 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:19,082 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:19,228 - INFO - Frame 3074 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:19,232 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:19,233 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:19,388 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:19,389 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:19,552 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:19,554 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:19,566 - INFO - Frame 3076 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:19,748 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:19,749 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:19,920 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:19,921 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:20,076 - INFO - Frame 3078 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:20,076 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:20,077 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:20,232 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:20,232 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:20,394 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:20,395 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:20,411 - INFO - Frame 3080 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:20,554 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:20,555 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:20,715 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:20,715 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:20,864 - INFO - Frame 3082 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:20,868 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:20,869 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:21,024 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:21,025 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:21,188 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:21,188 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:21,218 - INFO - Frame 3084 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:21,340 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:21,342 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:21,507 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:21,507 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:21,667 - INFO - Frame 3086 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:21,670 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:21,673 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:21,826 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:21,827 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:21,983 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:21,983 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:22,006 - INFO - Frame 3088 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:22,147 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:22,148 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:22,324 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:22,327 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:22,495 - INFO - Frame 3090 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:22,498 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:22,500 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:22,669 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:22,670 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:22,822 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:22,822 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:22,843 - INFO - Frame 3092 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:22,979 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:22,979 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:23,143 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:23,144 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:23,310 - INFO - Frame 3094 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:23,312 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:23,313 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:23,469 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:23,469 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:23,639 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:23,640 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:23,659 - INFO - Frame 3096 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:23,808 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:23,808 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:23,972 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:23,972 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:24,123 - INFO - Frame 3098 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:24,124 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:24,125 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:24,284 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:24,284 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:24,444 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:24,444 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:24,464 - INFO - Frame 3100 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:24,613 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:24,613 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:24,766 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:24,767 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:24,924 - INFO - Frame 3102 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:24,928 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:24,928 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:25,084 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:25,090 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:25,249 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:25,250 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:25,269 - INFO - Frame 3104 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:25,412 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:25,412 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:25,574 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:25,574 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:25,728 - INFO - Frame 3106 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:25,730 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:25,731 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:25,895 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:25,897 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:26,061 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:26,066 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:26,081 - INFO - Frame 3108 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:26,228 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:26,229 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:26,391 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:26,394 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:26,545 - INFO - Frame 3110 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:26,549 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:26,550 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:26,709 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:26,710 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:26,889 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:26,890 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:26,910 - INFO - Frame 3112 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:27,074 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:27,075 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:27,253 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:27,255 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:27,408 - INFO - Frame 3114 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:27,411 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:27,415 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:27,574 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:27,576 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:27,742 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:27,744 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:27,764 - INFO - Frame 3116 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:27,913 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:27,913 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:28,075 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:28,078 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:28,229 - INFO - Frame 3118 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:28,231 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:28,235 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:28,389 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:28,389 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:28,556 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:28,559 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:28,581 - INFO - Frame 3120 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:28,720 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:28,720 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:28,878 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:28,880 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:29,037 - INFO - Frame 3122 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:29,041 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:29,042 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:29,199 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:29,202 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:29,360 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:29,364 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:29,516 - INFO - Frame 3124 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:29,520 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:29,521 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:29,681 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:29,682 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:29,842 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:29,843 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:29,862 - INFO - Frame 3126 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:30,002 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:30,002 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:30,174 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:30,176 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:30,344 - INFO - Frame 3128 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:30,347 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:30,348 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:30,511 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:30,511 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:30,689 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:30,690 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:30,708 - INFO - Frame 3130 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:30,848 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:30,849 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:31,018 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:31,019 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:31,178 - INFO - Frame 3132 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:31,180 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:31,181 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:31,343 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:31,343 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:31,499 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:31,500 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:31,520 - INFO - Frame 3134 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:31,664 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:31,665 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:31,834 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:31,834 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:31,991 - INFO - Frame 3136 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:31,994 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:31,994 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:32,158 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:32,159 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:32,321 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:32,325 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:32,341 - INFO - Frame 3138 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:32,473 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:32,476 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:32,626 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:32,627 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:32,788 - INFO - Frame 3140 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:32,789 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:32,792 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:32,943 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:32,943 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:33,111 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:33,111 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:33,131 - INFO - Frame 3142 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:33,269 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:33,269 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:33,436 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:33,438 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:33,637 - INFO - Frame 3144 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:33,640 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:33,640 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:33,797 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:33,801 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:33,971 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:33,971 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:33,994 - INFO - Frame 3146 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:34,139 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:34,140 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:34,319 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:34,320 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:34,493 - INFO - Frame 3148 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:34,497 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:34,498 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:34,658 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:34,658 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:34,826 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:34,827 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:34,846 - INFO - Frame 3150 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:34,993 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:34,996 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:35,152 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:35,154 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:35,308 - INFO - Frame 3152 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:35,312 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:35,312 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:35,468 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:35,469 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:35,628 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:35,628 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:35,648 - INFO - Frame 3154 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:35,789 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:35,789 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:35,954 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:35,955 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:36,115 - INFO - Frame 3156 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:36,119 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:36,119 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:36,272 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:36,277 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:36,437 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:36,438 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:36,457 - INFO - Frame 3158 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:36,594 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:36,594 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:36,768 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:36,771 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:36,934 - INFO - Frame 3160 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:36,936 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:36,937 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:37,115 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:37,115 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:37,286 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:37,288 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:37,306 - INFO - Frame 3162 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:37,435 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:37,438 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:37,610 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:37,611 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:37,767 - INFO - Frame 3164 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:37,772 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:37,772 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:37,931 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:37,933 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:38,097 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:38,097 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:38,116 - INFO - Frame 3166 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:38,260 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:38,260 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:38,424 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:38,427 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:38,575 - INFO - Frame 3168 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:38,578 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:38,582 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:38,741 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:38,741 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:38,906 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:38,906 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:38,924 - INFO - Frame 3170 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:39,061 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:39,062 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:39,228 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:39,228 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:39,386 - INFO - Frame 3172 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:39,390 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:39,391 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:39,537 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:39,538 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:39,706 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:39,709 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:39,727 - INFO - Frame 3174 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:39,867 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:39,868 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:40,040 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:40,041 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:40,204 - INFO - Frame 3176 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:40,207 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:40,209 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:40,372 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:40,377 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:40,532 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:40,534 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:40,552 - INFO - Frame 3178 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:40,707 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:40,709 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:40,880 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:40,883 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:41,038 - INFO - Frame 3180 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:41,041 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:41,043 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:41,191 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:41,191 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:41,351 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:41,351 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:41,371 - INFO - Frame 3182 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:41,516 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:41,516 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:41,683 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:41,683 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:41,827 - INFO - Frame 3184 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:41,832 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:41,832 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:41,989 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:41,989 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:42,169 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:42,170 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:42,335 - INFO - Frame 3186 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:42,338 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:42,338 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:42,528 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:42,528 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:42,701 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:42,702 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:42,721 - INFO - Frame 3188 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:42,878 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:42,879 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:43,053 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:43,054 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:43,203 - INFO - Frame 3190 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:43,207 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:43,207 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:43,374 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:43,375 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:43,543 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:43,544 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:43,564 - INFO - Frame 3192 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:43,701 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:43,702 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:43,873 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:43,873 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:44,029 - INFO - Frame 3194 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:44,032 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:44,033 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:44,195 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:44,195 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:44,363 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:44,363 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:44,382 - INFO - Frame 3196 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:44,517 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:44,517 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:44,672 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:44,672 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:44,833 - INFO - Frame 3198 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:44,835 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:44,835 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:45,000 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:45,001 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:45,170 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:45,170 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:45,189 - INFO - Frame 3200 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:45,322 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:45,324 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:45,476 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:45,479 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:45,638 - INFO - Frame 3202 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:45,641 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:45,641 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:45,799 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:45,800 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:45,965 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:45,965 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:45,982 - INFO - Frame 3204 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:46,128 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:46,129 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:46,297 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:46,297 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:46,471 - INFO - Frame 3206 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:46,475 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:46,476 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:46,634 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:46,634 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:46,798 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:46,798 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:46,814 - INFO - Frame 3208 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:46,959 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:46,959 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:47,124 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:47,125 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:47,282 - INFO - Frame 3210 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:47,287 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:47,287 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:47,448 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:47,451 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:47,611 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:47,612 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:47,632 - INFO - Frame 3212 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:47,776 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:47,777 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:47,953 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:47,953 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:48,105 - INFO - Frame 3214 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:48,107 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:48,108 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:48,270 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:48,270 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:48,432 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:48,432 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:48,452 - INFO - Frame 3216 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:48,595 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:48,597 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:48,756 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:48,756 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:48,915 - INFO - Frame 3218 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:48,916 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:48,916 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:49,081 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:49,082 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:49,251 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:49,253 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:49,270 - INFO - Frame 3220 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:49,414 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:49,418 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:49,627 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:49,632 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:49,803 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:49,804 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:49,821 - INFO - Frame 3222 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:49,965 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:49,966 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:50,126 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:50,128 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:50,275 - INFO - Frame 3224 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:50,279 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:50,279 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:50,436 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:50,436 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:50,605 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:50,605 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:50,620 - INFO - Frame 3226 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:50,766 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:50,767 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:50,936 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:50,937 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:51,103 - INFO - Frame 3228 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:51,105 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:51,105 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:51,257 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:51,259 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:51,432 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:51,433 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:51,450 - INFO - Frame 3230 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:51,586 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:51,586 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:51,749 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:51,750 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:51,905 - INFO - Frame 3232 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:51,909 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:51,910 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:52,071 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:52,072 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:52,232 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:52,233 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:52,248 - INFO - Frame 3234 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:52,396 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:52,396 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:52,564 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:52,564 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:52,725 - INFO - Frame 3236 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:52,726 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:52,730 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:52,888 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:52,888 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:53,063 - INFO - Frame 3238 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:53,063 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:53,065 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:53,247 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:53,247 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:53,435 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:53,436 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:53,455 - INFO - Frame 3240 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:53,612 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:53,613 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:53,798 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:53,799 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:53,969 - INFO - Frame 3242 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:53,973 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:53,975 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:54,118 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:54,120 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:54,282 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:54,283 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:54,302 - INFO - Frame 3244 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:54,438 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:54,438 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:54,606 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:54,607 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:54,775 - INFO - Frame 3246 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:54,779 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:54,782 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:54,935 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:54,935 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:55,098 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:55,098 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:55,113 - INFO - Frame 3248 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:55,258 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:55,259 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:55,428 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:55,433 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:55,588 - INFO - Frame 3250 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:55,592 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:55,592 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:55,743 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:55,743 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:55,905 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:55,906 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:55,925 - INFO - Frame 3252 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:56,063 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:56,064 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:56,236 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:56,237 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:56,400 - INFO - Frame 3254 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:56,404 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:56,404 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:56,561 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:56,561 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:56,730 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:56,732 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:56,750 - INFO - Frame 3256 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:56,893 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:56,893 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:57,070 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:57,070 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:57,245 - INFO - Frame 3258 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:57,247 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:57,251 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:57,431 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:57,431 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:57,597 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:57,597 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:57,616 - INFO - Frame 3260 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:57,767 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:57,767 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:57,947 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:57,947 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:58,109 - INFO - Frame 3262 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:58,112 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:58,113 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:58,275 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:58,275 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:58,441 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:58,443 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:58,601 - INFO - Frame 3264 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:58,605 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:58,606 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:58,762 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:58,767 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:58,922 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:58,922 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:58,943 - INFO - Frame 3266 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:59,085 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:59,086 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:59,254 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:59,254 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:59,419 - INFO - Frame 3268 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:59,421 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:59,421 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:59,589 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:59,590 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:59,751 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:59,751 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:59,771 - INFO - Frame 3270 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:48:59,913 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:48:59,914 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:00,083 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:00,083 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:00,237 - INFO - Frame 3272 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:00,239 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:00,241 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:00,397 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:00,397 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:00,564 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:00,565 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:00,584 - INFO - Frame 3274 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:00,721 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:00,721 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:00,890 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:00,894 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:01,052 - INFO - Frame 3276 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:01,056 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:01,056 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:01,218 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:01,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:01,391 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:01,397 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:01,412 - INFO - Frame 3278 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:01,566 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:01,567 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:01,730 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:01,730 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:01,884 - INFO - Frame 3280 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:01,888 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:01,888 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:02,047 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:02,047 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:02,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:02,221 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:02,241 - INFO - Frame 3282 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:02,383 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:02,384 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:02,547 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:02,547 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:02,710 - INFO - Frame 3284 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:02,713 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:02,717 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:02,866 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:02,874 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:03,026 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:03,026 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:03,042 - INFO - Frame 3286 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:03,185 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:03,186 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:03,358 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:03,358 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:03,520 - INFO - Frame 3288 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:03,523 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:03,525 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:03,682 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:03,682 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:03,849 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:03,855 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:03,870 - INFO - Frame 3290 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:04,010 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:04,011 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:04,181 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:04,181 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:04,340 - INFO - Frame 3292 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:04,344 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:04,344 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:04,513 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:04,513 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:04,684 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:04,684 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:04,703 - INFO - Frame 3294 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:04,855 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:04,855 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:05,029 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:05,030 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:05,175 - INFO - Frame 3296 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:05,177 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:05,178 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:05,336 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:05,337 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:05,494 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:05,494 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:05,514 - INFO - Frame 3298 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:05,648 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:05,648 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:05,820 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:05,820 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:06,020 - INFO - Frame 3300 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:06,024 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:06,024 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:06,181 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:06,181 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:06,359 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:06,359 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:06,380 - INFO - Frame 3302 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:06,532 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:06,533 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:06,698 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:06,698 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:06,872 - INFO - Frame 3304 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:06,874 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:06,875 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:07,033 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:07,034 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:07,193 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:07,194 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:07,212 - INFO - Frame 3306 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:07,354 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:07,354 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:07,523 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:07,523 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:07,679 - INFO - Frame 3308 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:07,683 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:07,683 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:07,848 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:07,853 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:08,007 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:08,008 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:08,028 - INFO - Frame 3310 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:08,169 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:08,169 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:08,331 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:08,332 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:08,504 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:08,504 - INFO - Frame 3312 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:08,509 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:08,662 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:08,663 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:08,820 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:08,821 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:08,839 - INFO - Frame 3314 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:08,988 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:08,991 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:09,158 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:09,159 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:09,315 - INFO - Frame 3316 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:09,318 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:09,318 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:09,483 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:09,483 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:09,654 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:09,655 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:09,675 - INFO - Frame 3318 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:09,819 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:09,820 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:09,996 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:09,998 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:10,177 - INFO - Frame 3320 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:10,182 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:10,182 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:10,362 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:10,363 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:10,535 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:10,537 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:10,554 - INFO - Frame 3322 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:10,696 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:10,697 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:10,853 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:10,854 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:11,013 - INFO - Frame 3324 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:11,014 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:11,014 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:11,186 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:11,189 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:11,363 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:11,364 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:11,385 - INFO - Frame 3326 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:11,542 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:11,543 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:11,711 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:11,711 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:11,865 - INFO - Frame 3328 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:11,869 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:11,869 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:12,020 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:12,021 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:12,191 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:12,191 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:12,211 - INFO - Frame 3330 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:12,353 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:12,353 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:12,512 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:12,513 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:12,675 - INFO - Frame 3332 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:12,678 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:12,679 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:12,834 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:12,835 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:12,995 - INFO - Frame 3334 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:12,996 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:12,997 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:13,159 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:13,159 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:13,321 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:13,321 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:13,336 - INFO - Frame 3336 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:13,489 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:13,489 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:13,655 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:13,655 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:13,814 - INFO - Frame 3338 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:13,818 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:13,818 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:13,974 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:13,974 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:14,144 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:14,145 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:14,165 - INFO - Frame 3340 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:14,314 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:14,315 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:14,492 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:14,498 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:14,648 - INFO - Frame 3342 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:14,652 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:14,652 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:14,805 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:14,806 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:14,982 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:14,983 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:15,001 - INFO - Frame 3344 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:15,159 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:15,159 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:15,327 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:15,327 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:15,488 - INFO - Frame 3346 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:15,490 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:15,491 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:15,652 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:15,652 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:15,820 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:15,820 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:15,836 - INFO - Frame 3348 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:15,991 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:15,991 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:16,156 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:16,157 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:16,319 - INFO - Frame 3350 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:16,323 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:16,324 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:16,489 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:16,491 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:16,662 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:16,665 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:16,683 - INFO - Frame 3352 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:16,827 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:16,827 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:16,987 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:16,987 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:17,143 - INFO - Frame 3354 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:17,144 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:17,145 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:17,308 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:17,308 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:17,466 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:17,467 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:17,481 - INFO - Frame 3356 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:17,628 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:17,628 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:17,789 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:17,790 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:17,954 - INFO - Frame 3358 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:17,958 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:17,958 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:18,122 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:18,122 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:18,288 - INFO - Frame 3360 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:18,288 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:18,288 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:18,442 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:18,442 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:18,618 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:18,619 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:18,638 - INFO - Frame 3362 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:18,784 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:18,784 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:18,958 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:18,963 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:19,132 - INFO - Frame 3364 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:19,132 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:19,135 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:19,311 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:19,313 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:19,501 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:19,502 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:19,522 - INFO - Frame 3366 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:19,695 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:19,696 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:19,895 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:19,896 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:20,067 - INFO - Frame 3368 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:20,071 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:20,071 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:20,226 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:20,226 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:20,392 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:20,396 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:20,554 - INFO - Frame 3370 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:20,557 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:20,561 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:20,709 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:20,711 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:20,876 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:20,878 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:20,895 - INFO - Frame 3372 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:21,042 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:21,042 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:21,200 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:21,205 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:21,355 - INFO - Frame 3374 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:21,359 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:21,359 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:21,529 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:21,530 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:21,698 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:21,702 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:21,719 - INFO - Frame 3376 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:21,860 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:21,861 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:22,066 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:22,069 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:22,226 - INFO - Frame 3378 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:22,230 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:22,230 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:22,387 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:22,387 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:22,559 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:22,562 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:22,580 - INFO - Frame 3380 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:22,722 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:22,722 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:22,897 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:22,898 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:23,051 - INFO - Frame 3382 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:23,055 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:23,055 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:23,211 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:23,211 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:23,395 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:23,395 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:23,416 - INFO - Frame 3384 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:23,564 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:23,567 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:23,742 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:23,746 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:23,901 - INFO - Frame 3386 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:23,901 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:23,905 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:24,062 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:24,062 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:24,222 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:24,224 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:24,377 - INFO - Frame 3388 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:24,377 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:24,378 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:24,540 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:24,540 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:24,710 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:24,710 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:24,727 - INFO - Frame 3390 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:24,870 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:24,871 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:25,038 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:25,038 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:25,205 - INFO - Frame 3392 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:25,208 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:25,210 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:25,366 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:25,368 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:25,540 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:25,541 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:25,561 - INFO - Frame 3394 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:25,709 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:25,710 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:25,872 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:25,873 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:26,018 - INFO - Frame 3396 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:26,022 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:26,023 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:26,183 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:26,184 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:26,352 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:26,352 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:26,374 - INFO - Frame 3398 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:26,510 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:26,511 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:26,672 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:26,673 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:26,847 - INFO - Frame 3400 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:26,848 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:26,848 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:27,022 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:27,023 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:27,198 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:27,201 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:27,221 - INFO - Frame 3402 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:27,376 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:27,377 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:27,543 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:27,544 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:27,702 - INFO - Frame 3404 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:27,706 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:27,706 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:27,872 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:27,872 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:28,041 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:28,042 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:28,062 - INFO - Frame 3406 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:28,207 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:28,207 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:28,375 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:28,377 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:28,542 - INFO - Frame 3408 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:28,545 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:28,545 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:28,706 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:28,707 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:28,866 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:28,867 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:28,885 - INFO - Frame 3410 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:29,023 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:29,023 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:29,178 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:29,179 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:29,340 - INFO - Frame 3412 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:29,344 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:29,344 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:29,502 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:29,503 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:29,662 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:29,663 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:29,683 - INFO - Frame 3414 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:29,823 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:29,825 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:29,996 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:29,996 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:30,157 - INFO - Frame 3416 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:30,161 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:30,161 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:30,319 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:30,319 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:30,478 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:30,482 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:30,498 - INFO - Frame 3418 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:30,648 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:30,649 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:30,820 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:30,825 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:30,995 - INFO - Frame 3420 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:30,999 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:31,002 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:31,166 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:31,167 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:31,352 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:31,352 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:31,521 - INFO - Frame 3422 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:31,523 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:31,524 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:31,693 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:31,693 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:31,863 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:31,863 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:31,880 - INFO - Frame 3424 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:32,024 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:32,024 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:32,190 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:32,190 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:32,345 - INFO - Frame 3426 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:32,347 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:32,348 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:32,503 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:32,504 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:32,675 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:32,676 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:32,695 - INFO - Frame 3428 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:32,834 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:32,835 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:32,998 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:32,999 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:33,146 - INFO - Frame 3430 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:33,151 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:33,152 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:33,312 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:33,313 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:33,485 - INFO - Frame 3432 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:33,486 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:33,490 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:33,647 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:33,650 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:33,814 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:33,815 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:33,832 - INFO - Frame 3434 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:33,988 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:33,991 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:34,163 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:34,164 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:34,323 - INFO - Frame 3436 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:34,327 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:34,327 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:34,497 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:34,502 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:34,662 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:34,662 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:34,681 - INFO - Frame 3438 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:34,833 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:34,836 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:35,005 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:35,006 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:35,179 - INFO - Frame 3440 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:35,181 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:35,182 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:35,334 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:35,335 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:35,493 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:35,495 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:35,514 - INFO - Frame 3442 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:35,655 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:35,656 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:35,819 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:35,821 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:35,979 - INFO - Frame 3444 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:35,982 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:35,982 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:36,137 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:36,138 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:36,303 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:36,303 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:36,321 - INFO - Frame 3446 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:36,462 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:36,464 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:36,626 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:36,627 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:36,789 - INFO - Frame 3448 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:36,793 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:36,793 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:36,957 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:36,957 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:37,114 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:37,115 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:37,133 - INFO - Frame 3450 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:37,281 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:37,281 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:37,451 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:37,452 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:37,613 - INFO - Frame 3452 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:37,616 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:37,616 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:37,776 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:37,777 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:37,944 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:37,944 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:37,962 - INFO - Frame 3454 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:38,109 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:38,113 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:38,271 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:38,271 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:38,434 - INFO - Frame 3456 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:38,438 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:38,438 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:38,600 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:38,601 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:38,764 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:38,765 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:38,783 - INFO - Frame 3458 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:38,939 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:38,940 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:39,096 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:39,097 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:39,265 - INFO - Frame 3460 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:39,268 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:39,269 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:39,419 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:39,424 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:39,591 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:39,591 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:39,609 - INFO - Frame 3462 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:39,757 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:39,757 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:39,920 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:39,921 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:40,084 - INFO - Frame 3464 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:40,087 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:40,092 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:40,249 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:40,250 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:40,417 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:40,418 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:40,436 - INFO - Frame 3466 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:40,574 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:40,575 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:40,745 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:40,746 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:40,909 - INFO - Frame 3468 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:40,910 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:40,911 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:41,068 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:41,070 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:41,236 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:41,236 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:41,254 - INFO - Frame 3470 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:41,425 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:41,425 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:41,591 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:41,592 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:41,752 - INFO - Frame 3472 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:41,755 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:41,755 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:41,929 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:41,935 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:42,114 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:42,114 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:42,133 - INFO - Frame 3474 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:42,284 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:42,287 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:42,443 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:42,444 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:42,597 - INFO - Frame 3476 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:42,601 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:42,601 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:42,752 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:42,753 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:42,919 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:42,919 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:42,939 - INFO - Frame 3478 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:43,072 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:43,072 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:43,235 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:43,237 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:43,392 - INFO - Frame 3480 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:43,396 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:43,396 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:43,556 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:43,559 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:43,717 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:43,718 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:43,736 - INFO - Frame 3482 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:43,883 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:43,887 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:44,049 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:44,051 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:44,216 - INFO - Frame 3484 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:44,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:44,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:44,369 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:44,369 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:44,539 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:44,540 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:44,560 - INFO - Frame 3486 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:44,697 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:44,697 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:44,868 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:44,869 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:45,033 - INFO - Frame 3488 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:45,036 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:45,039 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:45,190 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:45,193 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:45,367 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:45,368 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:45,383 - INFO - Frame 3490 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:45,540 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:45,543 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:45,714 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:45,716 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:45,892 - INFO - Frame 3492 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:45,896 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:45,897 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:46,059 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:46,059 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:46,234 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:46,234 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:46,253 - INFO - Frame 3494 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:46,395 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:46,395 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:46,563 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:46,565 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:46,729 - INFO - Frame 3496 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:46,731 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:46,734 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:46,890 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:46,891 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:47,049 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:47,049 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:47,069 - INFO - Frame 3498 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:47,214 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:47,215 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:47,385 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:47,386 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:47,546 - INFO - Frame 3500 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:47,549 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:47,552 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:47,715 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:47,716 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:47,874 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:47,875 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:47,894 - INFO - Frame 3502 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:48,036 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:48,037 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:48,208 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:48,208 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:48,373 - INFO - Frame 3504 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:48,375 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:48,375 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:48,536 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:48,536 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:48,696 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:48,699 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:48,718 - INFO - Frame 3506 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:48,861 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:48,861 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:49,032 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:49,032 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:49,205 - INFO - Frame 3508 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:49,209 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:49,210 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:49,366 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:49,369 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:49,528 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:49,529 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:49,547 - INFO - Frame 3510 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:49,707 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:49,707 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:49,876 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:49,876 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:50,039 - INFO - Frame 3512 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:50,043 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:50,043 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:50,199 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:50,199 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:50,379 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:50,379 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:50,398 - INFO - Frame 3514 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:50,529 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:50,530 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:50,703 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:50,703 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:50,873 - INFO - Frame 3516 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:50,877 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:50,877 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:51,041 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:51,041 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:51,205 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:51,207 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:51,225 - INFO - Frame 3518 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:51,371 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:51,371 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:51,530 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:51,533 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:51,693 - INFO - Frame 3520 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:51,697 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:51,699 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:51,854 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:51,855 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:52,011 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:52,014 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:52,178 - INFO - Frame 3522 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:52,182 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:52,182 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:52,341 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:52,345 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:52,513 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:52,514 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:52,536 - INFO - Frame 3524 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:52,685 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:52,685 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:52,850 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:52,850 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:53,011 - INFO - Frame 3526 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:53,014 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:53,014 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:53,202 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:53,204 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:53,378 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:53,379 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:53,400 - INFO - Frame 3528 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:53,556 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:53,557 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:53,739 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:53,742 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:53,899 - INFO - Frame 3530 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:53,901 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:53,902 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:54,062 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:54,063 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:54,235 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:54,236 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:54,256 - INFO - Frame 3532 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:54,388 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:54,388 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:54,556 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:54,557 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:54,718 - INFO - Frame 3534 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:54,718 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:54,719 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:54,874 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:54,875 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:55,045 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:55,045 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:55,064 - INFO - Frame 3536 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:55,199 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:55,200 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:55,373 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:55,373 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:55,530 - INFO - Frame 3538 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:55,533 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:55,534 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:55,696 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:55,699 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:55,870 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:55,870 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:55,889 - INFO - Frame 3540 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:56,028 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:56,029 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:56,196 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:56,199 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:56,348 - INFO - Frame 3542 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:56,353 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:56,353 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:56,512 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:56,513 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:56,677 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:56,678 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:56,697 - INFO - Frame 3544 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:56,844 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:56,845 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:57,019 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:57,020 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:57,173 - INFO - Frame 3546 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:57,178 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:57,178 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:57,347 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:57,348 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:57,566 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:57,566 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:57,585 - INFO - Frame 3548 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:57,727 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:57,728 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:57,904 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:57,904 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:58,084 - INFO - Frame 3550 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:58,088 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:58,089 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:58,241 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:58,241 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:58,405 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:58,406 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:58,425 - INFO - Frame 3552 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:58,572 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:58,572 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:58,734 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:58,735 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:58,897 - INFO - Frame 3554 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:58,902 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:58,902 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:59,063 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:59,064 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:59,236 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:59,238 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:59,257 - INFO - Frame 3556 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:59,400 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:59,400 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:59,568 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:59,570 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:59,732 - INFO - Frame 3558 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:49:59,733 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:59,739 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:59,903 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:49:59,903 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:00,070 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:00,071 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:00,090 - INFO - Frame 3560 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:00,228 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:00,228 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:00,384 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:00,384 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:00,550 - INFO - Frame 3562 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:00,554 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:00,554 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:00,715 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:00,715 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:00,872 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:00,872 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:00,892 - INFO - Frame 3564 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:01,045 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:01,045 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:01,210 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:01,210 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:01,376 - INFO - Frame 3566 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:01,380 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:01,381 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:01,549 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:01,552 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:01,724 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:01,724 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:01,743 - INFO - Frame 3568 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:01,888 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:01,889 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:02,066 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:02,067 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:02,222 - INFO - Frame 3570 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:02,226 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:02,226 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:02,381 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:02,382 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:02,558 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:02,558 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:02,578 - INFO - Frame 3572 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:02,727 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:02,727 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:02,898 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:02,902 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:03,070 - INFO - Frame 3574 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:03,070 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:03,074 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:03,224 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:03,224 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:03,397 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:03,398 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:03,558 - INFO - Frame 3576 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:03,560 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:03,561 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:03,720 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:03,721 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:03,882 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:03,882 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:03,903 - INFO - Frame 3578 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:04,053 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:04,053 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:04,221 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:04,221 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:04,379 - INFO - Frame 3580 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:04,382 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:04,384 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:04,549 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:04,550 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:04,733 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:04,733 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:04,752 - INFO - Frame 3582 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:04,891 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:04,891 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:05,059 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:05,060 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:05,235 - INFO - Frame 3584 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:05,239 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:05,239 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:05,416 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:05,416 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:05,592 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:05,593 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:05,766 - INFO - Frame 3586 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:05,767 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:05,771 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:05,940 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:05,942 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:06,108 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:06,112 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:06,266 - INFO - Frame 3588 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:06,267 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:06,267 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:06,433 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:06,434 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:06,595 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:06,598 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:06,615 - INFO - Frame 3590 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:06,758 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:06,758 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:06,935 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:06,936 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:07,102 - INFO - Frame 3592 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:07,105 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:07,107 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:07,255 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:07,255 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:07,418 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:07,419 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:07,438 - INFO - Frame 3594 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:07,574 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:07,574 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:07,743 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:07,743 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:07,902 - INFO - Frame 3596 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:07,905 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:07,908 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:08,057 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:08,058 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:08,214 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:08,217 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:08,235 - INFO - Frame 3598 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:08,368 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:08,369 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:08,536 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:08,537 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:08,698 - INFO - Frame 3600 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:08,702 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:08,703 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:08,864 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:08,864 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:09,039 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:09,039 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:09,059 - INFO - Frame 3602 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:09,208 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:09,208 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:09,384 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:09,385 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:09,548 - INFO - Frame 3604 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:09,549 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:09,550 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:09,712 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:09,713 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:09,870 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:09,874 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:09,890 - INFO - Frame 3606 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:10,034 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:10,034 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:10,197 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:10,197 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:10,361 - INFO - Frame 3608 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:10,365 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:10,365 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:10,516 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:10,517 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:10,682 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:10,684 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:10,702 - INFO - Frame 3610 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:10,848 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:10,849 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:11,017 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:11,019 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:11,188 - INFO - Frame 3612 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:11,191 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:11,191 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:11,353 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:11,356 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:11,515 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:11,516 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:11,534 - INFO - Frame 3614 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:11,681 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:11,681 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:11,852 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:11,853 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:12,016 - INFO - Frame 3616 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:12,017 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:12,019 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:12,177 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:12,178 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:12,337 - INFO - Frame 3618 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:12,338 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:12,343 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:12,494 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:12,494 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:12,643 - INFO - Frame 3620 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:12,645 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:12,646 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:12,792 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:12,795 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:12,954 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:12,954 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:12,974 - INFO - Frame 3622 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:13,119 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:13,120 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:13,290 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:13,291 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:13,455 - INFO - Frame 3624 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:13,456 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:13,458 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:13,620 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:13,621 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:13,790 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:13,791 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:13,807 - INFO - Frame 3626 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:13,991 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:13,995 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:14,166 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:14,168 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:14,330 - INFO - Frame 3628 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:14,332 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:14,332 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:14,495 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:14,495 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:14,675 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:14,676 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:14,695 - INFO - Frame 3630 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:14,833 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:14,833 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:15,001 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:15,003 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:15,161 - INFO - Frame 3632 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:15,164 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:15,164 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:15,329 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:15,330 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:15,493 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:15,494 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:15,513 - INFO - Frame 3634 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:15,652 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:15,656 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:15,812 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:15,812 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:15,968 - INFO - Frame 3636 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:15,969 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:15,971 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:16,129 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:16,130 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:16,298 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:16,300 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:16,318 - INFO - Frame 3638 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:16,468 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:16,468 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:16,639 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:16,639 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:16,800 - INFO - Frame 3640 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:16,803 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:16,804 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:16,973 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:16,974 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:17,144 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:17,145 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:17,164 - INFO - Frame 3642 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:17,301 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:17,302 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:17,478 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:17,479 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:17,636 - INFO - Frame 3644 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:17,639 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:17,640 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:17,799 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:17,800 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:17,974 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:17,975 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:17,995 - INFO - Frame 3646 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:18,139 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:18,141 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:18,307 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:18,308 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:18,469 - INFO - Frame 3648 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:18,473 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:18,474 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:18,642 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:18,643 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:18,800 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:18,801 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:18,819 - INFO - Frame 3650 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:18,958 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:18,958 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:19,131 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:19,134 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:19,287 - INFO - Frame 3652 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:19,290 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:19,291 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:19,453 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:19,453 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:19,613 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:19,614 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:19,635 - INFO - Frame 3654 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:19,778 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:19,779 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:19,942 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:19,942 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:20,096 - INFO - Frame 3656 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:20,098 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:20,099 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:20,272 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:20,272 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:20,451 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:20,453 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:20,467 - INFO - Frame 3658 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:20,661 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:20,664 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:20,832 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:20,832 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:20,996 - INFO - Frame 3660 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:20,998 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:20,999 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:21,166 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:21,169 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:21,323 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:21,323 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:21,492 - INFO - Frame 3662 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:21,493 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:21,494 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:21,654 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:21,655 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:21,820 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:21,823 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:21,840 - INFO - Frame 3664 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:21,990 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:21,991 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:22,148 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:22,150 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:22,311 - INFO - Frame 3666 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:22,313 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:22,313 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:22,467 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:22,468 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:22,641 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:22,641 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:22,661 - INFO - Frame 3668 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:22,810 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:22,810 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:22,977 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:22,979 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:23,135 - INFO - Frame 3670 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:23,137 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:23,142 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:23,297 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:23,298 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:23,464 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:23,465 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:23,479 - INFO - Frame 3672 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:23,620 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:23,621 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:23,781 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:23,783 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:23,957 - INFO - Frame 3674 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:23,960 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:23,960 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:24,129 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:24,134 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:24,312 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:24,315 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:24,335 - INFO - Frame 3676 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:24,480 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:24,480 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:24,644 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:24,646 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:24,801 - INFO - Frame 3678 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:24,805 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:24,805 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:24,971 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:24,971 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:25,137 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:25,138 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:25,159 - INFO - Frame 3680 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:25,298 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:25,300 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:25,462 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:25,467 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:25,621 - INFO - Frame 3682 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:25,622 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:25,623 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:25,778 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:25,783 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:25,953 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:25,956 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:25,971 - INFO - Frame 3684 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:26,115 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:26,120 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:26,283 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:26,285 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:26,445 - INFO - Frame 3686 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:26,449 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:26,449 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:26,613 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:26,614 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:26,782 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:26,786 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:26,802 - INFO - Frame 3688 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:26,945 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:26,945 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:27,112 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:27,114 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:27,272 - INFO - Frame 3690 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:27,276 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:27,277 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:27,440 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:27,440 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:27,607 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:27,609 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:27,627 - INFO - Frame 3692 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:27,768 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:27,768 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:27,948 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:27,949 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:28,121 - INFO - Frame 3694 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:28,123 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:28,124 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:28,290 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:28,291 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:28,454 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:28,454 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:28,474 - INFO - Frame 3696 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:28,622 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:28,623 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:28,794 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:28,795 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:28,952 - INFO - Frame 3698 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:28,956 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:28,956 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:29,113 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:29,114 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:29,283 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:29,284 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:29,304 - INFO - Frame 3700 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:29,453 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:29,453 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:29,615 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:29,616 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:29,784 - INFO - Frame 3702 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:29,788 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:29,788 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:29,948 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:29,948 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:30,119 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:30,119 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:30,139 - INFO - Frame 3704 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:30,275 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:30,276 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:30,441 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:30,446 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:30,595 - INFO - Frame 3706 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:30,598 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:30,599 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:30,759 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:30,760 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:30,923 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:30,923 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:30,943 - INFO - Frame 3708 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:31,092 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:31,092 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:31,264 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:31,265 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:31,428 - INFO - Frame 3710 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:31,431 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:31,433 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:31,596 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:31,598 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:31,765 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:31,769 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:31,785 - INFO - Frame 3712 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:31,928 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:31,929 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:32,104 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:32,104 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:32,274 - INFO - Frame 3714 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:32,278 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:32,278 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:32,470 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:32,476 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:32,632 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:32,635 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:32,651 - INFO - Frame 3716 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:32,796 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:32,796 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:32,964 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:32,966 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:33,132 - INFO - Frame 3718 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:33,133 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:33,135 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:33,298 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:33,298 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:33,475 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:33,476 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:33,496 - INFO - Frame 3720 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:33,648 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:33,649 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:33,817 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:33,819 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:34,010 - INFO - Frame 3722 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:34,014 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:34,015 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:34,167 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:34,168 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:34,328 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:34,330 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:34,347 - INFO - Frame 3724 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:34,491 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:34,491 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:34,662 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:34,664 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:34,823 - INFO - Frame 3726 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:34,827 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:34,827 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:34,986 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:34,987 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:35,158 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:35,159 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:35,176 - INFO - Frame 3728 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:35,329 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:35,329 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:35,493 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:35,495 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:35,658 - INFO - Frame 3730 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:35,661 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:35,661 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:35,824 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:35,825 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:35,983 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:35,985 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:35,999 - INFO - Frame 3732 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:36,149 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:36,149 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:36,322 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:36,323 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:36,483 - INFO - Frame 3734 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:36,487 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:36,488 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:36,682 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:36,695 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:36,874 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:36,875 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:36,896 - INFO - Frame 3736 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:37,039 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:37,039 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:37,219 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:37,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:37,392 - INFO - Frame 3738 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:37,394 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:37,398 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:37,577 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:37,578 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:37,756 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:37,757 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:37,777 - INFO - Frame 3740 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:37,940 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:37,940 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:38,111 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:38,113 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:38,276 - INFO - Frame 3742 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:38,279 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:38,280 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:38,432 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:38,433 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:38,596 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:38,596 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:38,615 - INFO - Frame 3744 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:38,746 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:38,747 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:38,920 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:38,921 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:39,076 - INFO - Frame 3746 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:39,079 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:39,080 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:39,247 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:39,247 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:39,422 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:39,425 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:39,440 - INFO - Frame 3748 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:39,583 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:39,587 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:39,762 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:39,762 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:39,927 - INFO - Frame 3750 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:39,930 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:39,931 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:40,088 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:40,089 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:40,246 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:40,247 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:40,262 - INFO - Frame 3752 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:40,400 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:40,400 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:40,575 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:40,575 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:40,744 - INFO - Frame 3754 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:40,748 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:40,748 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:40,914 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:40,916 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:41,080 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:41,084 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:41,102 - INFO - Frame 3756 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:41,250 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:41,251 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:41,425 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:41,427 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:41,595 - INFO - Frame 3758 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:41,598 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:41,600 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:41,771 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:41,772 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:41,954 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:41,955 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:41,973 - INFO - Frame 3760 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:42,133 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:42,133 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:42,308 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:42,311 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:42,479 - INFO - Frame 3762 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:42,484 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:42,487 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:42,657 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:42,658 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:42,828 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:42,829 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:42,848 - INFO - Frame 3764 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:42,999 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:42,999 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:43,163 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:43,163 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:43,325 - INFO - Frame 3766 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:43,327 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:43,327 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:43,483 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:43,483 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:43,645 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:43,645 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:43,665 - INFO - Frame 3768 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:43,810 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:43,814 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:43,988 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:43,989 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:44,136 - INFO - Frame 3770 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:44,139 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:44,140 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:44,298 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:44,299 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:44,456 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:44,457 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:44,476 - INFO - Frame 3772 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:44,611 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:44,611 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:44,776 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:44,777 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:44,934 - INFO - Frame 3774 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:44,938 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:44,939 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:45,092 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:45,097 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:45,260 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:45,260 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:45,279 - INFO - Frame 3776 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:45,419 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:45,419 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:45,575 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:45,575 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:45,736 - INFO - Frame 3778 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:45,739 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:45,740 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:45,904 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:45,906 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:46,073 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:46,077 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:46,093 - INFO - Frame 3780 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:46,240 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:46,241 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:46,411 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:46,412 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:46,585 - INFO - Frame 3782 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:46,588 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:46,589 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:46,757 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:46,757 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:46,942 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:46,942 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:46,963 - INFO - Frame 3784 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:47,114 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:47,114 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:47,286 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:47,287 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:47,449 - INFO - Frame 3786 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:47,452 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:47,452 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:47,608 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:47,609 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:47,778 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:47,779 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:47,797 - INFO - Frame 3788 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:47,942 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:47,943 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:48,101 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:48,102 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:48,259 - INFO - Frame 3790 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:48,264 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:48,264 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:48,425 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:48,426 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:48,597 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:48,598 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:48,620 - INFO - Frame 3792 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:48,759 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:48,761 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:48,920 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:48,922 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:49,083 - INFO - Frame 3794 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:49,085 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:49,086 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:49,244 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:49,246 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:49,421 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:49,421 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:49,442 - INFO - Frame 3796 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:49,586 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:49,587 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:49,757 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:49,758 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:49,916 - INFO - Frame 3798 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:49,919 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:49,919 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:50,080 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:50,081 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:50,254 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:50,254 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:50,273 - INFO - Frame 3800 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:50,419 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:50,422 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:50,597 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:50,597 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:50,748 - INFO - Frame 3802 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:50,752 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:50,752 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:50,928 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:50,929 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:51,112 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:51,112 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:51,133 - INFO - Frame 3804 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:51,293 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:51,293 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:51,462 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:51,463 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:51,629 - INFO - Frame 3806 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:51,632 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:51,634 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:51,791 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:51,797 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:51,956 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:51,957 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:51,974 - INFO - Frame 3808 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:52,116 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:52,117 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:52,290 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:52,291 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:52,445 - INFO - Frame 3810 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:52,447 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:52,447 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:52,604 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:52,605 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:52,778 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:52,778 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:52,798 - INFO - Frame 3812 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:52,948 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:52,949 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:53,154 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:53,156 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:53,310 - INFO - Frame 3814 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:53,313 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:53,313 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:53,477 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:53,477 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:53,643 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:53,643 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:53,662 - INFO - Frame 3816 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:53,811 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:53,812 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:53,970 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:53,971 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:54,127 - INFO - Frame 3818 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:54,127 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:54,127 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:54,284 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:54,285 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:54,455 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:54,456 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:54,475 - INFO - Frame 3820 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:54,619 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:54,620 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:54,796 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:54,796 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:54,979 - INFO - Frame 3822 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:54,982 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:54,983 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:55,160 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:55,160 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:55,333 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:55,335 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:55,351 - INFO - Frame 3824 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:55,494 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:55,494 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:55,659 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:55,663 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:55,816 - INFO - Frame 3826 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:55,819 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:55,820 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:55,989 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:55,989 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:56,149 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:56,150 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:56,169 - INFO - Frame 3828 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:56,320 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:56,321 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:56,488 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:56,489 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:56,659 - INFO - Frame 3830 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:56,662 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:56,666 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:56,814 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:56,817 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:56,975 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:56,975 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:56,997 - INFO - Frame 3832 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:57,143 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:57,143 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:57,305 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:57,306 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:57,477 - INFO - Frame 3834 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:57,481 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:57,482 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:57,646 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:57,648 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:57,802 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:57,802 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:57,821 - INFO - Frame 3836 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:57,959 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:57,959 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:58,125 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:58,126 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:58,281 - INFO - Frame 3838 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:58,285 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:58,287 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:58,442 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:58,443 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:58,612 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:58,613 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:58,633 - INFO - Frame 3840 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:58,786 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:58,786 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:58,958 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:58,958 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:59,132 - INFO - Frame 3842 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:59,136 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:59,136 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:59,298 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:59,298 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:59,463 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:59,463 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:59,483 - INFO - Frame 3844 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:59,621 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:59,622 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:59,792 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:59,794 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:59,953 - INFO - Frame 3846 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:50:59,957 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:50:59,957 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:00,117 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:00,123 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:00,284 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:00,287 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:00,303 - INFO - Frame 3848 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:00,442 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:00,443 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:00,614 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:00,614 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:00,779 - INFO - Frame 3850 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:00,783 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:00,783 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:00,945 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:00,946 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:01,113 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:01,114 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:01,132 - INFO - Frame 3852 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:01,262 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:01,263 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:01,424 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:01,425 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:01,582 - INFO - Frame 3854 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:01,585 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:01,585 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:01,745 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:01,746 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:01,917 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:01,917 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:01,932 - INFO - Frame 3856 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:02,084 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:02,084 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:02,245 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:02,245 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:02,418 - INFO - Frame 3858 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:02,419 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:02,419 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:02,590 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:02,590 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:02,763 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:02,765 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:02,937 - INFO - Frame 3860 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:02,941 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:02,941 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:03,100 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:03,107 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:03,265 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:03,266 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:03,285 - INFO - Frame 3862 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:03,438 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:03,439 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:03,606 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:03,606 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:03,766 - INFO - Frame 3864 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:03,772 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:03,773 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:03,941 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:03,941 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:04,098 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:04,098 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:04,116 - INFO - Frame 3866 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:04,264 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:04,264 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:04,439 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:04,440 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:04,597 - INFO - Frame 3868 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:04,601 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:04,601 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:04,754 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:04,755 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:04,915 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:04,915 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:04,936 - INFO - Frame 3870 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:05,080 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:05,080 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:05,250 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:05,250 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:05,410 - INFO - Frame 3872 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:05,413 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:05,414 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:05,584 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:05,585 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:05,749 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:05,750 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:05,769 - INFO - Frame 3874 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:05,917 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:05,917 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:06,097 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:06,098 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:06,287 - INFO - Frame 3876 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:06,288 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:06,291 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:06,458 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:06,459 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:06,637 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:06,638 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:06,809 - INFO - Frame 3878 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:06,811 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:06,811 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:06,983 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:06,983 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:07,154 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:07,154 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:07,177 - INFO - Frame 3880 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:07,322 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:07,322 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:07,493 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:07,493 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:07,648 - INFO - Frame 3882 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:07,652 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:07,652 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:07,816 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:07,816 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:07,982 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:07,983 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:08,000 - INFO - Frame 3884 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:08,135 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:08,137 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:08,303 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:08,305 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:08,467 - INFO - Frame 3886 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:08,468 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:08,469 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:08,620 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:08,621 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:08,781 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:08,781 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:08,803 - INFO - Frame 3888 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:08,943 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:08,945 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:09,114 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:09,116 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:09,281 - INFO - Frame 3890 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:09,283 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:09,285 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:09,486 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:09,487 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:09,653 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:09,654 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:09,674 - INFO - Frame 3892 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:09,815 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:09,816 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:09,988 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:09,991 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:10,156 - INFO - Frame 3894 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:10,160 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:10,160 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:10,320 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:10,321 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:10,494 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:10,494 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:10,514 - INFO - Frame 3896 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:10,659 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:10,660 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:10,843 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:10,843 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:11,015 - INFO - Frame 3898 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:11,016 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:11,016 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:11,187 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:11,190 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:11,364 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:11,364 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:11,385 - INFO - Frame 3900 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:11,534 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:11,534 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:11,707 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:11,707 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:11,865 - INFO - Frame 3902 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:11,869 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:11,870 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:12,032 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:12,033 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:12,193 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:12,198 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:12,215 - INFO - Frame 3904 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:12,353 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:12,353 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:12,517 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:12,520 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:12,673 - INFO - Frame 3906 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:12,675 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:12,679 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:12,839 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:12,839 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:13,012 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:13,015 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:13,036 - INFO - Frame 3908 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:13,174 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:13,175 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:13,352 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:13,356 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:13,513 - INFO - Frame 3910 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:13,516 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:13,517 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:13,678 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:13,683 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:13,842 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:13,843 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:13,859 - INFO - Frame 3912 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:14,007 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:14,007 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:14,174 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:14,177 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:14,343 - INFO - Frame 3914 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:14,347 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:14,348 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:14,508 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:14,512 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:14,686 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:14,687 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:14,701 - INFO - Frame 3916 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:14,864 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:14,865 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:15,034 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:15,034 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:15,206 - INFO - Frame 3918 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:15,210 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:15,211 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:15,385 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:15,386 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:15,548 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:15,548 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:15,566 - INFO - Frame 3920 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:15,702 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:15,702 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:15,857 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:15,858 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:16,018 - INFO - Frame 3922 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:16,019 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:16,020 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:16,179 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:16,179 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:16,345 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:16,346 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:16,364 - INFO - Frame 3924 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:16,509 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:16,509 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:16,671 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:16,674 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:16,834 - INFO - Frame 3926 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:16,837 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:16,837 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:16,984 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:16,989 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:17,151 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:17,155 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:17,171 - INFO - Frame 3928 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:17,321 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:17,321 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:17,491 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:17,492 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:17,645 - INFO - Frame 3930 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:17,648 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:17,652 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:17,812 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:17,812 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:17,974 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:17,974 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:17,994 - INFO - Frame 3932 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:18,139 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:18,139 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:18,303 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:18,306 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:18,473 - INFO - Frame 3934 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:18,476 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:18,476 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:18,646 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:18,647 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:18,825 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:18,825 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:18,844 - INFO - Frame 3936 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:18,994 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:18,995 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:19,155 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:19,158 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:19,322 - INFO - Frame 3938 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:19,326 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:19,326 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:19,487 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:19,488 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:19,654 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:19,655 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:19,674 - INFO - Frame 3940 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:19,863 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:19,863 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:20,035 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:20,039 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:20,205 - INFO - Frame 3942 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:20,206 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:20,206 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:20,367 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:20,369 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:20,539 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:20,541 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:20,559 - INFO - Frame 3944 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:20,703 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:20,704 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:20,882 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:20,882 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:21,051 - INFO - Frame 3946 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:21,053 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:21,053 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:21,214 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:21,214 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:21,384 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:21,387 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:21,405 - INFO - Frame 3948 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:21,565 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:21,566 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:21,754 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:21,755 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:21,925 - INFO - Frame 3950 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:21,926 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:21,927 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:22,079 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:22,079 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:22,242 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:22,242 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:22,263 - INFO - Frame 3952 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:22,409 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:22,410 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:22,578 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:22,580 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:22,745 - INFO - Frame 3954 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:22,749 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:22,749 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:22,910 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:22,911 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:23,066 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:23,066 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:23,088 - INFO - Frame 3956 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:23,223 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:23,224 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:23,389 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:23,391 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:23,547 - INFO - Frame 3958 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:23,550 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:23,551 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:23,722 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:23,722 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:23,896 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:23,896 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:23,916 - INFO - Frame 3960 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:24,063 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:24,063 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:24,222 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:24,222 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:24,382 - INFO - Frame 3962 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:24,384 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:24,384 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:24,553 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:24,554 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:24,728 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:24,728 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:24,749 - INFO - Frame 3964 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:24,898 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:24,901 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:25,067 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:25,069 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:25,230 - INFO - Frame 3966 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:25,232 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:25,235 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:25,400 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:25,400 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:25,562 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:25,562 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:25,582 - INFO - Frame 3968 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:25,733 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:25,734 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:25,920 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:25,923 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:26,098 - INFO - Frame 3970 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:26,102 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:26,102 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:26,278 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:26,278 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:26,459 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:26,460 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:26,479 - INFO - Frame 3972 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:26,621 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:26,621 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:26,785 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:26,787 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:26,946 - INFO - Frame 3974 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:26,948 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:26,948 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:27,115 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:27,115 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:27,288 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:27,290 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:27,303 - INFO - Frame 3976 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:27,445 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:27,445 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:27,618 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:27,618 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:27,782 - INFO - Frame 3978 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:27,785 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:27,788 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:27,941 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:27,941 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:28,124 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:28,124 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:28,143 - INFO - Frame 3980 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:28,288 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:28,290 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:28,453 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:28,453 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:28,613 - INFO - Frame 3982 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:28,618 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:28,618 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:28,783 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:28,787 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:28,945 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:28,948 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:28,965 - INFO - Frame 3984 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:29,109 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:29,109 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:29,277 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:29,277 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:29,425 - INFO - Frame 3986 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:29,429 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:29,429 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:29,582 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:29,582 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:29,756 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:29,757 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:29,911 - INFO - Frame 3988 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:29,915 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:29,916 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:30,080 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:30,084 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:30,258 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:30,259 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:30,445 - INFO - Frame 3990 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:30,446 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:30,449 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:30,617 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:30,618 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:30,795 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:30,797 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:30,816 - INFO - Frame 3992 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:30,974 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:30,974 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:31,153 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:31,153 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:31,317 - INFO - Frame 3994 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:31,321 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:31,321 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:31,483 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:31,483 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:31,645 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:31,645 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:31,664 - INFO - Frame 3996 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:31,803 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:31,804 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:31,975 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:31,978 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:32,126 - INFO - Frame 3998 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:32,127 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:32,128 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:32,286 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:32,286 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:32,458 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:32,458 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:32,471 - INFO - Frame 4000 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:32,625 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:32,625 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:32,784 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:32,786 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:32,956 - INFO - Frame 4002 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:32,957 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:32,958 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:33,123 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:33,124 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:33,300 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:33,301 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:33,314 - INFO - Frame 4004 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:33,469 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:33,470 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:33,630 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:33,635 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:33,788 - INFO - Frame 4006 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:33,791 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:33,791 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:33,964 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:33,965 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:34,136 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:34,140 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:34,154 - INFO - Frame 4008 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:34,292 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:34,293 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:34,480 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:34,481 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:34,519 - INFO - Frame 4010 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:34,674 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:34,676 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:34,863 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:34,864 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:35,039 - INFO - Frame 4012 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:35,043 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:35,043 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:35,219 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:35,219 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:35,402 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:35,402 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:35,417 - INFO - Frame 4014 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:35,579 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:35,579 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:35,749 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:35,749 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:35,916 - INFO - Frame 4016 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:35,921 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:35,922 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:36,073 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:36,075 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:36,245 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:36,245 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:36,260 - INFO - Frame 4018 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:36,415 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:36,416 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:36,580 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:36,585 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:36,775 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:36,775 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:36,789 - INFO - Frame 4020 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:36,943 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:36,944 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:37,115 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:37,117 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:37,280 - INFO - Frame 4022 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:37,282 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:37,282 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:37,451 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:37,452 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:37,618 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:37,618 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:37,631 - INFO - Frame 4024 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:37,779 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:37,781 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:37,943 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:37,944 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:38,098 - INFO - Frame 4026 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:38,098 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:38,098 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:38,258 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:38,258 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:38,426 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:38,426 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:38,442 - INFO - Frame 4028 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:38,589 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:38,589 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:38,761 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:38,765 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:38,937 - INFO - Frame 4030 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:38,937 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:38,940 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:39,117 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:39,119 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:39,298 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:39,299 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:39,317 - INFO - Frame 4032 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:39,462 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:39,463 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:39,637 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:39,639 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:39,798 - INFO - Frame 4034 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:39,800 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:39,801 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:39,957 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:39,957 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:40,119 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:40,119 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:40,132 - INFO - Frame 4036 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:40,277 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:40,277 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:40,447 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:40,449 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:40,484 - INFO - Frame 4038 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:40,621 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:40,622 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:40,779 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:40,780 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:40,793 - INFO - Frame 4040 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:40,940 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:40,940 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:41,115 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:41,117 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:41,288 - INFO - Frame 4042 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:41,290 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:41,291 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:41,456 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:41,456 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:41,619 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:41,619 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:41,632 - INFO - Frame 4044 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:41,783 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:41,785 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:41,957 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:41,959 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:42,117 - INFO - Frame 4046 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:42,123 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:42,123 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:42,282 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:42,284 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:42,452 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:42,453 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:42,467 - INFO - Frame 4048 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:42,609 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:42,612 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:42,790 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:42,790 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:42,962 - INFO - Frame 4050 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:42,966 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:42,967 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:43,148 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:43,149 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:43,324 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:43,325 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:43,338 - INFO - Frame 4052 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:43,488 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:43,489 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:43,649 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:43,655 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:43,810 - INFO - Frame 4054 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:43,814 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:43,814 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:43,977 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:43,978 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:44,148 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:44,148 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:44,163 - INFO - Frame 4056 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:44,312 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:44,316 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:44,489 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:44,489 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:44,654 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:44,654 - INFO - Frame 4058 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:44,654 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:44,810 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:44,812 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:44,978 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:44,978 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:44,993 - INFO - Frame 4060 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:45,135 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:45,135 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:45,296 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:45,296 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:45,452 - INFO - Frame 4062 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:45,457 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:45,457 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:45,621 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:45,622 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:45,793 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:45,797 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:45,810 - INFO - Frame 4064 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:45,957 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:45,957 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:46,122 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:46,122 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:46,294 - INFO - Frame 4066 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:46,297 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:46,297 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:46,455 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:46,457 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:46,632 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:46,633 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:46,663 - INFO - Frame 4068 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:46,809 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:46,810 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:46,999 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:47,002 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:47,174 - INFO - Frame 4070 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:47,178 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:47,178 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:47,352 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:47,354 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:47,525 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:47,527 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:47,543 - INFO - Frame 4072 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:47,699 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:47,700 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:47,873 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:47,875 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:48,032 - INFO - Frame 4074 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:48,033 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:48,034 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:48,200 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:48,205 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:48,353 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:48,353 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:48,368 - INFO - Frame 4076 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:48,513 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:48,513 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:48,687 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:48,687 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:48,849 - INFO - Frame 4078 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:48,854 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:48,854 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:49,019 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:49,021 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:49,171 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:49,171 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:49,185 - INFO - Frame 4080 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:49,326 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:49,326 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:49,498 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:49,499 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:49,658 - INFO - Frame 4082 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:49,659 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:49,661 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:49,820 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:49,820 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:49,993 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:49,993 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:50,007 - INFO - Frame 4084 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:50,161 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:50,165 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:50,334 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:50,335 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:50,510 - INFO - Frame 4086 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:50,513 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:50,513 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:50,676 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:50,676 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:50,845 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:50,845 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:50,859 - INFO - Frame 4088 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:51,023 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:51,023 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:51,190 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:51,193 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:51,365 - INFO - Frame 4090 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:51,368 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:51,371 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:51,542 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:51,546 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:51,718 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:51,718 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:51,749 - INFO - Frame 4092 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:51,889 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:51,890 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:52,051 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:52,051 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:52,218 - INFO - Frame 4094 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:52,221 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:52,221 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:52,382 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:52,383 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:52,549 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:52,550 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:52,563 - INFO - Frame 4096 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:52,710 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:52,711 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:52,880 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:52,882 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:53,044 - INFO - Frame 4098 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:53,045 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:53,046 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:53,210 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:53,211 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:53,377 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:53,381 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:53,403 - INFO - Frame 4100 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:53,569 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:53,570 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:53,745 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:53,748 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:53,903 - INFO - Frame 4102 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:53,904 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:53,904 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:54,065 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:54,066 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:54,239 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:54,239 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:54,253 - INFO - Frame 4104 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:54,400 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:54,401 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:54,571 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:54,572 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:54,730 - INFO - Frame 4106 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:54,734 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:54,735 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:54,898 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:54,899 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:55,068 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:55,068 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:55,083 - INFO - Frame 4108 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:55,230 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:55,230 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:55,401 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:55,402 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:55,566 - INFO - Frame 4110 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:55,568 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:55,568 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:55,744 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:55,745 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:55,932 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:55,932 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:55,947 - INFO - Frame 4112 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:56,119 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:56,119 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:56,280 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:56,284 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:56,447 - INFO - Frame 4114 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:56,448 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:56,449 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:56,610 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:56,612 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:56,773 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:56,773 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:56,786 - INFO - Frame 4116 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:56,944 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:56,944 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:57,108 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:57,108 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:57,261 - INFO - Frame 4118 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:57,264 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:57,264 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:57,429 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:57,430 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:57,585 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:57,585 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:57,598 - INFO - Frame 4120 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:57,747 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:57,748 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:57,921 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:57,921 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:58,086 - INFO - Frame 4122 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:58,086 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:58,086 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:58,253 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:58,254 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:58,432 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:58,433 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:58,445 - INFO - Frame 4124 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:58,589 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:58,590 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:58,752 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:58,752 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:58,920 - INFO - Frame 4126 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:58,922 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:58,923 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:59,088 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:59,088 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:59,255 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:59,256 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:59,272 - INFO - Frame 4128 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:59,415 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:59,415 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:59,591 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:59,591 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:59,629 - INFO - Frame 4130 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:51:59,763 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:59,763 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:59,925 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:51:59,926 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:00,098 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:00,098 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:00,109 - INFO - Frame 4132 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:00,256 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:00,256 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:00,434 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:00,435 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:00,587 - INFO - Frame 4134 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:00,587 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:00,588 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:00,749 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:00,749 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:00,918 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:00,918 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:00,932 - INFO - Frame 4136 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:01,087 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:01,087 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:01,256 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:01,258 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:01,418 - INFO - Frame 4138 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:01,419 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:01,420 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:01,575 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:01,577 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:01,748 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:01,748 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:01,764 - INFO - Frame 4140 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:01,910 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:01,910 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:02,079 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:02,079 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:02,241 - INFO - Frame 4142 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:02,243 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:02,246 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:02,408 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:02,408 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:02,576 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:02,578 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:02,590 - INFO - Frame 4144 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:02,736 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:02,736 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:02,909 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:02,909 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:02,945 - INFO - Frame 4146 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:03,074 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:03,074 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:03,233 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:03,233 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:03,269 - INFO - Frame 4148 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:03,397 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:03,398 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:03,582 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:03,582 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:03,765 - INFO - Frame 4150 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:03,766 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:03,766 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:03,948 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:03,948 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:04,123 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:04,123 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:04,135 - INFO - Frame 4152 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:04,280 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:04,282 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:04,462 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:04,463 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:04,619 - INFO - Frame 4154 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:04,621 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:04,622 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:04,777 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:04,778 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:04,944 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:04,945 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:04,959 - INFO - Frame 4156 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:05,116 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:05,116 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:05,284 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:05,284 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:05,319 - INFO - Frame 4158 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:05,448 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:05,448 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:05,615 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:05,618 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:05,784 - INFO - Frame 4160 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:05,789 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:05,789 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:05,956 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:05,957 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:06,139 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:06,140 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:06,153 - INFO - Frame 4162 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:06,319 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:06,319 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:06,493 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:06,493 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:06,647 - INFO - Frame 4164 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:06,651 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:06,651 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:06,816 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:06,820 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:06,972 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:06,972 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:06,985 - INFO - Frame 4166 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:07,141 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:07,143 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:07,313 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:07,313 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:07,470 - INFO - Frame 4168 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:07,471 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:07,471 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:07,631 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:07,633 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:07,802 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:07,804 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:07,817 - INFO - Frame 4170 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:07,977 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:07,978 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:08,153 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:08,153 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:08,306 - INFO - Frame 4172 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:08,310 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:08,310 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:08,479 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:08,480 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:08,648 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:08,648 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:08,664 - INFO - Frame 4174 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:08,812 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:08,812 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:08,990 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:08,990 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:09,147 - INFO - Frame 4176 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:09,149 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:09,151 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:09,303 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:09,303 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:09,473 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:09,476 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:09,489 - INFO - Frame 4178 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:09,642 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:09,642 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:09,817 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:09,818 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:09,975 - INFO - Frame 4180 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:09,975 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:09,975 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:10,135 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:10,144 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:10,344 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:10,346 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:10,365 - INFO - Frame 4182 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:10,546 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:10,546 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:10,721 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:10,723 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:10,885 - INFO - Frame 4184 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:10,886 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:10,888 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:11,050 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:11,051 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:11,216 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:11,216 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:11,230 - INFO - Frame 4186 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:11,386 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:11,391 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:11,547 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:11,548 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:11,713 - INFO - Frame 4188 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:11,717 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:11,717 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:11,883 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:11,883 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:12,052 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:12,053 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:12,064 - INFO - Frame 4190 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:12,222 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:12,222 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:12,400 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:12,401 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:12,561 - INFO - Frame 4192 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:12,564 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:12,564 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:12,722 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:12,722 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:12,894 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:12,895 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:12,909 - INFO - Frame 4194 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:13,057 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:13,057 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:13,226 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:13,226 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:13,392 - INFO - Frame 4196 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:13,395 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:13,397 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:13,556 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:13,558 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:13,717 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:13,717 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:13,732 - INFO - Frame 4198 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:13,879 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:13,879 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:14,052 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:14,053 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:14,212 - INFO - Frame 4200 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:14,212 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:14,214 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:14,374 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:14,374 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:14,542 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:14,542 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:14,561 - INFO - Frame 4202 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:14,710 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:14,710 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:14,879 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:14,880 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:15,050 - INFO - Frame 4204 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:15,054 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:15,054 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:15,211 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:15,211 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:15,374 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:15,375 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:15,390 - INFO - Frame 4206 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:15,544 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:15,548 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:15,709 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:15,710 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:15,869 - INFO - Frame 4208 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:15,873 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:15,873 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:16,037 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:16,037 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:16,197 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:16,197 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:16,211 - INFO - Frame 4210 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:16,362 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:16,363 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:16,531 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:16,532 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:16,684 - INFO - Frame 4212 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:16,686 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:16,687 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:16,845 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:16,845 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:17,008 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:17,011 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:17,021 - INFO - Frame 4214 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:17,172 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:17,173 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:17,335 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:17,336 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:17,499 - INFO - Frame 4216 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:17,502 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:17,502 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:17,665 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:17,671 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:17,834 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:17,835 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:17,846 - INFO - Frame 4218 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:18,001 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:18,002 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:18,165 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:18,165 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:18,332 - INFO - Frame 4220 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:18,335 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:18,335 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:18,511 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:18,511 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:18,675 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:18,675 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:18,690 - INFO - Frame 4222 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:18,849 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:18,850 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:19,021 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:19,025 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:19,183 - INFO - Frame 4224 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:19,185 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:19,185 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:19,346 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:19,346 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:19,507 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:19,508 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:19,521 - INFO - Frame 4226 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:19,674 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:19,675 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:19,900 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:19,904 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:19,934 - INFO - Frame 4228 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:20,058 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:20,058 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:20,226 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:20,226 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:20,382 - INFO - Frame 4230 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:20,384 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:20,385 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:20,542 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:20,546 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:20,716 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:20,716 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:20,731 - INFO - Frame 4232 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:20,881 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:20,882 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:21,048 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:21,049 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:21,206 - INFO - Frame 4234 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:21,207 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:21,207 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:21,378 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:21,379 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:21,555 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:21,559 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:21,569 - INFO - Frame 4236 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:21,719 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:21,723 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:21,887 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:21,891 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:22,044 - INFO - Frame 4238 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:22,047 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:22,052 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:22,219 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:22,219 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:22,373 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:22,373 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:22,389 - INFO - Frame 4240 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:22,544 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:22,544 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:22,736 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:22,741 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:22,901 - INFO - Frame 4242 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:22,904 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:22,904 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:23,075 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:23,075 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:23,265 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:23,268 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:23,282 - INFO - Frame 4244 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:23,434 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:23,434 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:23,609 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:23,609 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:23,776 - INFO - Frame 4246 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:23,777 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:23,778 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:23,935 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:23,935 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:24,104 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:24,104 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:24,121 - INFO - Frame 4248 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:24,265 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:24,266 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:24,430 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:24,434 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:24,590 - INFO - Frame 4250 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:24,594 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:24,594 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:24,757 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:24,761 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:24,921 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:24,922 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:24,958 - INFO - Frame 4252 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:25,087 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:25,088 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:25,255 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:25,256 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:25,417 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:25,417 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:25,429 - INFO - Frame 4254 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:25,584 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:25,585 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:25,761 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:25,762 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:25,915 - INFO - Frame 4256 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:25,918 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:25,919 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:26,084 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:26,089 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:26,244 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:26,247 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:26,260 - INFO - Frame 4258 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:26,403 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:26,403 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:26,576 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:26,577 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:26,732 - INFO - Frame 4260 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:26,734 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:26,735 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:26,904 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:26,905 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:27,073 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:27,073 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:27,087 - INFO - Frame 4262 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:27,237 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:27,237 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:27,410 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:27,411 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:27,565 - INFO - Frame 4264 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:27,567 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:27,571 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:27,723 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:27,724 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:27,897 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:27,902 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:27,912 - INFO - Frame 4266 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:28,067 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:28,067 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:28,235 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:28,235 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:28,388 - INFO - Frame 4268 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:28,390 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:28,390 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:28,556 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:28,556 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:28,724 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:28,724 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:28,738 - INFO - Frame 4270 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:28,887 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:28,889 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:29,055 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:29,056 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:29,216 - INFO - Frame 4272 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:29,217 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:29,217 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:29,382 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:29,385 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:29,545 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:29,545 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:29,560 - INFO - Frame 4274 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:29,710 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:29,710 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:29,881 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:29,883 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:30,052 - INFO - Frame 4276 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:30,054 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:30,054 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:30,214 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:30,216 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:30,384 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:30,384 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:30,414 - INFO - Frame 4278 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:30,563 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:30,566 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:30,735 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:30,736 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:30,908 - INFO - Frame 4280 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:30,910 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:30,910 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:31,096 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:31,100 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:31,265 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:31,266 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:31,281 - INFO - Frame 4282 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:31,429 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:31,429 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:31,600 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:31,603 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:31,759 - INFO - Frame 4284 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:31,763 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:31,763 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:31,930 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:31,931 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:32,105 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:32,105 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:32,119 - INFO - Frame 4286 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:32,269 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:32,270 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:32,433 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:32,433 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:32,589 - INFO - Frame 4288 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:32,591 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:32,592 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:32,755 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:32,760 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:32,920 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:32,920 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:32,933 - INFO - Frame 4290 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:33,066 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:33,068 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:33,242 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:33,242 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:33,405 - INFO - Frame 4292 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:33,408 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:33,408 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:33,561 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:33,563 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:33,731 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:33,731 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:33,745 - INFO - Frame 4294 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:33,900 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:33,902 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:34,063 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:34,065 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:34,099 - INFO - Frame 4296 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:34,225 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:34,225 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:34,396 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:34,396 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:34,435 - INFO - Frame 4298 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:34,563 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:34,564 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:34,727 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:34,727 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:34,894 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:34,895 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:34,912 - INFO - Frame 4300 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:35,052 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:35,053 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:35,218 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:35,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:35,384 - INFO - Frame 4302 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:35,387 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:35,387 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:35,554 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:35,554 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:35,715 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:35,716 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:35,728 - INFO - Frame 4304 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:35,871 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:35,873 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:36,034 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:36,036 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:36,189 - INFO - Frame 4306 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:36,192 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:36,194 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:36,346 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:36,347 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:36,545 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:36,546 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:36,578 - INFO - Frame 4308 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:36,703 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:36,703 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:36,878 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:36,880 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:36,919 - INFO - Frame 4310 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:37,058 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:37,058 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:37,221 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:37,222 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:37,389 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:37,389 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:37,402 - INFO - Frame 4312 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:37,554 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:37,554 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:37,719 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:37,722 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:37,758 - INFO - Frame 4314 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:37,888 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:37,892 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:38,064 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:38,064 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:38,225 - INFO - Frame 4316 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:38,226 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:38,226 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:38,397 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:38,397 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:38,564 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:38,564 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:38,582 - INFO - Frame 4318 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:38,744 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:38,744 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:38,926 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:38,926 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:39,092 - INFO - Frame 4320 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:39,094 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:39,094 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:39,263 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:39,267 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:39,433 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:39,435 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:39,465 - INFO - Frame 4322 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:39,611 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:39,612 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:39,778 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:39,778 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:39,943 - INFO - Frame 4324 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:39,944 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:39,945 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:40,112 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:40,112 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:40,286 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:40,287 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:40,301 - INFO - Frame 4326 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:40,459 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:40,459 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:40,617 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:40,619 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:40,781 - INFO - Frame 4328 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:40,784 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:40,785 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:40,949 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:40,949 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:41,116 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:41,120 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:41,131 - INFO - Frame 4330 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:41,286 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:41,286 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:41,457 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:41,457 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:41,619 - INFO - Frame 4332 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:41,623 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:41,623 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:41,791 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:41,791 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:41,950 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:41,950 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:41,963 - INFO - Frame 4334 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:42,115 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:42,116 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:42,284 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:42,286 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:42,445 - INFO - Frame 4336 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:42,448 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:42,449 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:42,623 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:42,624 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:42,789 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:42,790 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:42,803 - INFO - Frame 4338 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:42,956 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:42,957 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:43,123 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:43,124 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:43,280 - INFO - Frame 4340 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:43,283 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:43,283 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:43,447 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:43,447 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:43,613 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:43,613 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:43,627 - INFO - Frame 4342 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:43,774 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:43,778 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:43,946 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:43,949 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:44,109 - INFO - Frame 4344 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:44,110 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:44,110 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:44,265 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:44,265 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:44,434 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:44,437 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:44,447 - INFO - Frame 4346 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:44,596 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:44,597 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:44,764 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:44,765 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:44,930 - INFO - Frame 4348 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:44,932 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:44,932 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:45,102 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:45,103 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:45,261 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:45,261 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:45,276 - INFO - Frame 4350 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:45,411 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:45,411 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:45,570 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:45,571 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:45,733 - INFO - Frame 4352 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:45,734 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:45,737 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:45,896 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:45,896 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:46,066 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:46,067 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:46,080 - INFO - Frame 4354 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:46,229 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:46,232 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:46,399 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:46,400 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:46,560 - INFO - Frame 4356 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:46,565 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:46,566 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:46,748 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:46,755 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:46,925 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:46,926 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:46,938 - INFO - Frame 4358 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:47,098 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:47,101 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:47,278 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:47,278 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:47,442 - INFO - Frame 4360 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:47,446 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:47,447 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:47,609 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:47,611 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:47,768 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:47,770 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:47,781 - INFO - Frame 4362 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:47,931 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:47,931 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:48,101 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:48,102 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:48,270 - INFO - Frame 4364 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:48,271 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:48,271 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:48,428 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:48,429 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:48,599 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:48,601 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:48,611 - INFO - Frame 4366 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:48,761 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:48,761 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:48,925 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:48,925 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:49,088 - INFO - Frame 4368 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:49,089 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:49,089 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:49,242 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:49,242 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:49,404 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:49,408 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:49,418 - INFO - Frame 4370 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:49,574 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:49,574 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:49,744 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:49,745 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:49,911 - INFO - Frame 4372 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:49,912 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:49,913 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:50,078 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:50,078 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:50,244 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:50,245 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:50,258 - INFO - Frame 4374 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:50,408 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:50,408 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:50,581 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:50,582 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:50,741 - INFO - Frame 4376 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:50,745 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:50,746 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:50,924 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:50,925 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:51,093 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:51,096 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:51,109 - INFO - Frame 4378 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:51,272 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:51,272 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:51,449 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:51,449 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:51,657 - INFO - Frame 4380 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:51,659 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:51,660 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:51,821 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:51,821 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:51,993 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:51,995 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:52,008 - INFO - Frame 4382 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:52,155 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:52,155 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:52,327 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:52,327 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:52,491 - INFO - Frame 4384 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:52,493 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:52,496 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:52,659 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:52,661 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:52,825 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:52,826 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:52,840 - INFO - Frame 4386 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:52,990 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:52,991 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:53,172 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:53,174 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:53,325 - INFO - Frame 4388 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:53,328 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:53,331 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:53,483 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:53,483 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:53,656 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:53,656 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:53,670 - INFO - Frame 4390 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:53,823 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:53,823 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:53,982 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:53,983 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:54,020 - INFO - Frame 4392 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:54,152 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:54,153 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:54,321 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:54,325 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:54,478 - INFO - Frame 4394 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:54,482 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:54,482 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:54,648 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:54,648 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:54,814 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:54,814 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:54,828 - INFO - Frame 4396 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:54,988 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:54,988 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:55,147 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:55,147 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:55,182 - INFO - Frame 4398 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:55,308 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:55,308 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:55,463 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:55,463 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:55,627 - INFO - Frame 4400 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:55,630 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:55,630 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:55,802 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:55,802 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:55,966 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:55,966 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:55,980 - INFO - Frame 4402 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:56,130 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:56,131 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:56,313 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:56,314 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:56,481 - INFO - Frame 4404 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:56,484 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:56,485 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:56,658 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:56,659 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:56,836 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:56,837 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:56,847 - INFO - Frame 4406 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:57,001 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:57,005 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:57,174 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:57,178 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:57,332 - INFO - Frame 4408 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:57,335 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:57,335 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:57,495 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:57,496 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:57,663 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:57,665 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:57,677 - INFO - Frame 4410 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:57,828 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:57,832 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:58,002 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:58,005 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:58,155 - INFO - Frame 4412 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:58,157 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:58,160 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:58,316 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:58,316 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:58,480 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:58,483 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:58,497 - INFO - Frame 4414 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:58,653 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:58,653 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:58,812 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:58,812 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:58,848 - INFO - Frame 4416 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:58,972 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:58,972 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:59,141 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:59,141 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:59,295 - INFO - Frame 4418 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:59,299 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:59,299 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:59,466 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:59,468 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:59,637 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:59,637 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:59,653 - INFO - Frame 4420 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:52:59,791 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:59,792 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:59,954 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:52:59,958 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:00,115 - INFO - Frame 4422 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:00,117 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:00,118 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:00,283 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:00,283 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:00,453 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:00,454 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:00,465 - INFO - Frame 4424 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:00,634 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:00,635 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:00,806 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:00,807 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:00,986 - INFO - Frame 4426 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:00,986 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:00,986 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:01,154 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:01,155 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:01,333 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:01,335 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:01,346 - INFO - Frame 4428 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:01,500 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:01,500 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:01,677 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:01,677 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:01,841 - INFO - Frame 4430 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:01,842 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:01,842 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:02,009 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:02,009 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:02,173 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:02,174 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:02,190 - INFO - Frame 4432 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:02,331 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:02,332 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:02,509 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:02,513 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:02,664 - INFO - Frame 4434 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:02,668 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:02,668 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:02,832 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:02,832 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:03,012 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:03,012 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:03,028 - INFO - Frame 4436 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:03,181 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:03,183 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:03,347 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:03,351 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:03,511 - INFO - Frame 4438 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:03,512 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:03,513 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:03,682 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:03,682 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:03,853 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:03,853 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:03,866 - INFO - Frame 4440 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:04,009 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:04,010 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:04,179 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:04,179 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:04,344 - INFO - Frame 4442 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:04,345 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:04,345 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:04,501 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:04,502 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:04,671 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:04,671 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:04,842 - INFO - Frame 4444 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:04,846 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:04,847 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:04,997 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:04,997 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:05,175 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:05,175 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:05,196 - INFO - Frame 4446 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:05,355 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:05,357 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:05,523 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:05,525 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:05,709 - INFO - Frame 4448 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:05,712 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:05,713 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:05,877 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:05,877 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:06,050 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:06,057 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:06,072 - INFO - Frame 4450 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:06,202 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:06,202 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:06,370 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:06,372 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:06,542 - INFO - Frame 4452 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:06,545 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:06,545 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:06,712 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:06,712 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:06,876 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:06,877 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:06,897 - INFO - Frame 4454 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:07,047 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:07,047 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:07,219 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:07,219 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:07,419 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:07,421 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:07,441 - INFO - Frame 4456 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:07,594 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:07,594 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:07,759 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:07,759 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:07,921 - INFO - Frame 4458 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:07,925 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:07,926 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:08,087 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:08,087 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:08,242 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:08,243 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:08,260 - INFO - Frame 4460 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:08,401 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:08,401 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:08,575 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:08,575 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:08,745 - INFO - Frame 4462 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:08,747 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:08,748 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:08,916 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:08,917 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:09,082 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:09,084 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:09,102 - INFO - Frame 4464 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:09,252 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:09,253 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:09,427 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:09,432 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:09,591 - INFO - Frame 4466 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:09,594 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:09,596 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:09,761 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:09,761 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:09,937 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:09,937 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:09,955 - INFO - Frame 4468 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:10,095 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:10,095 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:10,265 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:10,267 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:10,427 - INFO - Frame 4470 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:10,431 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:10,432 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:10,591 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:10,591 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:10,752 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:10,753 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:10,771 - INFO - Frame 4472 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:10,920 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:10,920 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:11,084 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:11,085 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:11,248 - INFO - Frame 4474 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:11,252 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:11,252 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:11,412 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:11,413 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:11,583 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:11,584 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:11,600 - INFO - Frame 4476 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:11,757 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:11,757 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:11,923 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:11,924 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:12,091 - INFO - Frame 4478 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:12,094 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:12,095 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:12,262 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:12,262 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:12,436 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:12,437 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:12,455 - INFO - Frame 4480 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:12,605 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:12,605 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:12,774 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:12,774 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:12,929 - INFO - Frame 4482 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:12,931 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:12,934 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:13,105 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:13,105 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:13,274 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:13,274 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:13,293 - INFO - Frame 4484 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:13,433 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:13,435 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:13,609 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:13,610 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:13,774 - INFO - Frame 4486 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:13,777 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:13,779 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:13,937 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:13,939 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:14,110 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:14,112 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:14,129 - INFO - Frame 4488 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:14,278 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:14,279 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:14,455 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:14,455 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:14,612 - INFO - Frame 4490 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:14,615 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:14,616 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:14,774 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:14,775 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:14,938 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:14,939 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:14,959 - INFO - Frame 4492 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:15,093 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:15,093 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:15,260 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:15,260 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:15,409 - INFO - Frame 4494 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:15,412 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:15,412 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:15,570 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:15,570 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:15,735 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:15,735 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:15,758 - INFO - Frame 4496 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:15,911 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:15,911 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:16,077 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:16,079 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:16,245 - INFO - Frame 4498 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:16,248 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:16,249 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:16,416 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:16,422 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:16,594 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:16,594 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:16,616 - INFO - Frame 4500 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:16,759 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:16,759 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:16,932 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:16,932 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:17,104 - INFO - Frame 4502 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:17,107 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:17,108 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:17,286 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:17,287 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:17,462 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:17,462 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:17,482 - INFO - Frame 4504 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:17,636 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:17,637 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:17,805 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:17,806 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:17,977 - INFO - Frame 4506 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:17,978 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:17,980 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:18,138 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:18,138 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:18,316 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:18,316 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:18,334 - INFO - Frame 4508 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:18,486 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:18,487 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:18,656 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:18,657 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:18,831 - INFO - Frame 4510 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:18,835 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:18,839 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:18,999 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:19,001 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:19,159 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:19,159 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:19,179 - INFO - Frame 4512 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:19,325 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:19,325 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:19,485 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:19,486 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:19,646 - INFO - Frame 4514 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:19,647 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:19,647 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:19,865 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:19,865 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:20,037 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:20,037 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:20,057 - INFO - Frame 4516 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:20,199 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:20,199 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:20,372 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:20,374 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:20,535 - INFO - Frame 4518 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:20,538 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:20,538 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:20,702 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:20,702 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:20,877 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:20,877 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:20,897 - INFO - Frame 4520 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:21,042 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:21,043 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:21,218 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:21,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:21,379 - INFO - Frame 4522 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:21,383 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:21,384 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:21,560 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:21,562 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:21,732 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:21,733 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:21,751 - INFO - Frame 4524 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:21,902 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:21,906 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:22,066 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:22,066 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:22,236 - INFO - Frame 4526 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:22,238 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:22,242 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:22,398 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:22,399 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:22,572 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:22,574 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:22,592 - INFO - Frame 4528 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:22,736 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:22,736 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:22,903 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:22,905 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:23,060 - INFO - Frame 4530 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 2
2025-11-24 17:53:23,060 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:23,063 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:23,223 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:23,228 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:23,382 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:23,383 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:23,402 - INFO - Frame 4532 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:23,556 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:23,559 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:23,732 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:23,732 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:23,904 - INFO - Frame 4534 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:23,905 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:23,905 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:24,081 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:24,087 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:24,257 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:24,259 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:24,277 - INFO - Frame 4536 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:24,427 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:24,427 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:24,592 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:24,593 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:24,751 - INFO - Frame 4538 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:24,756 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:24,756 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:24,920 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:24,921 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:25,093 - INFO - Frame 4540 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:25,097 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:25,100 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:25,265 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:25,266 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:25,436 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:25,441 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:25,457 - INFO - Frame 4542 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:25,612 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:25,612 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:25,783 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:25,783 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:25,945 - INFO - Frame 4544 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:25,947 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:25,947 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:26,114 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:26,115 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:26,284 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:26,284 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:26,300 - INFO - Frame 4546 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:26,453 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:26,453 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:26,621 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:26,624 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:26,788 - INFO - Frame 4548 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:26,792 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:26,792 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:26,965 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:26,966 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:27,145 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:27,149 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:27,166 - INFO - Frame 4550 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:27,313 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:27,314 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:27,486 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:27,487 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:27,648 - INFO - Frame 4552 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:27,654 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:27,654 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:27,818 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:27,818 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:27,989 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:27,990 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:28,009 - INFO - Frame 4554 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:28,155 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:28,157 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:28,329 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:28,329 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:28,488 - INFO - Frame 4556 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:28,492 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:28,492 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:28,658 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:28,661 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:28,823 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:28,827 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:28,846 - INFO - Frame 4558 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:28,995 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:28,996 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:29,170 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:29,170 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:29,332 - INFO - Frame 4560 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:29,335 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:29,339 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:29,505 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:29,505 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:29,671 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:29,671 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:29,690 - INFO - Frame 4562 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:29,833 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:29,837 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:30,007 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:30,007 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:30,172 - INFO - Frame 4564 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:30,173 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:30,174 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:30,338 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:30,339 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:30,514 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:30,515 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:30,530 - INFO - Frame 4566 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:30,682 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:30,683 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:30,860 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:30,861 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:31,040 - INFO - Frame 4568 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:31,043 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:31,044 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:31,212 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:31,213 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:31,389 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:31,391 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:31,410 - INFO - Frame 4570 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:31,547 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:31,550 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:31,715 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:31,716 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:31,868 - INFO - Frame 4572 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:31,870 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:31,873 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:32,038 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:32,039 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:32,204 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:32,204 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:32,225 - INFO - Frame 4574 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:32,361 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:32,363 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:32,538 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:32,539 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:32,691 - INFO - Frame 4576 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:32,695 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:32,696 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:32,853 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:32,854 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:33,015 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:33,015 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:33,034 - INFO - Frame 4578 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:33,188 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:33,189 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:33,357 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:33,358 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:33,523 - INFO - Frame 4580 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:33,525 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:33,526 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:33,684 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:33,685 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:33,857 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:33,861 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:33,877 - INFO - Frame 4582 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:34,017 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:34,018 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:34,188 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:34,188 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:34,350 - INFO - Frame 4584 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:34,355 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:34,356 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:34,530 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:34,531 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:34,699 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:34,703 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:34,719 - INFO - Frame 4586 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:34,889 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:34,890 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:35,059 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:35,060 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:35,218 - INFO - Frame 4588 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:35,221 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:35,221 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:35,377 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:35,379 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:35,536 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:35,537 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:35,553 - INFO - Frame 4590 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:35,699 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:35,700 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:35,859 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:35,859 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:36,022 - INFO - Frame 4592 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:36,026 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:36,026 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:36,229 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:36,230 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:36,392 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:36,393 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:36,411 - INFO - Frame 4594 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:36,561 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:36,561 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:36,736 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:36,738 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:36,912 - INFO - Frame 4596 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:36,915 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:36,916 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:37,077 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:37,077 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:37,248 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:37,249 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:37,269 - INFO - Frame 4598 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:37,419 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:37,419 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:37,582 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:37,583 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:37,747 - INFO - Frame 4600 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:37,749 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:37,749 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:37,922 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:37,923 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:38,089 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:38,090 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:38,237 - INFO - Frame 4602 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:38,241 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:38,241 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:38,412 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:38,412 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:38,590 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:38,592 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:38,612 - INFO - Frame 4604 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:38,767 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:38,767 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:38,942 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:38,942 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:39,106 - INFO - Frame 4606 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:39,109 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:39,109 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:39,280 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:39,280 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:39,454 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:39,455 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:39,620 - INFO - Frame 4608 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:39,624 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:39,625 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:39,789 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:39,789 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:39,963 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:39,963 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:40,127 - INFO - Frame 4610 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:40,129 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:40,130 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:40,296 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:40,301 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:40,469 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:40,471 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:40,483 - INFO - Frame 4612 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:40,633 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:40,633 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:40,804 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:40,805 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:40,965 - INFO - Frame 4614 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:40,970 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:40,971 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:41,141 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:41,141 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:41,310 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:41,313 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:41,325 - INFO - Frame 4616 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:41,479 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:41,479 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:41,645 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:41,646 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:41,801 - INFO - Frame 4618 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:41,806 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:41,806 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:41,975 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:41,976 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:42,150 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:42,150 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:42,167 - INFO - Frame 4620 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:42,310 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:42,310 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:42,494 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:42,494 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:42,656 - INFO - Frame 4622 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:42,658 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:42,659 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:42,816 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:42,816 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:42,981 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:42,981 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:42,996 - INFO - Frame 4624 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:43,147 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:43,147 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:43,320 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:43,321 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:43,490 - INFO - Frame 4626 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:43,490 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:43,495 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:43,656 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:43,657 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:43,826 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:43,829 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:43,845 - INFO - Frame 4628 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:43,981 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:43,982 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:44,149 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:44,150 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:44,315 - INFO - Frame 4630 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:44,317 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:44,318 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:44,491 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:44,492 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:44,666 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:44,670 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:44,680 - INFO - Frame 4632 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:44,836 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:44,836 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:45,005 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:45,005 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:45,165 - INFO - Frame 4634 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:45,169 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:45,169 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:45,330 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:45,331 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:45,496 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:45,496 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:45,512 - INFO - Frame 4636 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:45,664 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:45,665 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:45,839 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:45,844 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:46,012 - INFO - Frame 4638 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:46,016 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:46,018 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:46,178 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:46,178 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:46,354 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:46,354 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:46,369 - INFO - Frame 4640 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:46,521 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:46,521 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:46,709 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:46,710 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:46,871 - INFO - Frame 4642 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:46,872 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:46,872 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:47,041 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:47,043 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:47,216 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:47,217 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:47,231 - INFO - Frame 4644 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:47,376 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:47,376 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:47,552 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:47,552 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:47,711 - INFO - Frame 4646 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:47,715 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:47,716 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:47,885 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:47,885 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:48,055 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:48,055 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:48,070 - INFO - Frame 4648 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:48,224 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:48,224 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:48,395 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:48,396 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:48,507 - INFO - Frame 4650 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:48,570 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:48,571 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:48,726 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:48,728 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:48,894 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:48,894 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:48,907 - INFO - Frame 4652 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:49,060 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:49,061 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:49,223 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:49,223 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:49,383 - INFO - Frame 4654 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:49,386 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:49,388 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:49,560 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:49,561 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:49,733 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:49,735 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:49,747 - INFO - Frame 4656 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:49,908 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:49,908 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:50,082 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:50,083 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:50,250 - INFO - Frame 4658 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:50,255 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:50,255 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:50,427 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:50,427 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:50,612 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:50,612 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:50,627 - INFO - Frame 4660 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:50,782 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:50,782 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:50,961 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:50,962 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:51,117 - INFO - Frame 4662 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:51,121 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:51,121 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:51,276 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:51,276 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:51,446 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:51,447 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:51,461 - INFO - Frame 4664 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:51,615 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:51,617 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:51,792 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:51,794 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:51,947 - INFO - Frame 4666 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:51,949 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:51,950 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:52,121 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:52,123 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:52,288 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:52,293 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:52,301 - INFO - Frame 4668 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:52,453 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:52,453 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:52,638 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:52,639 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:52,796 - INFO - Frame 4670 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:52,799 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:52,799 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:52,960 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:52,960 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:53,131 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:53,132 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:53,325 - INFO - Frame 4672 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:53,325 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:53,330 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:53,489 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:53,492 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:53,658 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:53,658 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:53,678 - INFO - Frame 4674 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:53,823 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:53,823 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:54,004 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:54,005 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:54,175 - INFO - Frame 4676 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:54,178 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:54,181 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:54,347 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:54,348 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:54,539 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:54,539 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:54,559 - INFO - Frame 4678 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:54,694 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:54,694 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:54,881 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:54,882 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:55,043 - INFO - Frame 4680 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:55,047 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:55,048 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:55,215 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:55,215 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:55,383 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:55,384 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:55,402 - INFO - Frame 4682 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:55,546 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:55,550 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:55,707 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:55,708 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:55,865 - INFO - Frame 4684 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:55,867 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:55,868 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:56,033 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:56,033 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:56,213 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:56,214 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:56,233 - INFO - Frame 4686 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:56,382 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:56,382 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:56,555 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:56,555 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:56,719 - INFO - Frame 4688 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:56,723 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:56,724 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:56,892 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:56,893 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:57,061 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:57,062 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:57,081 - INFO - Frame 4690 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:57,224 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:57,224 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:57,395 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:57,396 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:57,556 - INFO - Frame 4692 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:57,558 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:57,559 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:57,731 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:57,731 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:57,899 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:57,901 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:57,919 - INFO - Frame 4694 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:58,079 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:58,080 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:58,255 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:58,255 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:58,421 - INFO - Frame 4696 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:58,423 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:58,423 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:58,587 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:58,588 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:58,761 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:58,761 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:58,782 - INFO - Frame 4698 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:58,919 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:58,920 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:59,092 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:59,093 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:59,265 - INFO - Frame 4700 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:59,266 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:59,266 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:59,441 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:59,442 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:59,609 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:59,609 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:59,774 - INFO - Frame 4702 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:53:59,775 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:59,777 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:59,937 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:53:59,938 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:00,107 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:00,109 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:00,126 - INFO - Frame 4704 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:00,274 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:00,276 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:00,448 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:00,449 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:00,607 - INFO - Frame 4706 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:00,611 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:00,611 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:00,780 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:00,780 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:00,950 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:00,950 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:00,970 - INFO - Frame 4708 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:01,120 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:01,121 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:01,289 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:01,289 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:01,452 - INFO - Frame 4710 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:01,455 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:01,456 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:01,613 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:01,613 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:01,770 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:01,773 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:01,791 - INFO - Frame 4712 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:01,941 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:01,941 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:02,112 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:02,114 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:02,284 - INFO - Frame 4714 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:02,288 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:02,288 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:02,458 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:02,460 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:02,637 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:02,638 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:02,653 - INFO - Frame 4716 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:02,808 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:02,808 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:02,986 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:02,986 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:03,157 - INFO - Frame 4718 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:03,160 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:03,160 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:03,329 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:03,330 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:03,495 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:03,496 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:03,516 - INFO - Frame 4720 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:03,666 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:03,666 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:03,831 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:03,832 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:03,993 - INFO - Frame 4722 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:03,995 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:03,998 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:04,162 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:04,162 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:04,328 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:04,329 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:04,348 - INFO - Frame 4724 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:04,498 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:04,499 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:04,668 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:04,670 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:04,834 - INFO - Frame 4726 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:04,839 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:04,839 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:05,012 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:05,013 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:05,179 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:05,179 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:05,198 - INFO - Frame 4728 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:05,343 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:05,347 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:05,514 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:05,516 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:05,678 - INFO - Frame 4730 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:05,680 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:05,680 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:05,842 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:05,844 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:06,018 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:06,021 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:06,036 - INFO - Frame 4732 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:06,191 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:06,195 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:06,372 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:06,373 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:06,545 - INFO - Frame 4734 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:06,550 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:06,551 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:06,718 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:06,719 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:06,888 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:06,888 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:06,909 - INFO - Frame 4736 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:07,055 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:07,056 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:07,226 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:07,227 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:07,397 - INFO - Frame 4738 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:07,400 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:07,400 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:07,560 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:07,561 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:07,729 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:07,729 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:07,750 - INFO - Frame 4740 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:07,898 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:07,902 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:08,075 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:08,075 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:08,240 - INFO - Frame 4742 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:08,244 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:08,244 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:08,416 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:08,416 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:08,588 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:08,588 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:08,606 - INFO - Frame 4744 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:08,756 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:08,756 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:08,931 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:08,932 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:09,093 - INFO - Frame 4746 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:09,097 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:09,097 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:09,262 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:09,268 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:09,439 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:09,440 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:09,460 - INFO - Frame 4748 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:09,609 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:09,610 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:09,796 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:09,797 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:09,969 - INFO - Frame 4750 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:09,973 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:09,974 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:10,144 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:10,144 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:10,318 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:10,318 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:10,335 - INFO - Frame 4752 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:10,482 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:10,482 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:10,657 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:10,657 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:10,862 - INFO - Frame 4754 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:10,863 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:10,863 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:11,018 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:11,019 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:11,193 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:11,193 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:11,216 - INFO - Frame 4756 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:11,368 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:11,370 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:11,537 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:11,538 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:11,703 - INFO - Frame 4758 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:11,705 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:11,706 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:11,867 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:11,869 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:12,033 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:12,034 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:12,049 - INFO - Frame 4760 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:12,201 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:12,201 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:12,370 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:12,371 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:12,532 - INFO - Frame 4762 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:12,535 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:12,536 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:12,697 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:12,698 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:12,873 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:12,874 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:12,894 - INFO - Frame 4764 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:13,042 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:13,042 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:13,212 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:13,214 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:13,376 - INFO - Frame 4766 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:13,380 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:13,380 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:13,544 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:13,546 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:13,710 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:13,710 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:13,730 - INFO - Frame 4768 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:13,879 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:13,879 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:14,051 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:14,051 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:14,220 - INFO - Frame 4770 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:14,223 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:14,223 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:14,391 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:14,392 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:14,557 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:14,557 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:14,576 - INFO - Frame 4772 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:14,726 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:14,726 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:14,908 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:14,911 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:15,079 - INFO - Frame 4774 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:15,082 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:15,086 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:15,249 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:15,250 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:15,427 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:15,427 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:15,446 - INFO - Frame 4776 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:15,588 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:15,590 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:15,759 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:15,759 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:15,922 - INFO - Frame 4778 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:15,924 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:15,924 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:16,088 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:16,090 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:16,262 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:16,262 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:16,279 - INFO - Frame 4780 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:16,440 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:16,440 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:16,603 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:16,603 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:16,762 - INFO - Frame 4782 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:16,766 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:16,767 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:16,926 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:16,931 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:17,091 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:17,092 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:17,110 - INFO - Frame 4784 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:17,245 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:17,246 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:17,413 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:17,413 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:17,583 - INFO - Frame 4786 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:17,585 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:17,586 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:17,764 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:17,767 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:17,948 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:17,951 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:17,972 - INFO - Frame 4788 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:18,124 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:18,124 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:18,302 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:18,306 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:18,477 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:18,478 - INFO - Frame 4790 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:18,478 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:18,661 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:18,666 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:18,829 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:18,829 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:18,850 - INFO - Frame 4792 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:18,996 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:18,996 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:19,175 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:19,176 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:19,344 - INFO - Frame 4794 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:19,348 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:19,348 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:19,522 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:19,523 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:19,699 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:19,699 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:19,718 - INFO - Frame 4796 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:19,921 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:19,922 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:20,097 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:20,101 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:20,266 - INFO - Frame 4798 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:20,271 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:20,272 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:20,445 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:20,445 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:20,619 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:20,620 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:20,643 - INFO - Frame 4800 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:20,791 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:20,791 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:20,970 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:20,970 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:21,152 - INFO - Frame 4802 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:21,153 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:21,155 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:21,311 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:21,312 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:21,480 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:21,480 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:21,499 - INFO - Frame 4804 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:21,649 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:21,649 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:21,852 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:21,856 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:22,022 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:22,022 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:22,039 - INFO - Frame 4806 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:22,184 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:22,187 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:22,361 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:22,363 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:22,537 - INFO - Frame 4808 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:22,541 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:22,541 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:22,714 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:22,715 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:22,888 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:22,889 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:22,902 - INFO - Frame 4810 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:23,065 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:23,065 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:23,232 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:23,232 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:23,331 - INFO - Frame 4812 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:23,390 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:23,390 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:23,556 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:23,561 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:23,730 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:23,731 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:23,745 - INFO - Frame 4814 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:23,895 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:23,895 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:24,067 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:24,068 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:24,104 - INFO - Frame 4816 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:24,230 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:24,230 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:24,388 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:24,390 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:24,552 - INFO - Frame 4818 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:24,556 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:24,556 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:24,725 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:24,725 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:24,893 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:24,893 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:24,908 - INFO - Frame 4820 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:25,055 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:25,055 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:25,216 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:25,216 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:25,372 - INFO - Frame 4822 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:25,376 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:25,378 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:25,542 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:25,544 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:25,712 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:25,712 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:25,725 - INFO - Frame 4824 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:25,873 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:25,874 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:26,045 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:26,046 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:26,213 - INFO - Frame 4826 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:26,215 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:26,215 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:26,382 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:26,383 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:26,552 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:26,552 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:26,570 - INFO - Frame 4828 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:26,726 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:26,726 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:26,901 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:26,904 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:27,088 - INFO - Frame 4830 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:27,093 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:27,093 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:27,264 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:27,266 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:27,442 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:27,446 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:27,460 - INFO - Frame 4832 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:27,608 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:27,609 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:27,778 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:27,778 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:27,813 - INFO - Frame 4834 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:27,944 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:27,944 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:28,102 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:28,104 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:28,261 - INFO - Frame 4836 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:28,266 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:28,266 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:28,434 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:28,435 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:28,598 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:28,599 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:28,615 - INFO - Frame 4838 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:28,765 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:28,766 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:28,934 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:28,938 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:29,093 - INFO - Frame 4840 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:29,096 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:29,098 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:29,257 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:29,259 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:29,420 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:29,421 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:29,433 - INFO - Frame 4842 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:29,587 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:29,587 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:29,771 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:29,773 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:29,937 - INFO - Frame 4844 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:29,940 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:29,941 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:30,116 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:30,118 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:30,291 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:30,291 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:30,309 - INFO - Frame 4846 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:30,459 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:30,461 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:30,644 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:30,646 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:30,818 - INFO - Frame 4848 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:30,822 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:30,823 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:30,997 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:30,999 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:31,189 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:31,191 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:31,204 - INFO - Frame 4850 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:31,357 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:31,358 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:31,527 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:31,527 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:31,689 - INFO - Frame 4852 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:31,691 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:31,691 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:31,859 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:31,861 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:32,036 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:32,037 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:32,050 - INFO - Frame 4854 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:32,204 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:32,205 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:32,379 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:32,379 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:32,538 - INFO - Frame 4856 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:32,542 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:32,542 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:32,705 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:32,705 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:32,875 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:32,879 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:32,892 - INFO - Frame 4858 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:33,045 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:33,046 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:33,216 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:33,218 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:33,370 - INFO - Frame 4860 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:33,373 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:33,373 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:33,539 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:33,540 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:33,714 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:33,715 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:33,728 - INFO - Frame 4862 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:33,879 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:33,881 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:34,044 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:34,044 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:34,199 - INFO - Frame 4864 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:34,202 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:34,203 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:34,369 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:34,369 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:34,544 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:34,548 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:34,577 - INFO - Frame 4866 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:34,703 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:34,703 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:34,897 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:34,901 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:35,065 - INFO - Frame 4868 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:35,069 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:35,069 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:35,252 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:35,253 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:35,417 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:35,417 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:35,431 - INFO - Frame 4870 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:35,581 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:35,585 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:35,754 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:35,754 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:35,917 - INFO - Frame 4872 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:35,922 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:35,922 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:36,090 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:36,090 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:36,267 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:36,267 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:36,279 - INFO - Frame 4874 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:36,432 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:36,432 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:36,600 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:36,600 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:36,765 - INFO - Frame 4876 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:36,766 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:36,767 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:36,920 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:36,921 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:37,093 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:37,094 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:37,108 - INFO - Frame 4878 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:37,265 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:37,266 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:37,436 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:37,437 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:37,602 - INFO - Frame 4880 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:37,605 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:37,605 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:37,771 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:37,772 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:37,945 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:37,945 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:37,960 - INFO - Frame 4882 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:38,108 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:38,109 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:38,277 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:38,278 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:38,439 - INFO - Frame 4884 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:38,441 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:38,441 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:38,599 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:38,601 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:38,770 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:38,771 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:38,786 - INFO - Frame 4886 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:38,945 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:38,948 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:39,129 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:39,133 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:39,303 - INFO - Frame 4888 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:39,304 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:39,307 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:39,474 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:39,475 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:39,630 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:39,630 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:39,644 - INFO - Frame 4890 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:39,790 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:39,791 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:39,970 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:39,971 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:40,133 - INFO - Frame 4892 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:40,138 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:40,138 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:40,306 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:40,306 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:40,478 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:40,479 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:40,493 - INFO - Frame 4894 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:40,646 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:40,646 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:40,816 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:40,816 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:40,985 - INFO - Frame 4896 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:40,988 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:40,990 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:41,154 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:41,156 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:41,310 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:41,312 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:41,325 - INFO - Frame 4898 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:41,474 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:41,474 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:41,648 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:41,651 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:41,816 - INFO - Frame 4900 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:41,821 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:41,822 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:41,982 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:41,983 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:42,155 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:42,155 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:42,181 - INFO - Frame 4902 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:42,320 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:42,321 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:42,487 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:42,488 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:42,653 - INFO - Frame 4904 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:42,654 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:42,654 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:42,818 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:42,819 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:42,993 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:42,994 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:43,008 - INFO - Frame 4906 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:43,166 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:43,169 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:43,342 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:43,342 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:43,522 - INFO - Frame 4908 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:43,526 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:43,527 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:43,704 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:43,704 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:43,880 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:43,881 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:43,894 - INFO - Frame 4910 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:44,049 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:44,049 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:44,230 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:44,233 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:44,426 - INFO - Frame 4912 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:44,432 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:44,433 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:44,604 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:44,605 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:44,781 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:44,781 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:44,795 - INFO - Frame 4914 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:44,959 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:44,959 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:45,119 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:45,122 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:45,279 - INFO - Frame 4916 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:45,283 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:45,283 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:45,445 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:45,445 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:45,606 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:45,607 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:45,620 - INFO - Frame 4918 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:45,772 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:45,772 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:45,944 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:45,946 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:46,108 - INFO - Frame 4920 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:46,112 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:46,112 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:46,278 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:46,279 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:46,443 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:46,443 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:46,458 - INFO - Frame 4922 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:46,612 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:46,614 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:46,790 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:46,790 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:46,947 - INFO - Frame 4924 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:46,948 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:46,948 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:47,118 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:47,119 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:47,295 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:47,295 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:47,309 - INFO - Frame 4926 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:47,464 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:47,465 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:47,636 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:47,637 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:47,812 - INFO - Frame 4928 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:47,813 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:47,815 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:47,983 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:47,988 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:48,165 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:48,168 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:48,180 - INFO - Frame 4930 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:48,355 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:48,355 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:48,531 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:48,531 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:48,696 - INFO - Frame 4932 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:48,699 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:48,699 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:48,867 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:48,875 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:49,046 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:49,047 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:49,061 - INFO - Frame 4934 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:49,216 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:49,216 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:49,402 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:49,404 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:49,574 - INFO - Frame 4936 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:49,577 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:49,577 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:49,741 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:49,742 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:49,910 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:49,910 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:49,925 - INFO - Frame 4938 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:50,078 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:50,078 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:50,241 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:50,242 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:50,397 - INFO - Frame 4940 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:50,400 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:50,400 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:50,563 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:50,565 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:50,749 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:50,749 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:50,763 - INFO - Frame 4942 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:50,921 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:50,922 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:51,093 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:51,094 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:51,260 - INFO - Frame 4944 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:51,263 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:51,267 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:51,423 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:51,424 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:51,596 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:51,598 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:51,610 - INFO - Frame 4946 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:51,772 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:51,772 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:51,946 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:51,946 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:52,114 - INFO - Frame 4948 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:52,116 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:52,116 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:52,283 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:52,285 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:52,458 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:52,459 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:52,472 - INFO - Frame 4950 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:52,630 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:52,631 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:52,810 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:52,810 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:52,978 - INFO - Frame 4952 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:52,978 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:52,978 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:53,135 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:53,137 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:53,313 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:53,314 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:53,327 - INFO - Frame 4954 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:53,480 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:53,480 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:53,653 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:53,654 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:53,814 - INFO - Frame 4956 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:53,817 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:53,817 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:53,973 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:53,974 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:54,140 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:54,143 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:54,154 - INFO - Frame 4958 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:54,302 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:54,303 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:54,482 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:54,483 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:54,656 - INFO - Frame 4960 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:54,656 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:54,656 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:54,816 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:54,823 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:54,982 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:54,983 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:54,996 - INFO - Frame 4962 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:55,141 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:55,141 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:55,315 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:55,315 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:55,483 - INFO - Frame 4964 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:55,485 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:55,485 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:55,643 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:55,643 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:55,810 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:55,811 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:55,826 - INFO - Frame 4966 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:55,985 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:55,986 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:56,158 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:56,158 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:56,319 - INFO - Frame 4968 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:56,323 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:56,323 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:56,501 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:56,502 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:56,676 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:56,677 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:56,696 - INFO - Frame 4970 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:56,862 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:56,863 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:57,036 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:57,037 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:57,194 - INFO - Frame 4972 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:57,197 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:57,198 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:57,363 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:57,368 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:57,540 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:57,540 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:57,553 - INFO - Frame 4974 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:57,708 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:57,708 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:57,886 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:57,886 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:58,034 - INFO - Frame 4976 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:58,038 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:58,039 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:58,217 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:58,217 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:58,380 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:58,380 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:58,396 - INFO - Frame 4978 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:58,540 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:58,540 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:58,712 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:58,713 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:58,880 - INFO - Frame 4980 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:58,881 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:58,882 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:59,043 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:59,044 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:59,224 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:59,224 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:59,239 - INFO - Frame 4982 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:59,392 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:59,393 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:59,559 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:59,559 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:59,724 - INFO - Frame 4984 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:54:59,729 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:59,730 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:59,895 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:54:59,896 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:00,070 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:00,071 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:00,086 - INFO - Frame 4986 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:00,248 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:00,250 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:00,422 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:00,425 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:00,587 - INFO - Frame 4988 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:00,588 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:00,589 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:00,752 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:00,756 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:00,930 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:00,930 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:00,944 - INFO - Frame 4990 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:01,101 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:01,102 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:01,315 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:01,315 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:01,487 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:01,487 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:01,502 - INFO - Frame 4992 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:01,655 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:01,656 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:01,829 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:01,832 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:01,995 - INFO - Frame 4994 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:01,998 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:01,999 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:02,167 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:02,168 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:02,343 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:02,344 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:02,359 - INFO - Frame 4996 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:02,512 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:02,513 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:02,688 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:02,688 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:02,852 - INFO - Frame 4998 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:02,855 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:02,856 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:03,020 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:03,024 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:03,185 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:03,186 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:03,199 - INFO - Frame 5000 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:03,349 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:03,350 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:03,526 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:03,526 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:03,697 - INFO - Frame 5002 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:03,701 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:03,701 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:03,867 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:03,868 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:04,032 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:04,033 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:04,047 - INFO - Frame 5004 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:04,196 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:04,197 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:04,382 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:04,382 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:04,422 - INFO - Frame 5006 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:04,558 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:04,558 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:04,723 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:04,723 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:04,900 - INFO - Frame 5008 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:04,905 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:04,905 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:05,075 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:05,079 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:05,255 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:05,257 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:05,270 - INFO - Frame 5010 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:05,428 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:05,428 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:05,626 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:05,626 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:05,801 - INFO - Frame 5012 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:05,803 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:05,804 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:05,981 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:05,987 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:06,167 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:06,169 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:06,182 - INFO - Frame 5014 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:06,349 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:06,350 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:06,518 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:06,519 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:06,693 - INFO - Frame 5016 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:06,695 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:06,696 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:06,866 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:06,867 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:07,029 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:07,029 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:07,042 - INFO - Frame 5018 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:07,192 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:07,192 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:07,360 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:07,360 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:07,397 - INFO - Frame 5020 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:07,534 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:07,536 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:07,701 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:07,701 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:07,873 - INFO - Frame 5022 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:07,876 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:07,879 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:08,036 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:08,039 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:08,221 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:08,224 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:08,236 - INFO - Frame 5024 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:08,376 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:08,376 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:08,538 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:08,540 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:08,691 - INFO - Frame 5026 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:08,694 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:08,695 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:08,866 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:08,868 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:09,041 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:09,045 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:09,058 - INFO - Frame 5028 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:09,201 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:09,201 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:09,375 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:09,377 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:09,554 - INFO - Frame 5030 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:09,558 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:09,558 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:09,725 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:09,725 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:09,900 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:09,901 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:09,914 - INFO - Frame 5032 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:10,068 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:10,068 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:10,234 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:10,234 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:10,398 - INFO - Frame 5034 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:10,402 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:10,403 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:10,571 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:10,571 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:10,731 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:10,731 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:10,745 - INFO - Frame 5036 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:10,900 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:10,900 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:11,074 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:11,076 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:11,246 - INFO - Frame 5038 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:11,250 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:11,250 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:11,408 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:11,409 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:11,573 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:11,573 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:11,586 - INFO - Frame 5040 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:11,734 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:11,736 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:11,906 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:11,907 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:12,072 - INFO - Frame 5042 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:12,075 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:12,076 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:12,237 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:12,239 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:12,405 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:12,406 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:12,419 - INFO - Frame 5044 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:12,575 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:12,576 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:12,748 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:12,750 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:12,913 - INFO - Frame 5046 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:12,916 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:12,919 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:13,093 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:13,093 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:13,268 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:13,268 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:13,281 - INFO - Frame 5048 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:13,426 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:13,426 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:13,600 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:13,601 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:13,758 - INFO - Frame 5050 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:13,759 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:13,762 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:13,923 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:13,926 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:14,083 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:14,084 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:14,098 - INFO - Frame 5052 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:14,259 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:14,260 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:14,440 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:14,441 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:14,611 - INFO - Frame 5054 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:14,614 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:14,615 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:14,792 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:14,792 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:14,987 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:14,987 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:15,002 - INFO - Frame 5056 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:15,153 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:15,157 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:15,328 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:15,329 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:15,493 - INFO - Frame 5058 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:15,496 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:15,497 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:15,662 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:15,663 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:15,826 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:15,829 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:15,843 - INFO - Frame 5060 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:15,995 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:15,995 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:16,174 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:16,174 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:16,341 - INFO - Frame 5062 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:16,342 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:16,344 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:16,503 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:16,504 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:16,672 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:16,672 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:16,686 - INFO - Frame 5064 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:16,837 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:16,837 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:17,017 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:17,017 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:17,183 - INFO - Frame 5066 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:17,184 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:17,185 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:17,349 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:17,351 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:17,520 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:17,521 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:17,535 - INFO - Frame 5068 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:17,689 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:17,689 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:17,862 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:17,863 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:18,029 - INFO - Frame 5070 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:18,031 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:18,032 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:18,189 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:18,196 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:18,387 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:18,391 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:18,401 - INFO - Frame 5072 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:18,537 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:18,537 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:18,713 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:18,719 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:18,886 - INFO - Frame 5074 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:18,888 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:18,889 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:19,061 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:19,063 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:19,230 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:19,230 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:19,248 - INFO - Frame 5076 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:19,407 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:19,408 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:19,598 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:19,599 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:19,772 - INFO - Frame 5078 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:19,774 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:19,775 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:19,934 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:19,935 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:20,111 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:20,112 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:20,125 - INFO - Frame 5080 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:20,281 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:20,281 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:20,465 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:20,465 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:20,632 - INFO - Frame 5082 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:20,635 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:20,636 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:20,799 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:20,799 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:20,971 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:20,971 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:20,984 - INFO - Frame 5084 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:21,137 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:21,138 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:21,310 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:21,311 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:21,347 - INFO - Frame 5086 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:21,480 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:21,481 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:21,659 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:21,659 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:21,811 - INFO - Frame 5088 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:21,814 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:21,814 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:21,981 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:21,982 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:22,159 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:22,159 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:22,173 - INFO - Frame 5090 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:22,320 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:22,321 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:22,490 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:22,491 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:22,665 - INFO - Frame 5092 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:22,666 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:22,669 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:22,834 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:22,835 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:23,005 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:23,007 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:23,021 - INFO - Frame 5094 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:23,166 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:23,166 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:23,347 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:23,347 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:23,383 - INFO - Frame 5096 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:23,518 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:23,521 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:23,682 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:23,683 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:23,851 - INFO - Frame 5098 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:23,853 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:23,856 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:24,021 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:24,023 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:24,195 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:24,195 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:24,361 - INFO - Frame 5100 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:24,361 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:24,362 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:24,540 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:24,543 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:24,717 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:24,718 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:24,731 - INFO - Frame 5102 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:24,889 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:24,889 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:25,071 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:25,071 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:25,224 - INFO - Frame 5104 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:25,228 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:25,229 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:25,384 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:25,385 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:25,533 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:25,536 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:25,547 - INFO - Frame 5106 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:25,700 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:25,700 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:25,870 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:25,871 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:26,034 - INFO - Frame 5108 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:26,035 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:26,035 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:26,214 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:26,215 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:26,391 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:26,391 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:26,406 - INFO - Frame 5110 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:26,553 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:26,554 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:26,715 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:26,720 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:26,874 - INFO - Frame 5112 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:26,876 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:26,878 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:27,046 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:27,053 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:27,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:27,221 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:27,234 - INFO - Frame 5114 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:27,387 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:27,387 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:27,557 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:27,557 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:27,706 - INFO - Frame 5116 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:27,709 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:27,709 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:27,889 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:27,891 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:28,066 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:28,066 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:28,079 - INFO - Frame 5118 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:28,236 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:28,237 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:28,408 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:28,409 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:28,443 - INFO - Frame 5120 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:28,581 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:28,581 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:28,743 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:28,746 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:28,914 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:28,914 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:28,936 - INFO - Frame 5122 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:29,088 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:29,088 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:29,253 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:29,253 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:29,430 - INFO - Frame 5124 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:29,431 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:29,431 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:29,639 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:29,640 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:29,811 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:29,811 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:29,831 - INFO - Frame 5126 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:29,980 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:29,981 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:30,152 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:30,153 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:30,315 - INFO - Frame 5128 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:30,316 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:30,317 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:30,480 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:30,486 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:30,657 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:30,657 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:30,677 - INFO - Frame 5130 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:30,819 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:30,824 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:30,995 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:30,996 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:31,168 - INFO - Frame 5132 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:31,169 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:31,171 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:31,342 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:31,343 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:31,514 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:31,518 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:31,687 - INFO - Frame 5134 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:31,689 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:31,690 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:31,857 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:31,857 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:32,034 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:32,035 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:32,054 - INFO - Frame 5136 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:32,202 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:32,202 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:32,375 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:32,376 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:32,553 - INFO - Frame 5138 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:32,558 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:32,558 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:32,725 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:32,726 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:32,915 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:32,915 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:32,935 - INFO - Frame 5140 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:33,094 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:33,095 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:33,276 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:33,280 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:33,454 - INFO - Frame 5142 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:33,460 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:33,461 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:33,637 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:33,637 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:33,820 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:33,820 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:33,837 - INFO - Frame 5144 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:33,991 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:33,992 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:34,163 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:34,164 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:34,332 - INFO - Frame 5146 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:34,334 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:34,337 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:34,509 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:34,510 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:34,682 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:34,682 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:34,699 - INFO - Frame 5148 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:34,846 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:34,846 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:35,029 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:35,029 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:35,194 - INFO - Frame 5150 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:35,198 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:35,198 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:35,362 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:35,363 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:35,538 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:35,538 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:35,559 - INFO - Frame 5152 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:35,697 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:35,698 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:35,872 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:35,872 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:36,045 - INFO - Frame 5154 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:36,047 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:36,047 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:36,218 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:36,220 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:36,392 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:36,393 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:36,411 - INFO - Frame 5156 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:36,552 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:36,553 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:36,728 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:36,729 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:36,896 - INFO - Frame 5158 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:36,897 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:36,897 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:37,068 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:37,070 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:37,252 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:37,254 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:37,273 - INFO - Frame 5160 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:37,438 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:37,439 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:37,613 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:37,613 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:37,769 - INFO - Frame 5162 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:37,770 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:37,773 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:37,938 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:37,938 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:38,108 - INFO - Frame 5164 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:38,110 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:38,111 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:38,281 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:38,282 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:38,448 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:38,450 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:38,472 - INFO - Frame 5166 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:38,613 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:38,613 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:38,786 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:38,787 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:38,950 - INFO - Frame 5168 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:38,953 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:38,956 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:39,113 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:39,114 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:39,293 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:39,295 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:39,314 - INFO - Frame 5170 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:39,471 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:39,472 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:39,665 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:39,665 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:39,837 - INFO - Frame 5172 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:39,840 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:39,841 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:40,023 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:40,031 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:40,206 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:40,206 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:40,227 - INFO - Frame 5174 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:40,378 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:40,380 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:40,550 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:40,554 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:40,715 - INFO - Frame 5176 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:40,719 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:40,720 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:40,887 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:40,889 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:41,055 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:41,059 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:41,073 - INFO - Frame 5178 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:41,233 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:41,233 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:41,403 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:41,403 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:41,565 - INFO - Frame 5180 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:41,568 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:41,569 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:41,738 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:41,739 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:41,911 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:41,916 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:41,932 - INFO - Frame 5182 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:42,084 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:42,084 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:42,257 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:42,257 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:42,408 - INFO - Frame 5184 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:42,411 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:42,415 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:42,580 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:42,580 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:42,745 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:42,746 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:42,766 - INFO - Frame 5186 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:42,926 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:42,928 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:43,094 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:43,097 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:43,252 - INFO - Frame 5188 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:43,255 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:43,256 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:43,417 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:43,418 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:43,587 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:43,592 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:43,611 - INFO - Frame 5190 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:43,758 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:43,759 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:43,926 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:43,926 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:44,090 - INFO - Frame 5192 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:44,093 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:44,094 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:44,261 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:44,261 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:44,442 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:44,442 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:44,462 - INFO - Frame 5194 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:44,602 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:44,604 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:44,794 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:44,795 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:44,959 - INFO - Frame 5196 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:44,963 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:44,964 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:45,135 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:45,135 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:45,310 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:45,310 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:45,332 - INFO - Frame 5198 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:45,504 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:45,504 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:45,678 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:45,679 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:45,844 - INFO - Frame 5200 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:45,850 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:45,850 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:46,020 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:46,021 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:46,187 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:46,187 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:46,209 - INFO - Frame 5202 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:46,351 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:46,351 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:46,517 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:46,520 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:46,684 - INFO - Frame 5204 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:46,684 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:46,685 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:46,848 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:46,855 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:47,030 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:47,030 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:47,051 - INFO - Frame 5206 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:47,188 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:47,188 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:47,369 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:47,369 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:47,527 - INFO - Frame 5208 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:47,531 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:47,531 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:47,690 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:47,693 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:47,863 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:47,864 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:47,883 - INFO - Frame 5210 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:48,019 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:48,020 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:48,192 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:48,192 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:48,359 - INFO - Frame 5212 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:48,362 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:48,363 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:48,536 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:48,536 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:48,694 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:48,694 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:48,711 - INFO - Frame 5214 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:48,851 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:48,853 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:49,031 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:49,033 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:49,194 - INFO - Frame 5216 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:49,197 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:49,198 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:49,364 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:49,365 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:49,547 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:49,547 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:49,566 - INFO - Frame 5218 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:49,722 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:49,722 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:49,909 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:49,912 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:50,096 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:50,096 - INFO - Frame 5220 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:50,097 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:50,259 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:50,259 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:50,431 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:50,435 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:50,602 - INFO - Frame 5222 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:50,603 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:50,604 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:50,767 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:50,767 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:50,937 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:50,939 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:50,956 - INFO - Frame 5224 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:51,107 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:51,109 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:51,277 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:51,278 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:51,435 - INFO - Frame 5226 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:51,438 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:51,438 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:51,600 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:51,600 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:51,763 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:51,763 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:51,784 - INFO - Frame 5228 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:51,937 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:51,938 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:52,106 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:52,110 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:52,265 - INFO - Frame 5230 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:52,267 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:52,270 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:52,433 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:52,433 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:52,614 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:52,617 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:52,631 - INFO - Frame 5232 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:52,770 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:52,770 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:52,941 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:52,941 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:53,104 - INFO - Frame 5234 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:53,108 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:53,109 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:53,277 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:53,277 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:53,436 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:53,437 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:53,459 - INFO - Frame 5236 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:53,606 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:53,606 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:53,785 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:53,786 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:53,944 - INFO - Frame 5238 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:53,945 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:53,946 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:54,123 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:54,124 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:54,294 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:54,294 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:54,317 - INFO - Frame 5240 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:54,470 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:54,470 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:54,648 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:54,648 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:54,805 - INFO - Frame 5242 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:54,809 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:54,809 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:54,972 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:54,973 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:55,142 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:55,143 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:55,162 - INFO - Frame 5244 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:55,306 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:55,307 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:55,485 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:55,485 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:55,658 - INFO - Frame 5246 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:55,660 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:55,660 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:55,826 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:55,827 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:55,988 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:55,988 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:56,006 - INFO - Frame 5248 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:56,159 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:56,159 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:56,334 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:56,335 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:56,509 - INFO - Frame 5250 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:56,512 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:56,515 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:56,670 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:56,671 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:56,830 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:56,835 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:56,853 - INFO - Frame 5252 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:56,991 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:56,991 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:57,152 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:57,153 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:57,316 - INFO - Frame 5254 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:57,321 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:57,321 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:57,482 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:57,482 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:57,650 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:57,650 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:57,666 - INFO - Frame 5256 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:57,823 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:57,823 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:57,994 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:57,995 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:58,157 - INFO - Frame 5258 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:58,160 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:58,160 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:58,322 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:58,322 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:58,496 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:58,497 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:58,516 - INFO - Frame 5260 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:58,665 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:58,665 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:58,835 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:58,836 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:58,991 - INFO - Frame 5262 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:58,994 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:58,994 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:59,163 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:59,164 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:59,339 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:59,341 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:59,354 - INFO - Frame 5264 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:59,507 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:59,511 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:59,682 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:59,683 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:59,854 - INFO - Frame 5266 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:55:59,855 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:55:59,858 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:00,022 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:00,023 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:00,197 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:00,198 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:00,217 - INFO - Frame 5268 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:00,364 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:00,365 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:00,546 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:00,547 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:00,704 - INFO - Frame 5270 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:00,708 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:00,708 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:00,875 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:00,876 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:01,055 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:01,055 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:01,075 - INFO - Frame 5272 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:01,234 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:01,235 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:01,411 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:01,413 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:01,586 - INFO - Frame 5274 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:01,589 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:01,590 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:01,760 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:01,760 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:01,946 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:01,949 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:01,968 - INFO - Frame 5276 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:02,125 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:02,125 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:02,288 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:02,289 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:02,458 - INFO - Frame 5278 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:02,462 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:02,467 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:02,641 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:02,642 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:02,831 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:02,831 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:02,850 - INFO - Frame 5280 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:02,992 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:02,997 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:03,173 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:03,175 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:03,344 - INFO - Frame 5282 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:03,346 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:03,346 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:03,519 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:03,520 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:03,685 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:03,685 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:03,843 - INFO - Frame 5284 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:03,847 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:03,847 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:04,011 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:04,013 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:04,175 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:04,178 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:04,195 - INFO - Frame 5286 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:04,343 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:04,343 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:04,515 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:04,515 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:04,677 - INFO - Frame 5288 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:04,678 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:04,678 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:04,840 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:04,841 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:05,023 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:05,023 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:05,043 - INFO - Frame 5290 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:05,176 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:05,176 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:05,349 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:05,349 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:05,520 - INFO - Frame 5292 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:05,523 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:05,524 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:05,692 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:05,692 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:05,860 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:05,860 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:05,880 - INFO - Frame 5294 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:06,028 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:06,028 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:06,200 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:06,201 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:06,362 - INFO - Frame 5296 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:06,365 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:06,366 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:06,545 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:06,545 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:06,730 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:06,730 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:06,749 - INFO - Frame 5298 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:06,919 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:06,919 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:07,099 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:07,103 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:07,275 - INFO - Frame 5300 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:07,277 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:07,278 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:07,454 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:07,455 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:07,630 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:07,630 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:07,649 - INFO - Frame 5302 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:07,798 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:07,798 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:07,974 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:07,974 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:08,140 - INFO - Frame 5304 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:08,140 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:08,142 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:08,306 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:08,306 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:08,463 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:08,466 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:08,478 - INFO - Frame 5306 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:08,637 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:08,637 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:08,806 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:08,807 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:08,962 - INFO - Frame 5308 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:08,966 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:08,967 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:09,127 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:09,127 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:09,296 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:09,297 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:09,311 - INFO - Frame 5310 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:09,468 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:09,472 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:09,641 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:09,641 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:09,803 - INFO - Frame 5312 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:09,806 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:09,807 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:09,962 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:09,966 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:10,133 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:10,134 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:10,146 - INFO - Frame 5314 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:10,309 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:10,310 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:10,480 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:10,481 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:10,650 - INFO - Frame 5316 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:10,651 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:10,655 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:10,810 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:10,816 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:10,978 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:10,978 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:11,075 - INFO - Frame 5318 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:11,135 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:11,135 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:11,289 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:11,289 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:11,469 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:11,471 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:11,486 - INFO - Frame 5320 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:11,642 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:11,642 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:11,831 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:11,836 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:12,013 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:12,014 - INFO - Frame 5322 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:12,014 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:12,191 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:12,191 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:12,361 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:12,362 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:12,375 - INFO - Frame 5324 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:12,538 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:12,538 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:12,709 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:12,709 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:12,874 - INFO - Frame 5326 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:12,874 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:12,874 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:13,040 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:13,041 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:13,211 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:13,211 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:13,225 - INFO - Frame 5328 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:13,380 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:13,380 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:13,554 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:13,559 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:13,716 - INFO - Frame 5330 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:13,717 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:13,721 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:13,888 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:13,888 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:14,069 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:14,070 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:14,083 - INFO - Frame 5332 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:14,238 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:14,238 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:14,416 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:14,417 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:14,576 - INFO - Frame 5334 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:14,579 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:14,581 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:14,740 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:14,741 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:14,913 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:14,913 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:14,929 - INFO - Frame 5336 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:15,089 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:15,093 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:15,266 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:15,271 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:15,439 - INFO - Frame 5338 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:15,442 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:15,443 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:15,612 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:15,615 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:15,798 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:15,798 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:15,813 - INFO - Frame 5340 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:15,977 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:15,977 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:16,159 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:16,161 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:16,335 - INFO - Frame 5342 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:16,336 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:16,337 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:16,492 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:16,493 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:16,653 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:16,656 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:16,671 - INFO - Frame 5344 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:16,829 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:16,829 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:16,993 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:16,993 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:17,154 - INFO - Frame 5346 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:17,158 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:17,158 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:17,326 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:17,327 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:17,502 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:17,504 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:17,517 - INFO - Frame 5348 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:17,678 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:17,679 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:17,861 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:17,862 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:18,028 - INFO - Frame 5350 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:18,032 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:18,032 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:18,193 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:18,194 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:18,357 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:18,357 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:18,372 - INFO - Frame 5352 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:18,520 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:18,521 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:18,698 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:18,698 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:18,861 - INFO - Frame 5354 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:18,864 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:18,864 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:19,038 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:19,039 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:19,190 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:19,191 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:19,204 - INFO - Frame 5356 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:19,355 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:19,355 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:19,534 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:19,535 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:19,723 - INFO - Frame 5358 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:19,727 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:19,728 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:19,911 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:19,912 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:20,087 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:20,088 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:20,102 - INFO - Frame 5360 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:20,261 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:20,261 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:20,435 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:20,436 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:20,613 - INFO - Frame 5362 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:20,615 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:20,615 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:20,782 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:20,783 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:20,949 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:20,951 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:20,964 - INFO - Frame 5364 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:21,127 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:21,127 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:21,301 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:21,302 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:21,474 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:21,475 - INFO - Frame 5366 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:21,476 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:21,643 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:21,643 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:21,807 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:21,807 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:21,820 - INFO - Frame 5368 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:21,953 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:21,953 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:22,116 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:22,117 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:22,286 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:22,286 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:22,301 - INFO - Frame 5370 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:22,451 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:22,452 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:22,643 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:22,643 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:22,809 - INFO - Frame 5372 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:22,814 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:22,815 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:22,977 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:22,977 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:23,147 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:23,147 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:23,165 - INFO - Frame 5374 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:23,316 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:23,316 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:23,490 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:23,490 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:23,659 - INFO - Frame 5376 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:23,660 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:23,661 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:23,832 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:23,832 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:24,003 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:24,003 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:24,015 - INFO - Frame 5378 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:24,181 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:24,181 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:24,364 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:24,367 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:24,542 - INFO - Frame 5380 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:24,546 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:24,546 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:24,711 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:24,711 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:24,875 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:24,875 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:24,889 - INFO - Frame 5382 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:25,041 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:25,041 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:25,208 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:25,208 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:25,373 - INFO - Frame 5384 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:25,375 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:25,379 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:25,542 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:25,542 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:25,710 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:25,710 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:25,742 - INFO - Frame 5386 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:25,888 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:25,888 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:26,062 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:26,065 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:26,222 - INFO - Frame 5388 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:26,226 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:26,226 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:26,388 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:26,388 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:26,565 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:26,565 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:26,578 - INFO - Frame 5390 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:26,735 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:26,735 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:26,904 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:26,906 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:27,069 - INFO - Frame 5392 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:27,071 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:27,072 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:27,235 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:27,237 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:27,406 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:27,406 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:27,420 - INFO - Frame 5394 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:27,573 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:27,573 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:27,748 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:27,752 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:27,905 - INFO - Frame 5396 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:27,909 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:27,909 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:28,067 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:28,070 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:28,232 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:28,234 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:28,247 - INFO - Frame 5398 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:28,396 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:28,396 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:28,571 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:28,571 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:28,609 - INFO - Frame 5400 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:28,748 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:28,748 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:28,917 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:28,918 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:29,088 - INFO - Frame 5402 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:29,093 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:29,094 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:29,257 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:29,257 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:29,429 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:29,430 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:29,460 - INFO - Frame 5404 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:29,606 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:29,607 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:29,778 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:29,779 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:29,953 - INFO - Frame 5406 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:29,958 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:29,958 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:30,122 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:30,122 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:30,295 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:30,297 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:30,328 - INFO - Frame 5408 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:30,471 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:30,471 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:30,648 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:30,649 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:30,821 - INFO - Frame 5410 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:30,825 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:30,825 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:30,992 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:30,993 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:31,165 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:31,169 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:31,197 - INFO - Frame 5412 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:31,329 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:31,331 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:31,504 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:31,505 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:31,541 - INFO - Frame 5414 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:31,673 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:31,673 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:31,843 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:31,843 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:32,009 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:32,010 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:32,027 - INFO - Frame 5416 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:32,176 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:32,176 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:32,352 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:32,353 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:32,531 - INFO - Frame 5418 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:32,535 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:32,537 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:32,713 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:32,713 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:32,896 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:32,900 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:32,912 - INFO - Frame 5420 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:33,085 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:33,086 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:33,252 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:33,257 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:33,418 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:33,419 - INFO - Frame 5422 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:33,421 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:33,591 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:33,591 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:33,757 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:33,757 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:33,921 - INFO - Frame 5424 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:33,924 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:33,924 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:34,084 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:34,084 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:34,249 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:34,250 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:34,262 - INFO - Frame 5426 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:34,428 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:34,429 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:34,598 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:34,603 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:34,767 - INFO - Frame 5428 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:34,771 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:34,771 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:34,951 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:34,951 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:35,134 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:35,136 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:35,147 - INFO - Frame 5430 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:35,301 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:35,303 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:35,468 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:35,469 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:35,674 - INFO - Frame 5432 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:35,675 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:35,676 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:35,845 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:35,847 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:36,017 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:36,023 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:36,032 - INFO - Frame 5434 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:36,196 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:36,197 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:36,372 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:36,373 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:36,540 - INFO - Frame 5436 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:36,542 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:36,542 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:36,712 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:36,714 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:36,880 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:36,880 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:36,894 - INFO - Frame 5438 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:37,049 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:37,051 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:37,244 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:37,245 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:37,410 - INFO - Frame 5440 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:37,412 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:37,413 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:37,585 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:37,586 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:37,757 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:37,758 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:37,772 - INFO - Frame 5442 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:37,920 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:37,920 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:38,097 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:38,097 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:38,274 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:38,275 - INFO - Frame 5444 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:38,275 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:38,433 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:38,435 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:38,592 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:38,593 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:38,623 - INFO - Frame 5446 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:38,767 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:38,767 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:38,936 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:38,938 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:39,105 - INFO - Frame 5448 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:39,109 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:39,109 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:39,282 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:39,283 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:39,461 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:39,462 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:39,476 - INFO - Frame 5450 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:39,626 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:39,626 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:39,795 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:39,797 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:39,953 - INFO - Frame 5452 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:39,957 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:39,958 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:40,110 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:40,110 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:40,280 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:40,280 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:40,294 - INFO - Frame 5454 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:40,448 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:40,449 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:40,629 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:40,630 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:40,810 - INFO - Frame 5456 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:40,811 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:40,812 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:40,985 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:40,985 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:41,158 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:41,158 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:41,191 - INFO - Frame 5458 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:41,321 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:41,321 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:41,499 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:41,499 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:41,671 - INFO - Frame 5460 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:41,674 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:41,674 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:41,846 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:41,847 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:42,038 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:42,038 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:42,053 - INFO - Frame 5462 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:42,206 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:42,206 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:42,379 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:42,380 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:42,553 - INFO - Frame 5464 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:42,554 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:42,554 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:42,718 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:42,718 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:42,892 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:42,893 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:42,906 - INFO - Frame 5466 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:43,060 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:43,060 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:43,228 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:43,229 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:43,400 - INFO - Frame 5468 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:43,401 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:43,402 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:43,573 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:43,573 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:43,751 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:43,752 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:43,766 - INFO - Frame 5470 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:43,921 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:43,921 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:44,102 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:44,102 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:44,269 - INFO - Frame 5472 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:44,270 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:44,272 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:44,436 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:44,436 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:44,610 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:44,611 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:44,770 - INFO - Frame 5474 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:44,774 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:44,776 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:44,940 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:44,945 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:45,117 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:45,118 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:45,135 - INFO - Frame 5476 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:45,282 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:45,282 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:45,457 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:45,457 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:45,623 - INFO - Frame 5478 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:45,627 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:45,628 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:45,787 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:45,787 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:45,959 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:45,959 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:45,973 - INFO - Frame 5480 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:46,133 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:46,133 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:46,306 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:46,306 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:46,467 - INFO - Frame 5482 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:46,472 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:46,473 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:46,639 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:46,644 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:46,814 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:46,814 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:46,829 - INFO - Frame 5484 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:46,986 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:46,989 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:47,161 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:47,161 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:47,331 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:47,331 - INFO - Frame 5486 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:47,333 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:47,500 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:47,507 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:47,680 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:47,683 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:47,695 - INFO - Frame 5488 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:47,853 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:47,854 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:48,036 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:48,038 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:48,186 - INFO - Frame 5490 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:48,189 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:48,189 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:48,356 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:48,357 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:48,526 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:48,526 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:48,541 - INFO - Frame 5492 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:48,688 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:48,688 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:48,854 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:48,855 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:49,016 - INFO - Frame 5494 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:49,019 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:49,020 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:49,178 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:49,178 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:49,346 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:49,349 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:49,361 - INFO - Frame 5496 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:49,519 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:49,520 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:49,695 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:49,697 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:49,861 - INFO - Frame 5498 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:49,865 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:49,865 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:50,044 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:50,044 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:50,210 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:50,210 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:50,224 - INFO - Frame 5500 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:50,374 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:50,374 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:50,558 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:50,558 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:50,714 - INFO - Frame 5502 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:50,718 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:50,718 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:50,889 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:50,889 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:51,061 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:51,061 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:51,076 - INFO - Frame 5504 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:51,233 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:51,234 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:51,408 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:51,413 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:51,582 - INFO - Frame 5506 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:51,582 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:51,584 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:51,744 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:51,744 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:51,918 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:51,919 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:51,948 - INFO - Frame 5508 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:52,090 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:52,094 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:52,267 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:52,270 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:52,423 - INFO - Frame 5510 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:52,426 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:52,429 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:52,600 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:52,604 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:52,824 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:52,825 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:52,986 - INFO - Frame 5512 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:52,988 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:52,989 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:53,161 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:53,164 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:53,333 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:53,333 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:53,346 - INFO - Frame 5514 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:53,503 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:53,503 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:53,672 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:53,672 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:53,843 - INFO - Frame 5516 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:53,846 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:53,849 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:54,015 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:54,021 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:54,192 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:54,194 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:54,210 - INFO - Frame 5518 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:54,364 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:54,364 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:54,546 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:54,546 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:54,712 - INFO - Frame 5520 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:54,713 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:54,714 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:54,884 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:54,885 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:55,052 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:55,052 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:55,083 - INFO - Frame 5522 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:55,229 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:55,229 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:55,403 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:55,404 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:55,564 - INFO - Frame 5524 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:55,568 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:55,568 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:55,721 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:55,722 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:55,895 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:55,895 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:55,909 - INFO - Frame 5526 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:56,060 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:56,061 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:56,237 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:56,238 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:56,413 - INFO - Frame 5528 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:56,417 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:56,418 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:56,579 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:56,581 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:56,746 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:56,746 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:56,759 - INFO - Frame 5530 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:56,919 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:56,920 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:57,101 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:57,102 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:57,268 - INFO - Frame 5532 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:57,269 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:57,269 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:57,437 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:57,438 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:57,611 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:57,611 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:57,625 - INFO - Frame 5534 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:57,778 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:57,782 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:57,972 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:57,972 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:58,142 - INFO - Frame 5536 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:58,145 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:58,145 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:58,322 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:58,322 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:58,490 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:58,490 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:58,504 - INFO - Frame 5538 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:58,669 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:58,669 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:58,845 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:58,846 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:59,022 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:59,022 - INFO - Frame 5540 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:59,023 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:59,189 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:59,190 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:59,367 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:59,368 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:59,382 - INFO - Frame 5542 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:59,557 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:59,558 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:59,709 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:59,709 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:59,872 - INFO - Frame 5544 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:56:59,872 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:56:59,872 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:00,038 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:00,040 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:00,209 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:00,210 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:00,222 - INFO - Frame 5546 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:57:00,377 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:00,378 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:00,556 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:00,556 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:00,722 - INFO - Frame 5548 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:57:00,725 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:00,726 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:00,894 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:00,897 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:01,061 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:01,062 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:01,094 - INFO - Frame 5550 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:57:01,230 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:01,231 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:01,400 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:01,402 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:01,561 - INFO - Frame 5552 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:57:01,562 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:01,564 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:01,723 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:01,723 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:01,891 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:01,892 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:01,908 - INFO - Frame 5554 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:57:02,060 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:02,061 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:02,243 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:02,243 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:02,421 - INFO - Frame 5556 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:57:02,424 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:02,425 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:02,595 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:02,596 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:02,783 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:02,784 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:02,797 - INFO - Frame 5558 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:57:02,957 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:02,958 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:03,131 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:03,132 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:03,299 - INFO - Frame 5560 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:57:03,303 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:03,305 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:03,477 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:03,478 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:03,646 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:03,646 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:03,662 - INFO - Frame 5562 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:57:03,819 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:03,819 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:04,000 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:04,003 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:04,172 - INFO - Frame 5564 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:57:04,174 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:04,176 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:04,338 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:04,338 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:04,511 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:04,512 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:04,527 - INFO - Frame 5566 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:57:04,681 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:04,681 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:04,856 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:04,856 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:05,028 - INFO - Frame 5568 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:57:05,030 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:05,030 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:05,196 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:05,197 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:05,367 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:05,369 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:05,527 - INFO - Frame 5570 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:57:05,531 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:05,531 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:05,698 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:05,699 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:05,874 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:05,874 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:05,892 - INFO - Frame 5572 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:57:06,045 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:06,046 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:06,223 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:06,224 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:06,390 - INFO - Frame 5574 | PERCLOS: 0.08 | Yaw: 2.0° | Alerts: 0
2025-11-24 17:57:06,393 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:06,396 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:06,564 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:06,566 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:06,750 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:06,750 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:06,764 - INFO - Frame 5576 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 17:57:06,927 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:06,928 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:07,127 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:07,128 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:07,290 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:07,294 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:07,311 - INFO - Frame 5578 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 17:57:07,453 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:07,453 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:07,670 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:07,688 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:07,866 - INFO - Frame 5580 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 0
2025-11-24 17:57:07,868 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:07,869 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:08,034 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:08,034 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:08,222 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:08,223 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:08,239 - INFO - Frame 5582 | PERCLOS: 0.00 | Yaw: 8.7° | Alerts: 0
2025-11-24 17:57:08,386 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:08,387 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:08,561 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:08,561 - ERROR - ❌ No camera found! Trying to use video file or test pattern...
2025-11-24 17:57:08,673 - INFO - Frame 5584 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 0
2025-11-24 18:02:10,073 - INFO - Loading models...
2025-11-24 18:02:10,101 - INFO - ✓ YOLO ONNX loaded
2025-11-24 18:02:10,140 - INFO - ✓ MediaPipe Face Mesh loaded
2025-11-24 18:02:10,147 - INFO - ✓ MediaPipe Pose loaded (for smoke & seatbelt)
2025-11-24 18:04:26,992 - INFO - Loading models...
2025-11-24 18:04:27,015 - INFO - ✓ YOLO ONNX loaded
2025-11-24 18:04:27,050 - INFO - ✓ MediaPipe Face Mesh loaded
2025-11-24 18:04:27,057 - INFO - ✓ MediaPipe Pose loaded (for smoke & seatbelt)
2025-11-24 18:04:27,060 - INFO - Video thread started with source: Camera
2025-11-24 18:04:27,177 - INFO - ✓ Camera 0 opened successfully
2025-11-24 18:04:27,687 - INFO - Frame 0 | PERCLOS: 0.30 | Yaw: 3.9° | Alerts: 1
2025-11-24 18:04:27,888 - INFO - Frame 2 | PERCLOS: 0.31 | Yaw: 3.8° | Alerts: 2
2025-11-24 18:04:28,080 - INFO - Frame 4 | PERCLOS: 0.10 | Yaw: 4.0° | Alerts: 1
2025-11-24 18:04:28,398 - INFO - Frame 6 | PERCLOS: 0.09 | Yaw: 3.9° | Alerts: 1
2025-11-24 18:04:28,619 - INFO - Frame 8 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 18:04:28,832 - INFO - Frame 10 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 18:04:29,115 - INFO - Frame 12 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 1
2025-11-24 18:04:29,325 - INFO - Frame 14 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 1
2025-11-24 18:04:29,540 - INFO - Frame 16 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 18:04:29,819 - INFO - Frame 18 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:04:30,025 - INFO - Frame 20 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 1
2025-11-24 18:04:30,239 - INFO - Frame 22 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 1
2025-11-24 18:04:30,523 - INFO - Frame 24 | PERCLOS: 0.00 | Yaw: 5.1° | Alerts: 1
2025-11-24 18:04:30,739 - INFO - Frame 26 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-24 18:04:30,950 - INFO - Frame 28 | PERCLOS: 0.00 | Yaw: 5.2° | Alerts: 1
2025-11-24 18:04:31,234 - INFO - Frame 30 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 18:04:31,457 - INFO - Frame 32 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 18:04:31,664 - INFO - Frame 34 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 1
2025-11-24 18:04:31,948 - INFO - Frame 36 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 1
2025-11-24 18:04:32,177 - INFO - Frame 38 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 1
2025-11-24 18:04:32,387 - INFO - Frame 40 | PERCLOS: 0.00 | Yaw: -0.3° | Alerts: 1
2025-11-24 18:04:32,690 - INFO - Frame 42 | PERCLOS: 0.00 | Yaw: -1.2° | Alerts: 1
2025-11-24 18:04:32,909 - INFO - Frame 44 | PERCLOS: 0.00 | Yaw: -2.2° | Alerts: 1
2025-11-24 18:04:33,116 - INFO - Frame 46 | PERCLOS: 0.00 | Yaw: -2.8° | Alerts: 1
2025-11-24 18:04:33,408 - INFO - Frame 48 | PERCLOS: 0.00 | Yaw: -2.5° | Alerts: 1
2025-11-24 18:04:33,625 - INFO - Frame 50 | PERCLOS: 0.00 | Yaw: -1.7° | Alerts: 1
2025-11-24 18:04:33,839 - INFO - Frame 52 | PERCLOS: 0.00 | Yaw: -1.3° | Alerts: 1
2025-11-24 18:04:34,198 - INFO - Frame 54 | PERCLOS: 0.00 | Yaw: -0.8° | Alerts: 1
2025-11-24 18:04:34,417 - INFO - Frame 56 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 1
2025-11-24 18:04:34,640 - INFO - Frame 58 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 1
2025-11-24 18:04:34,969 - INFO - Frame 60 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 1
2025-11-24 18:04:35,189 - INFO - Frame 62 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 1
2025-11-24 18:04:35,406 - INFO - Frame 64 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 1
2025-11-24 18:04:35,721 - INFO - Frame 66 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 1
2025-11-24 18:04:35,936 - INFO - Frame 68 | PERCLOS: 0.00 | Yaw: -0.2° | Alerts: 1
2025-11-24 18:04:36,142 - INFO - Frame 70 | PERCLOS: 0.00 | Yaw: 0.2° | Alerts: 1
2025-11-24 18:04:36,451 - INFO - Frame 72 | PERCLOS: 0.43 | Yaw: -0.2° | Alerts: 2
2025-11-24 18:04:36,670 - INFO - Frame 74 | PERCLOS: 0.00 | Yaw: -0.3° | Alerts: 1
2025-11-24 18:04:36,897 - INFO - Frame 76 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 1
2025-11-24 18:04:37,198 - INFO - Frame 78 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 1
2025-11-24 18:04:37,426 - INFO - Frame 80 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 1
2025-11-24 18:04:37,653 - INFO - Frame 82 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 1
2025-11-24 18:04:37,955 - INFO - Frame 84 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 1
2025-11-24 18:04:38,180 - INFO - Frame 86 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 1
2025-11-24 18:04:38,393 - INFO - Frame 88 | PERCLOS: 0.31 | Yaw: -0.4° | Alerts: 2
2025-11-24 18:04:38,700 - INFO - Frame 90 | PERCLOS: 0.00 | Yaw: -0.2° | Alerts: 1
2025-11-24 18:04:38,913 - INFO - Frame 92 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 1
2025-11-24 18:04:39,133 - INFO - Frame 94 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 1
2025-11-24 18:04:39,454 - INFO - Frame 96 | PERCLOS: 0.00 | Yaw: 5.1° | Alerts: 1
2025-11-24 18:04:39,674 - INFO - Frame 98 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 1
2025-11-24 18:04:39,962 - INFO - Frame 100 | PERCLOS: 0.00 | Yaw: 5.9° | Alerts: 1
2025-11-24 18:04:40,271 - INFO - Frame 102 | PERCLOS: 0.00 | Yaw: 6.2° | Alerts: 1
2025-11-24 18:04:40,504 - INFO - Frame 104 | PERCLOS: 0.00 | Yaw: 6.5° | Alerts: 1
2025-11-24 18:04:40,713 - INFO - Frame 106 | PERCLOS: 0.00 | Yaw: 6.6° | Alerts: 1
2025-11-24 18:04:41,021 - INFO - Frame 108 | PERCLOS: 0.00 | Yaw: 6.9° | Alerts: 1
2025-11-24 18:04:41,237 - INFO - Frame 110 | PERCLOS: 0.00 | Yaw: 7.0° | Alerts: 1
2025-11-24 18:04:41,434 - INFO - Frame 112 | PERCLOS: 0.00 | Yaw: 7.3° | Alerts: 1
2025-11-24 18:04:41,737 - INFO - Frame 114 | PERCLOS: 0.00 | Yaw: 7.4° | Alerts: 1
2025-11-24 18:04:41,956 - INFO - Frame 116 | PERCLOS: 0.00 | Yaw: 7.9° | Alerts: 1
2025-11-24 18:04:42,174 - INFO - Frame 118 | PERCLOS: 0.00 | Yaw: 8.2° | Alerts: 1
2025-11-24 18:04:42,483 - INFO - Frame 120 | PERCLOS: 0.00 | Yaw: 8.6° | Alerts: 1
2025-11-24 18:04:42,717 - INFO - Frame 122 | PERCLOS: 0.00 | Yaw: 9.3° | Alerts: 1
2025-11-24 18:04:42,995 - INFO - Frame 124 | PERCLOS: 0.00 | Yaw: 9.6° | Alerts: 1
2025-11-24 18:04:43,353 - INFO - Frame 126 | PERCLOS: 0.00 | Yaw: 10.3° | Alerts: 1
2025-11-24 18:04:43,570 - INFO - Frame 128 | PERCLOS: 0.00 | Yaw: 11.5° | Alerts: 1
2025-11-24 18:04:43,791 - INFO - Frame 130 | PERCLOS: 0.00 | Yaw: 10.7° | Alerts: 1
2025-11-24 18:04:44,098 - INFO - Frame 132 | PERCLOS: 0.00 | Yaw: 12.1° | Alerts: 1
2025-11-24 18:04:44,313 - INFO - Frame 134 | PERCLOS: 0.00 | Yaw: 13.4° | Alerts: 1
2025-11-24 18:04:44,555 - INFO - Frame 136 | PERCLOS: 0.00 | Yaw: 13.3° | Alerts: 1
2025-11-24 18:04:44,871 - INFO - Frame 138 | PERCLOS: 0.00 | Yaw: 12.9° | Alerts: 1
2025-11-24 18:04:45,092 - INFO - Frame 140 | PERCLOS: 0.00 | Yaw: 12.5° | Alerts: 1
2025-11-24 18:04:45,314 - INFO - Frame 142 | PERCLOS: 0.00 | Yaw: 12.2° | Alerts: 1
2025-11-24 18:04:45,630 - INFO - Frame 144 | PERCLOS: 0.00 | Yaw: 10.9° | Alerts: 1
2025-11-24 18:04:45,866 - INFO - Frame 146 | PERCLOS: 0.00 | Yaw: 10.1° | Alerts: 1
2025-11-24 18:04:46,082 - INFO - Frame 148 | PERCLOS: 0.20 | Yaw: 7.4° | Alerts: 1
2025-11-24 18:04:46,401 - INFO - Frame 150 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 18:04:46,621 - INFO - Frame 152 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 1
2025-11-24 18:04:46,838 - INFO - Frame 154 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 1
2025-11-24 18:04:47,144 - INFO - Frame 156 | PERCLOS: 0.00 | Yaw: 6.9° | Alerts: 1
2025-11-24 18:04:47,365 - INFO - Frame 158 | PERCLOS: 0.00 | Yaw: 5.9° | Alerts: 1
2025-11-24 18:04:47,584 - INFO - Frame 160 | PERCLOS: 0.00 | Yaw: 4.8° | Alerts: 1
2025-11-24 18:04:47,887 - INFO - Frame 162 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 18:04:48,110 - INFO - Frame 164 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-24 18:04:48,315 - INFO - Frame 166 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 1
2025-11-24 18:04:48,670 - INFO - Frame 168 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 1
2025-11-24 18:04:48,905 - INFO - Frame 170 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-24 18:04:49,121 - INFO - Frame 172 | PERCLOS: 0.00 | Yaw: 6.4° | Alerts: 1
2025-11-24 18:04:49,437 - INFO - Frame 174 | PERCLOS: 0.00 | Yaw: 6.1° | Alerts: 1
2025-11-24 18:04:49,666 - INFO - Frame 176 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 1
2025-11-24 18:04:49,883 - INFO - Frame 178 | PERCLOS: 0.09 | Yaw: 3.9° | Alerts: 1
2025-11-24 18:04:50,199 - INFO - Frame 180 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 1
2025-11-24 18:04:50,428 - INFO - Frame 182 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 1
2025-11-24 18:04:50,651 - INFO - Frame 184 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 1
2025-11-24 18:04:50,962 - INFO - Frame 186 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 1
2025-11-24 18:04:51,188 - INFO - Frame 188 | PERCLOS: 0.00 | Yaw: 6.2° | Alerts: 1
2025-11-24 18:04:51,407 - INFO - Frame 190 | PERCLOS: 0.00 | Yaw: 9.4° | Alerts: 1
2025-11-24 18:04:51,722 - INFO - Frame 192 | PERCLOS: 0.00 | Yaw: 10.6° | Alerts: 1
2025-11-24 18:04:51,958 - INFO - Frame 194 | PERCLOS: 0.19 | Yaw: 7.8° | Alerts: 1
2025-11-24 18:04:52,185 - INFO - Frame 196 | PERCLOS: 0.00 | Yaw: 9.0° | Alerts: 1
2025-11-24 18:04:52,480 - INFO - Frame 198 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:04:52,691 - INFO - Frame 200 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 1
2025-11-24 18:04:52,908 - INFO - Frame 202 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 1
2025-11-24 18:04:53,237 - INFO - Frame 204 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 1
2025-11-24 18:04:53,490 - INFO - Frame 206 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 18:04:53,729 - INFO - Frame 208 | PERCLOS: 0.00 | Yaw: 6.5° | Alerts: 1
2025-11-24 18:04:54,069 - INFO - Frame 210 | PERCLOS: 0.00 | Yaw: 10.4° | Alerts: 1
2025-11-24 18:04:54,287 - INFO - Frame 212 | PERCLOS: 0.00 | Yaw: 10.3° | Alerts: 1
2025-11-24 18:04:54,509 - INFO - Frame 214 | PERCLOS: 0.00 | Yaw: 10.1° | Alerts: 1
2025-11-24 18:04:54,862 - INFO - Frame 216 | PERCLOS: 0.00 | Yaw: 9.6° | Alerts: 1
2025-11-24 18:04:55,096 - INFO - Frame 218 | PERCLOS: 0.00 | Yaw: 9.2° | Alerts: 1
2025-11-24 18:04:55,342 - INFO - Frame 220 | PERCLOS: 0.00 | Yaw: 8.6° | Alerts: 1
2025-11-24 18:04:55,636 - INFO - Frame 222 | PERCLOS: 0.00 | Yaw: 7.3° | Alerts: 1
2025-11-24 18:04:55,855 - INFO - Frame 224 | PERCLOS: 0.02 | Yaw: 7.3° | Alerts: 1
2025-11-24 18:04:56,078 - INFO - Frame 226 | PERCLOS: 0.00 | Yaw: 6.6° | Alerts: 1
2025-11-24 18:04:56,385 - INFO - Frame 228 | PERCLOS: 0.00 | Yaw: 6.6° | Alerts: 1
2025-11-24 18:04:56,603 - INFO - Frame 230 | PERCLOS: 0.00 | Yaw: 6.3° | Alerts: 1
2025-11-24 18:04:56,829 - INFO - Frame 232 | PERCLOS: 0.00 | Yaw: 6.2° | Alerts: 1
2025-11-24 18:04:57,132 - INFO - Frame 234 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 1
2025-11-24 18:04:57,349 - INFO - Frame 236 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 1
2025-11-24 18:04:57,580 - INFO - Frame 238 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 1
2025-11-24 18:04:57,909 - INFO - Frame 240 | PERCLOS: 0.00 | Yaw: 5.8° | Alerts: 1
2025-11-24 18:04:58,123 - INFO - Frame 242 | PERCLOS: 0.00 | Yaw: 5.8° | Alerts: 1
2025-11-24 18:04:58,325 - INFO - Frame 244 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-24 18:04:58,645 - INFO - Frame 246 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 1
2025-11-24 18:04:58,897 - INFO - Frame 248 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 1
2025-11-24 18:04:59,125 - INFO - Frame 250 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-24 18:04:59,453 - INFO - Frame 252 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-24 18:04:59,682 - INFO - Frame 254 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 1
2025-11-24 18:04:59,896 - INFO - Frame 256 | PERCLOS: 0.00 | Yaw: 4.9° | Alerts: 1
2025-11-24 18:05:00,214 - INFO - Frame 258 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 1
2025-11-24 18:05:00,481 - INFO - Frame 260 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 1
2025-11-24 18:05:00,704 - INFO - Frame 262 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-24 18:05:01,031 - INFO - Frame 264 | PERCLOS: 0.00 | Yaw: 5.8° | Alerts: 1
2025-11-24 18:05:01,248 - INFO - Frame 266 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-24 18:05:01,481 - INFO - Frame 268 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-24 18:05:01,800 - INFO - Frame 270 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 1
2025-11-24 18:05:02,052 - INFO - Frame 272 | PERCLOS: 0.00 | Yaw: 6.3° | Alerts: 1
2025-11-24 18:05:02,277 - INFO - Frame 274 | PERCLOS: 0.00 | Yaw: 6.9° | Alerts: 1
2025-11-24 18:05:02,584 - INFO - Frame 276 | PERCLOS: 0.04 | Yaw: 13.1° | Alerts: 1
2025-11-24 18:05:02,766 - INFO - Frame 278 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:02,872 - INFO - Frame 280 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:03,063 - INFO - Frame 282 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:03,160 - INFO - Frame 284 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:03,255 - INFO - Frame 286 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:03,453 - INFO - Frame 288 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:03,553 - INFO - Frame 290 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:03,678 - INFO - Frame 292 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:03,835 - INFO - Frame 294 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:03,941 - INFO - Frame 296 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:04,137 - INFO - Frame 298 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:04,445 - INFO - Frame 300 | PERCLOS: 0.00 | Yaw: -2.8° | Alerts: 1
2025-11-24 18:05:04,596 - INFO - Frame 302 | PERCLOS: 0.00 | Yaw: -2.5° | Alerts: 1
2025-11-24 18:05:04,820 - INFO - Frame 304 | PERCLOS: 0.00 | Yaw: -2.0° | Alerts: 1
2025-11-24 18:05:05,157 - INFO - Frame 306 | PERCLOS: 0.00 | Yaw: -2.2° | Alerts: 1
2025-11-24 18:05:05,375 - INFO - Frame 308 | PERCLOS: 0.00 | Yaw: -2.3° | Alerts: 1
2025-11-24 18:05:05,595 - INFO - Frame 310 | PERCLOS: 0.00 | Yaw: -2.6° | Alerts: 1
2025-11-24 18:05:05,951 - INFO - Frame 312 | PERCLOS: 0.00 | Yaw: -2.7° | Alerts: 1
2025-11-24 18:05:06,203 - INFO - Frame 314 | PERCLOS: 0.00 | Yaw: -3.4° | Alerts: 1
2025-11-24 18:05:06,407 - INFO - Frame 316 | PERCLOS: 0.00 | Yaw: -3.5° | Alerts: 1
2025-11-24 18:05:06,724 - INFO - Frame 318 | PERCLOS: 0.00 | Yaw: -3.6° | Alerts: 1
2025-11-24 18:05:06,960 - INFO - Frame 320 | PERCLOS: 0.53 | Yaw: -2.8° | Alerts: 2
2025-11-24 18:05:07,169 - INFO - Frame 322 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 1
2025-11-24 18:05:07,488 - INFO - Frame 324 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 18:05:07,720 - INFO - Frame 326 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 1
2025-11-24 18:05:07,941 - INFO - Frame 328 | PERCLOS: 0.00 | Yaw: -0.8° | Alerts: 1
2025-11-24 18:05:08,262 - INFO - Frame 330 | PERCLOS: 0.00 | Yaw: -1.5° | Alerts: 1
2025-11-24 18:05:08,503 - INFO - Frame 332 | PERCLOS: 0.00 | Yaw: -2.1° | Alerts: 1
2025-11-24 18:05:08,782 - INFO - Frame 334 | PERCLOS: 0.00 | Yaw: -2.5° | Alerts: 1
2025-11-24 18:05:09,119 - INFO - Frame 336 | PERCLOS: 0.00 | Yaw: -2.8° | Alerts: 1
2025-11-24 18:05:09,349 - INFO - Frame 338 | PERCLOS: 0.00 | Yaw: -2.5° | Alerts: 1
2025-11-24 18:05:09,566 - INFO - Frame 340 | PERCLOS: 0.00 | Yaw: -2.8° | Alerts: 1
2025-11-24 18:05:09,885 - INFO - Frame 342 | PERCLOS: 0.00 | Yaw: -2.0° | Alerts: 1
2025-11-24 18:05:10,126 - INFO - Frame 344 | PERCLOS: 0.00 | Yaw: -1.8° | Alerts: 1
2025-11-24 18:05:10,344 - INFO - Frame 346 | PERCLOS: 0.00 | Yaw: -1.5° | Alerts: 1
2025-11-24 18:05:10,666 - INFO - Frame 348 | PERCLOS: 0.00 | Yaw: -1.2° | Alerts: 1
2025-11-24 18:05:10,895 - INFO - Frame 350 | PERCLOS: 0.00 | Yaw: -1.1° | Alerts: 1
2025-11-24 18:05:11,123 - INFO - Frame 352 | PERCLOS: 0.60 | Yaw: 1.0° | Alerts: 2
2025-11-24 18:05:11,469 - INFO - Frame 354 | PERCLOS: 0.00 | Yaw: 8.7° | Alerts: 1
2025-11-24 18:05:11,689 - INFO - Frame 356 | PERCLOS: 0.00 | Yaw: 10.7° | Alerts: 1
2025-11-24 18:05:11,914 - INFO - Frame 358 | PERCLOS: 0.00 | Yaw: 12.2° | Alerts: 1
2025-11-24 18:05:12,238 - INFO - Frame 360 | PERCLOS: 0.00 | Yaw: 12.2° | Alerts: 1
2025-11-24 18:05:12,359 - INFO - Video file uploaded: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:05:12,359 - INFO - Video thread started with source: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:05:12,438 - INFO - ✓ Video file opened: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:05:12,540 - INFO - Frame 0 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:12,633 - INFO - Frame 362 | PERCLOS: 0.00 | Yaw: 11.7° | Alerts: 1
2025-11-24 18:05:12,654 - INFO - Frame 2 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:12,765 - INFO - Frame 4 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:12,859 - INFO - Frame 364 | PERCLOS: 0.00 | Yaw: 12.4° | Alerts: 1
2025-11-24 18:05:12,882 - INFO - Frame 6 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:13,013 - INFO - Frame 8 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:13,121 - INFO - Frame 366 | PERCLOS: 0.00 | Yaw: 12.5° | Alerts: 1
2025-11-24 18:05:13,123 - INFO - Frame 10 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:13,230 - INFO - Frame 12 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:13,344 - INFO - Frame 14 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:13,358 - INFO - Frame 368 | PERCLOS: 0.00 | Yaw: 12.0° | Alerts: 1
2025-11-24 18:05:13,443 - INFO - Frame 16 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:13,547 - INFO - Frame 18 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:13,583 - INFO - Frame 370 | PERCLOS: 0.17 | Yaw: 12.2° | Alerts: 1
2025-11-24 18:05:13,661 - INFO - Frame 20 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:13,773 - INFO - Frame 372 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:13,773 - INFO - Frame 22 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:13,875 - INFO - Frame 24 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:13,998 - INFO - Frame 26 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:14,003 - INFO - Frame 374 | PERCLOS: 0.00 | Yaw: 10.4° | Alerts: 0
2025-11-24 18:05:14,125 - INFO - Frame 28 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:14,175 - INFO - Frame 376 | PERCLOS: 0.00 | Yaw: 10.2° | Alerts: 0
2025-11-24 18:05:14,247 - INFO - Frame 30 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:14,359 - INFO - Frame 378 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:14,359 - INFO - Frame 32 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:14,480 - INFO - Frame 34 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:14,523 - INFO - Frame 380 | PERCLOS: 0.00 | Yaw: 9.9° | Alerts: 0
2025-11-24 18:05:14,588 - INFO - Frame 36 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:14,693 - INFO - Frame 38 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:14,693 - INFO - Frame 382 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:14,809 - INFO - Frame 40 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:14,922 - INFO - Frame 42 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:15,033 - INFO - Frame 384 | PERCLOS: 0.00 | Yaw: 10.6° | Alerts: 1
2025-11-24 18:05:15,033 - INFO - Frame 44 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:15,154 - INFO - Frame 46 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:15,259 - INFO - Frame 48 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:15,262 - INFO - Frame 386 | PERCLOS: 0.00 | Yaw: 10.8° | Alerts: 1
2025-11-24 18:05:15,368 - INFO - Frame 50 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:15,411 - INFO - Frame 388 | PERCLOS: 0.00 | Yaw: 10.8° | Alerts: 1
2025-11-24 18:05:15,480 - INFO - Frame 52 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:15,521 - INFO - Frame 54 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:15,708 - INFO - Frame 56 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:15,822 - INFO - Frame 58 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:15,823 - INFO - Frame 390 | PERCLOS: 0.00 | Yaw: 11.1° | Alerts: 1
2025-11-24 18:05:15,943 - INFO - Frame 60 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:16,044 - INFO - Frame 392 | PERCLOS: 0.00 | Yaw: 11.1° | Alerts: 1
2025-11-24 18:05:16,046 - INFO - Frame 62 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:16,149 - INFO - Frame 64 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:16,190 - INFO - Frame 394 | PERCLOS: 0.00 | Yaw: 10.7° | Alerts: 1
2025-11-24 18:05:16,264 - INFO - Frame 66 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:16,370 - INFO - Frame 396 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:16,373 - INFO - Frame 68 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:16,413 - INFO - Frame 70 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:16,581 - INFO - Frame 72 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:16,582 - INFO - Frame 398 | PERCLOS: 0.00 | Yaw: 10.7° | Alerts: 0
2025-11-24 18:05:16,623 - INFO - Frame 74 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:16,729 - INFO - Frame 76 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:16,810 - INFO - Frame 400 | PERCLOS: 0.00 | Yaw: 10.8° | Alerts: 0
2025-11-24 18:05:16,840 - INFO - Frame 78 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:16,955 - INFO - Frame 80 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:17,076 - INFO - Frame 82 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:17,164 - INFO - Frame 402 | PERCLOS: 0.00 | Yaw: 11.1° | Alerts: 1
2025-11-24 18:05:17,194 - INFO - Frame 84 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:17,305 - INFO - Frame 86 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:17,406 - INFO - Frame 404 | PERCLOS: 0.00 | Yaw: 11.7° | Alerts: 1
2025-11-24 18:05:17,426 - INFO - Frame 88 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:17,517 - INFO - Frame 90 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:17,517 - INFO - Frame 406 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:17,618 - INFO - Frame 92 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:17,732 - INFO - Frame 94 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:17,852 - INFO - Frame 96 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:17,866 - INFO - Frame 408 | PERCLOS: 0.00 | Yaw: 12.3° | Alerts: 1
2025-11-24 18:05:17,965 - INFO - Frame 98 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:18,080 - INFO - Frame 410 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:18,083 - INFO - Frame 100 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:18,189 - INFO - Frame 102 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:18,229 - INFO - Frame 412 | PERCLOS: 0.00 | Yaw: 11.2° | Alerts: 0
2025-11-24 18:05:18,230 - INFO - Frame 104 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:18,273 - INFO - Frame 106 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:18,316 - INFO - Frame 108 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:18,359 - INFO - Frame 110 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:18,387 - INFO - Frame 414 | PERCLOS: 0.00 | Yaw: 10.7° | Alerts: 1
2025-11-24 18:05:18,404 - INFO - Frame 112 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:18,447 - INFO - Frame 114 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:18,490 - INFO - Frame 116 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:18,496 - INFO - Frame 416 | PERCLOS: 0.00 | Yaw: 10.7° | Alerts: 1
2025-11-24 18:05:18,531 - INFO - Video thread started with source: Camera
2025-11-24 18:05:18,534 - ERROR - ❌ No camera found!
2025-11-24 18:05:18,535 - INFO - Frame 118 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:18,654 - INFO - Video thread started with source: Camera
2025-11-24 18:05:18,656 - ERROR - ❌ No camera found!
2025-11-24 18:05:18,662 - INFO - Frame 418 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:18,662 - INFO - Frame 120 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:18,774 - INFO - Video thread started with source: Camera
2025-11-24 18:05:18,774 - ERROR - ❌ No camera found!
2025-11-24 18:05:18,778 - INFO - Frame 122 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:18,887 - INFO - Video thread started with source: Camera
2025-11-24 18:05:18,888 - ERROR - ❌ No camera found!
2025-11-24 18:05:18,893 - INFO - Frame 124 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:18,988 - INFO - Video thread started with source: Camera
2025-11-24 18:05:18,989 - INFO - Frame 126 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:18,989 - ERROR - ❌ No camera found!
2025-11-24 18:05:19,009 - INFO - Frame 420 | PERCLOS: 0.00 | Yaw: 10.5° | Alerts: 1
2025-11-24 18:05:19,087 - INFO - Video thread started with source: Camera
2025-11-24 18:05:19,089 - ERROR - ❌ No camera found!
2025-11-24 18:05:19,092 - INFO - Frame 128 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:19,194 - INFO - Video thread started with source: Camera
2025-11-24 18:05:19,195 - ERROR - ❌ No camera found!
2025-11-24 18:05:19,200 - INFO - Frame 130 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:19,228 - INFO - Frame 422 | PERCLOS: 0.00 | Yaw: 10.4° | Alerts: 1
2025-11-24 18:05:19,305 - INFO - Video thread started with source: Camera
2025-11-24 18:05:19,306 - INFO - Frame 132 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:19,306 - ERROR - ❌ No camera found!
2025-11-24 18:05:19,409 - INFO - Video thread started with source: Camera
2025-11-24 18:05:19,411 - ERROR - ❌ No camera found!
2025-11-24 18:05:19,416 - INFO - Frame 134 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:19,446 - INFO - Frame 424 | PERCLOS: 0.00 | Yaw: 11.1° | Alerts: 1
2025-11-24 18:05:19,514 - INFO - Video thread started with source: Camera
2025-11-24 18:05:19,515 - INFO - Frame 136 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:19,515 - ERROR - ❌ No camera found!
2025-11-24 18:05:19,612 - INFO - Video thread started with source: Camera
2025-11-24 18:05:19,613 - ERROR - ❌ No camera found!
2025-11-24 18:05:19,617 - INFO - Frame 138 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:19,718 - INFO - Video thread started with source: Camera
2025-11-24 18:05:19,719 - INFO - Frame 140 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:19,720 - ERROR - ❌ No camera found!
2025-11-24 18:05:19,739 - INFO - Frame 426 | PERCLOS: 0.00 | Yaw: 11.3° | Alerts: 1
2025-11-24 18:05:19,821 - INFO - Video thread started with source: Camera
2025-11-24 18:05:19,822 - ERROR - ❌ No camera found!
2025-11-24 18:05:19,823 - INFO - Frame 142 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:19,954 - INFO - Frame 144 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:19,959 - INFO - Frame 428 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:19,959 - INFO - Video thread started with source: Camera
2025-11-24 18:05:19,969 - ERROR - ❌ No camera found!
2025-11-24 18:05:20,108 - INFO - Frame 146 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:20,111 - INFO - Video thread started with source: Camera
2025-11-24 18:05:20,112 - ERROR - ❌ No camera found!
2025-11-24 18:05:20,221 - INFO - Frame 148 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:20,223 - INFO - Video thread started with source: Camera
2025-11-24 18:05:20,224 - INFO - Frame 430 | PERCLOS: 0.00 | Yaw: 6.3° | Alerts: 0
2025-11-24 18:05:20,224 - ERROR - ❌ No camera found!
2025-11-24 18:05:20,323 - INFO - Frame 150 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:20,325 - INFO - Video thread started with source: Camera
2025-11-24 18:05:20,326 - ERROR - ❌ No camera found!
2025-11-24 18:05:20,440 - INFO - Video thread started with source: Camera
2025-11-24 18:05:20,441 - ERROR - ❌ No camera found!
2025-11-24 18:05:20,441 - INFO - Frame 152 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:20,540 - INFO - Frame 432 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:05:20,542 - INFO - Video thread started with source: Camera
2025-11-24 18:05:20,543 - ERROR - ❌ No camera found!
2025-11-24 18:05:20,543 - INFO - Frame 154 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:20,639 - INFO - Video thread started with source: Camera
2025-11-24 18:05:20,640 - ERROR - ❌ No camera found!
2025-11-24 18:05:20,742 - INFO - Frame 434 | PERCLOS: 0.00 | Yaw: 4.7° | Alerts: 1
2025-11-24 18:05:20,742 - INFO - Video thread started with source: Camera
2025-11-24 18:05:20,743 - ERROR - ❌ No camera found!
2025-11-24 18:05:20,867 - INFO - Frame 156 | PERCLOS: 0.00 | Yaw: 4.7° | Alerts: 0
2025-11-24 18:05:20,868 - INFO - Video thread started with source: Camera
2025-11-24 18:05:20,870 - ERROR - ❌ No camera found!
2025-11-24 18:05:20,974 - INFO - Frame 158 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:20,976 - INFO - Frame 436 | PERCLOS: 0.00 | Yaw: 5.8° | Alerts: 1
2025-11-24 18:05:20,977 - INFO - Video thread started with source: Camera
2025-11-24 18:05:20,977 - ERROR - ❌ No camera found!
2025-11-24 18:05:21,075 - INFO - Frame 160 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:21,078 - INFO - Video thread started with source: Camera
2025-11-24 18:05:21,078 - ERROR - ❌ No camera found!
2025-11-24 18:05:21,188 - INFO - Frame 162 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:21,191 - INFO - Video thread started with source: Camera
2025-11-24 18:05:21,192 - ERROR - ❌ No camera found!
2025-11-24 18:05:21,299 - INFO - Frame 164 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:21,305 - INFO - Video thread started with source: Camera
2025-11-24 18:05:21,305 - INFO - Frame 438 | PERCLOS: 0.00 | Yaw: 4.9° | Alerts: 1
2025-11-24 18:05:21,306 - ERROR - ❌ No camera found!
2025-11-24 18:05:21,411 - INFO - Video thread started with source: Camera
2025-11-24 18:05:21,412 - ERROR - ❌ No camera found!
2025-11-24 18:05:21,417 - INFO - Frame 440 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:21,445 - INFO - Frame 166 | PERCLOS: 0.00 | Yaw: -1.8° | Alerts: 0
2025-11-24 18:05:21,539 - INFO - Video thread started with source: Camera
2025-11-24 18:05:21,540 - ERROR - ❌ No camera found!
2025-11-24 18:05:21,562 - INFO - Frame 168 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:21,664 - INFO - Video thread started with source: Camera
2025-11-24 18:05:21,665 - ERROR - ❌ No camera found!
2025-11-24 18:05:21,689 - INFO - Frame 170 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:21,698 - INFO - Frame 442 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 18:05:21,777 - INFO - Video thread started with source: Camera
2025-11-24 18:05:21,778 - ERROR - ❌ No camera found!
2025-11-24 18:05:21,801 - INFO - Frame 172 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:21,886 - INFO - Video thread started with source: Camera
2025-11-24 18:05:21,887 - ERROR - ❌ No camera found!
2025-11-24 18:05:21,913 - INFO - Frame 174 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:22,015 - INFO - Video thread started with source: Camera
2025-11-24 18:05:22,016 - ERROR - ❌ No camera found!
2025-11-24 18:05:22,038 - INFO - Frame 176 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:22,040 - INFO - Frame 444 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 1
2025-11-24 18:05:22,124 - INFO - Video thread started with source: Camera
2025-11-24 18:05:22,125 - ERROR - ❌ No camera found!
2025-11-24 18:05:22,149 - INFO - Frame 178 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:22,233 - INFO - Video thread started with source: Camera
2025-11-24 18:05:22,235 - ERROR - ❌ No camera found!
2025-11-24 18:05:22,259 - INFO - Frame 180 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:22,266 - INFO - Frame 446 | PERCLOS: 0.00 | Yaw: 0.2° | Alerts: 1
2025-11-24 18:05:22,353 - INFO - Video thread started with source: Camera
2025-11-24 18:05:22,354 - ERROR - ❌ No camera found!
2025-11-24 18:05:22,379 - INFO - Frame 182 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:22,457 - INFO - Video thread started with source: Camera
2025-11-24 18:05:22,458 - ERROR - ❌ No camera found!
2025-11-24 18:05:22,482 - INFO - Frame 184 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:22,491 - INFO - Frame 448 | PERCLOS: 0.00 | Yaw: -1.4° | Alerts: 1
2025-11-24 18:05:22,566 - INFO - Video thread started with source: Camera
2025-11-24 18:05:22,567 - ERROR - ❌ No camera found!
2025-11-24 18:05:22,586 - INFO - Frame 186 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:22,673 - INFO - Video thread started with source: Camera
2025-11-24 18:05:22,674 - ERROR - ❌ No camera found!
2025-11-24 18:05:22,706 - INFO - Frame 188 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:22,795 - INFO - Video thread started with source: Camera
2025-11-24 18:05:22,796 - ERROR - ❌ No camera found!
2025-11-24 18:05:22,819 - INFO - Frame 450 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 1
2025-11-24 18:05:22,820 - INFO - Frame 190 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:22,900 - INFO - Video thread started with source: Camera
2025-11-24 18:05:22,901 - ERROR - ❌ No camera found!
2025-11-24 18:05:22,925 - INFO - Frame 192 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:23,002 - INFO - Video thread started with source: Camera
2025-11-24 18:05:23,003 - ERROR - ❌ No camera found!
2025-11-24 18:05:23,027 - INFO - Frame 194 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:23,037 - INFO - Frame 452 | PERCLOS: 0.27 | Yaw: 1.2° | Alerts: 1
2025-11-24 18:05:23,117 - INFO - Video thread started with source: Camera
2025-11-24 18:05:23,119 - ERROR - ❌ No camera found!
2025-11-24 18:05:23,143 - INFO - Frame 196 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:23,229 - INFO - Video thread started with source: Camera
2025-11-24 18:05:23,230 - ERROR - ❌ No camera found!
2025-11-24 18:05:23,253 - INFO - Frame 198 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:23,260 - INFO - Frame 454 | PERCLOS: 0.00 | Yaw: 8.1° | Alerts: 1
2025-11-24 18:05:23,344 - INFO - Video thread started with source: Camera
2025-11-24 18:05:23,345 - ERROR - ❌ No camera found!
2025-11-24 18:05:23,367 - INFO - Frame 200 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:23,460 - INFO - Video thread started with source: Camera
2025-11-24 18:05:23,461 - ERROR - ❌ No camera found!
2025-11-24 18:05:23,485 - INFO - Frame 202 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:23,574 - INFO - Video thread started with source: Camera
2025-11-24 18:05:23,575 - ERROR - ❌ No camera found!
2025-11-24 18:05:23,596 - INFO - Frame 456 | PERCLOS: 0.00 | Yaw: 9.8° | Alerts: 1
2025-11-24 18:05:23,602 - INFO - Frame 204 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:23,678 - INFO - Video thread started with source: Camera
2025-11-24 18:05:23,679 - ERROR - ❌ No camera found!
2025-11-24 18:05:23,699 - INFO - Frame 206 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:23,785 - INFO - Video thread started with source: Camera
2025-11-24 18:05:23,786 - ERROR - ❌ No camera found!
2025-11-24 18:05:23,809 - INFO - Frame 208 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:23,820 - INFO - Frame 458 | PERCLOS: 0.00 | Yaw: 9.9° | Alerts: 1
2025-11-24 18:05:23,895 - INFO - Video thread started with source: Camera
2025-11-24 18:05:23,896 - ERROR - ❌ No camera found!
2025-11-24 18:05:23,919 - INFO - Frame 210 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:23,997 - INFO - Video thread started with source: Camera
2025-11-24 18:05:23,998 - ERROR - ❌ No camera found!
2025-11-24 18:05:24,021 - INFO - Frame 212 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:24,028 - INFO - Frame 460 | PERCLOS: 0.00 | Yaw: 10.7° | Alerts: 1
2025-11-24 18:05:24,114 - INFO - Video thread started with source: Camera
2025-11-24 18:05:24,116 - ERROR - ❌ No camera found!
2025-11-24 18:05:24,139 - INFO - Frame 214 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:24,236 - INFO - Video thread started with source: Camera
2025-11-24 18:05:24,238 - ERROR - ❌ No camera found!
2025-11-24 18:05:24,262 - INFO - Frame 216 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:24,352 - INFO - Video thread started with source: Camera
2025-11-24 18:05:24,353 - ERROR - ❌ No camera found!
2025-11-24 18:05:24,375 - INFO - Frame 462 | PERCLOS: 0.00 | Yaw: 11.3° | Alerts: 1
2025-11-24 18:05:24,376 - INFO - Frame 218 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:24,461 - INFO - Video thread started with source: Camera
2025-11-24 18:05:24,462 - ERROR - ❌ No camera found!
2025-11-24 18:05:24,480 - INFO - Frame 220 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:24,591 - INFO - Video thread started with source: Camera
2025-11-24 18:05:24,593 - ERROR - ❌ No camera found!
2025-11-24 18:05:24,614 - INFO - Frame 222 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:24,623 - INFO - Frame 464 | PERCLOS: 0.00 | Yaw: 11.5° | Alerts: 1
2025-11-24 18:05:24,705 - INFO - Video thread started with source: Camera
2025-11-24 18:05:24,706 - ERROR - ❌ No camera found!
2025-11-24 18:05:24,725 - INFO - Frame 224 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:24,812 - INFO - Video thread started with source: Camera
2025-11-24 18:05:24,814 - ERROR - ❌ No camera found!
2025-11-24 18:05:24,838 - INFO - Frame 226 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:24,846 - INFO - Frame 466 | PERCLOS: 0.00 | Yaw: 11.8° | Alerts: 1
2025-11-24 18:05:25,013 - INFO - Video thread started with source: Camera
2025-11-24 18:05:25,014 - ERROR - ❌ No camera found!
2025-11-24 18:05:25,032 - INFO - Frame 228 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:25,134 - INFO - Video thread started with source: Camera
2025-11-24 18:05:25,136 - ERROR - ❌ No camera found!
2025-11-24 18:05:25,160 - INFO - Frame 230 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:25,255 - INFO - Video thread started with source: Camera
2025-11-24 18:05:25,257 - ERROR - ❌ No camera found!
2025-11-24 18:05:25,277 - INFO - Frame 232 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:25,277 - INFO - Frame 468 | PERCLOS: 0.00 | Yaw: 11.7° | Alerts: 1
2025-11-24 18:05:25,382 - INFO - Video thread started with source: Camera
2025-11-24 18:05:25,383 - ERROR - ❌ No camera found!
2025-11-24 18:05:25,402 - INFO - Frame 234 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:25,494 - INFO - Video thread started with source: Camera
2025-11-24 18:05:25,495 - ERROR - ❌ No camera found!
2025-11-24 18:05:25,499 - INFO - Frame 236 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:25,527 - INFO - Frame 470 | PERCLOS: 0.00 | Yaw: 11.5° | Alerts: 1
2025-11-24 18:05:25,603 - INFO - Video thread started with source: Camera
2025-11-24 18:05:25,605 - ERROR - ❌ No camera found!
2025-11-24 18:05:25,605 - INFO - Frame 238 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:25,718 - INFO - Video thread started with source: Camera
2025-11-24 18:05:25,720 - ERROR - ❌ No camera found!
2025-11-24 18:05:25,726 - INFO - Frame 240 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:25,752 - INFO - Frame 472 | PERCLOS: 0.00 | Yaw: 11.7° | Alerts: 1
2025-11-24 18:05:25,830 - INFO - Video thread started with source: Camera
2025-11-24 18:05:25,831 - INFO - Frame 242 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:25,831 - ERROR - ❌ No camera found!
2025-11-24 18:05:25,932 - INFO - Frame 474 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:25,932 - INFO - Frame 244 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:25,935 - INFO - Video thread started with source: Camera
2025-11-24 18:05:25,936 - ERROR - ❌ No camera found!
2025-11-24 18:05:26,045 - INFO - Frame 246 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:26,047 - INFO - Video thread started with source: Camera
2025-11-24 18:05:26,048 - ERROR - ❌ No camera found!
2025-11-24 18:05:26,149 - INFO - Frame 248 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:26,152 - INFO - Video thread started with source: Camera
2025-11-24 18:05:26,152 - INFO - Frame 476 | PERCLOS: 0.00 | Yaw: 10.8° | Alerts: 0
2025-11-24 18:05:26,153 - ERROR - ❌ No camera found!
2025-11-24 18:05:26,251 - INFO - Frame 250 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:26,253 - INFO - Video thread started with source: Camera
2025-11-24 18:05:26,254 - ERROR - ❌ No camera found!
2025-11-24 18:05:26,361 - INFO - Video thread started with source: Camera
2025-11-24 18:05:26,361 - INFO - Frame 478 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 0
2025-11-24 18:05:26,363 - ERROR - ❌ No camera found!
2025-11-24 18:05:26,364 - INFO - Frame 252 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:26,473 - INFO - Video thread started with source: Camera
2025-11-24 18:05:26,474 - ERROR - ❌ No camera found!
2025-11-24 18:05:26,480 - INFO - Frame 480 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:26,481 - INFO - Frame 254 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:26,579 - INFO - Video thread started with source: Camera
2025-11-24 18:05:26,580 - ERROR - ❌ No camera found!
2025-11-24 18:05:26,580 - INFO - Frame 256 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:26,687 - INFO - Frame 482 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:26,688 - INFO - Frame 258 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:26,690 - INFO - Video thread started with source: Camera
2025-11-24 18:05:26,692 - ERROR - ❌ No camera found!
2025-11-24 18:05:26,799 - INFO - Frame 260 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:26,801 - INFO - Video thread started with source: Camera
2025-11-24 18:05:26,803 - ERROR - ❌ No camera found!
2025-11-24 18:05:26,912 - INFO - Video thread started with source: Camera
2025-11-24 18:05:26,914 - ERROR - ❌ No camera found!
2025-11-24 18:05:26,914 - INFO - Frame 484 | PERCLOS: 0.00 | Yaw: -1.1° | Alerts: 0
2025-11-24 18:05:26,914 - INFO - Frame 262 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:27,022 - INFO - Frame 264 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:27,025 - INFO - Video thread started with source: Camera
2025-11-24 18:05:27,026 - ERROR - ❌ No camera found!
2025-11-24 18:05:27,137 - INFO - Frame 266 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:27,140 - INFO - Video thread started with source: Camera
2025-11-24 18:05:27,141 - ERROR - ❌ No camera found!
2025-11-24 18:05:27,246 - INFO - Frame 268 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:27,248 - INFO - Frame 486 | PERCLOS: 0.00 | Yaw: -1.4° | Alerts: 1
2025-11-24 18:05:27,248 - INFO - Video thread started with source: Camera
2025-11-24 18:05:27,249 - ERROR - ❌ No camera found!
2025-11-24 18:05:27,352 - INFO - Frame 270 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:27,355 - INFO - Video thread started with source: Camera
2025-11-24 18:05:27,356 - ERROR - ❌ No camera found!
2025-11-24 18:05:27,473 - INFO - Video thread started with source: Camera
2025-11-24 18:05:27,474 - ERROR - ❌ No camera found!
2025-11-24 18:05:27,474 - INFO - Frame 272 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:27,474 - INFO - Frame 488 | PERCLOS: 0.00 | Yaw: -1.3° | Alerts: 1
2025-11-24 18:05:27,579 - INFO - Frame 274 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:27,582 - INFO - Video thread started with source: Camera
2025-11-24 18:05:27,583 - ERROR - ❌ No camera found!
2025-11-24 18:05:27,690 - INFO - Frame 276 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:27,692 - INFO - Frame 490 | PERCLOS: 0.00 | Yaw: -1.5° | Alerts: 1
2025-11-24 18:05:27,693 - INFO - Video thread started with source: Camera
2025-11-24 18:05:27,694 - ERROR - ❌ No camera found!
2025-11-24 18:05:27,729 - INFO - Frame 278 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:27,813 - INFO - Video thread started with source: Camera
2025-11-24 18:05:27,814 - ERROR - ❌ No camera found!
2025-11-24 18:05:27,836 - INFO - Frame 280 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:27,923 - INFO - Video thread started with source: Camera
2025-11-24 18:05:27,924 - ERROR - ❌ No camera found!
2025-11-24 18:05:27,947 - INFO - Frame 282 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:28,028 - INFO - Frame 492 | PERCLOS: 0.00 | Yaw: -1.7° | Alerts: 1
2025-11-24 18:05:28,031 - INFO - Video thread started with source: Camera
2025-11-24 18:05:28,032 - ERROR - ❌ No camera found!
2025-11-24 18:05:28,052 - INFO - Frame 284 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:28,148 - INFO - Video thread started with source: Camera
2025-11-24 18:05:28,149 - ERROR - ❌ No camera found!
2025-11-24 18:05:28,174 - INFO - Frame 286 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:28,261 - INFO - Video thread started with source: Camera
2025-11-24 18:05:28,261 - INFO - Frame 494 | PERCLOS: 0.00 | Yaw: -1.7° | Alerts: 1
2025-11-24 18:05:28,262 - ERROR - ❌ No camera found!
2025-11-24 18:05:28,280 - INFO - Frame 288 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:28,371 - INFO - Video thread started with source: Camera
2025-11-24 18:05:28,372 - ERROR - ❌ No camera found!
2025-11-24 18:05:28,399 - INFO - Frame 290 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:28,485 - INFO - Video thread started with source: Camera
2025-11-24 18:05:28,487 - ERROR - ❌ No camera found!
2025-11-24 18:05:28,487 - INFO - Frame 496 | PERCLOS: 0.00 | Yaw: -1.4° | Alerts: 1
2025-11-24 18:05:28,508 - INFO - Frame 292 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:28,593 - INFO - Video thread started with source: Camera
2025-11-24 18:05:28,594 - ERROR - ❌ No camera found!
2025-11-24 18:05:28,614 - INFO - Frame 294 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:28,695 - INFO - Video thread started with source: Camera
2025-11-24 18:05:28,698 - ERROR - ❌ No camera found!
2025-11-24 18:05:28,722 - INFO - Frame 296 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:28,812 - INFO - Video thread started with source: Camera
2025-11-24 18:05:28,814 - ERROR - ❌ No camera found!
2025-11-24 18:05:28,834 - INFO - Frame 298 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:28,835 - INFO - Frame 498 | PERCLOS: 0.00 | Yaw: 5.2° | Alerts: 1
2025-11-24 18:05:28,919 - INFO - Video thread started with source: Camera
2025-11-24 18:05:28,920 - ERROR - ❌ No camera found!
2025-11-24 18:05:28,938 - INFO - Frame 300 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:29,026 - INFO - Video thread started with source: Camera
2025-11-24 18:05:29,027 - ERROR - ❌ No camera found!
2025-11-24 18:05:29,049 - INFO - Frame 302 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:29,062 - INFO - Frame 500 | PERCLOS: 0.00 | Yaw: 9.6° | Alerts: 1
2025-11-24 18:05:29,135 - INFO - Video thread started with source: Camera
2025-11-24 18:05:29,136 - ERROR - ❌ No camera found!
2025-11-24 18:05:29,160 - INFO - Frame 304 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:29,245 - INFO - Video thread started with source: Camera
2025-11-24 18:05:29,247 - ERROR - ❌ No camera found!
2025-11-24 18:05:29,271 - INFO - Frame 306 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:29,277 - INFO - Frame 502 | PERCLOS: 0.00 | Yaw: 10.8° | Alerts: 1
2025-11-24 18:05:29,353 - INFO - Video thread started with source: Camera
2025-11-24 18:05:29,355 - ERROR - ❌ No camera found!
2025-11-24 18:05:29,373 - INFO - Frame 308 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:29,544 - INFO - Frame 310 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:29,551 - INFO - Video file uploaded: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:05:29,551 - INFO - Video thread started with source: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:05:29,567 - INFO - ✓ Video file opened: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:05:29,587 - INFO - Frame 312 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:29,674 - INFO - Frame 0 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:29,694 - INFO - Frame 504 | PERCLOS: 0.00 | Yaw: 10.4° | Alerts: 1
2025-11-24 18:05:29,695 - INFO - Frame 314 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:29,787 - INFO - Frame 2 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:29,798 - INFO - Frame 316 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:29,920 - INFO - Frame 318 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:29,925 - INFO - Frame 4 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:29,947 - INFO - Frame 506 | PERCLOS: 0.00 | Yaw: 10.6° | Alerts: 1
2025-11-24 18:05:30,036 - INFO - Frame 6 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:30,036 - INFO - Frame 320 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:30,154 - INFO - Frame 322 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:30,154 - INFO - Frame 8 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:30,180 - INFO - Frame 508 | PERCLOS: 0.00 | Yaw: 10.3° | Alerts: 1
2025-11-24 18:05:30,275 - INFO - Frame 10 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:30,275 - INFO - Frame 324 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:30,393 - INFO - Frame 12 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:30,395 - INFO - Frame 326 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:30,498 - INFO - Frame 510 | PERCLOS: 0.00 | Yaw: 10.3° | Alerts: 1
2025-11-24 18:05:30,508 - INFO - Frame 14 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:30,508 - INFO - Frame 328 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:30,758 - INFO - Frame 512 | PERCLOS: 0.00 | Yaw: 10.8° | Alerts: 1
2025-11-24 18:05:30,762 - INFO - Frame 16 | PERCLOS: 0.00 | Yaw: 10.8° | Alerts: 0
2025-11-24 18:05:30,865 - INFO - Frame 330 | PERCLOS: 0.00 | Yaw: 10.8° | Alerts: 1
2025-11-24 18:05:30,983 - INFO - Frame 332 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:30,989 - INFO - Frame 514 | PERCLOS: 0.00 | Yaw: 9.2° | Alerts: 1
2025-11-24 18:05:31,026 - INFO - Frame 334 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:31,108 - INFO - Frame 18 | PERCLOS: 0.00 | Yaw: 9.2° | Alerts: 1
2025-11-24 18:05:31,141 - INFO - Frame 336 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:31,234 - INFO - Frame 20 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:31,245 - INFO - Frame 338 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:31,336 - INFO - Frame 516 | PERCLOS: 0.00 | Yaw: 9.3° | Alerts: 1
2025-11-24 18:05:31,347 - INFO - Frame 340 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:31,348 - INFO - Frame 22 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:31,598 - INFO - Frame 518 | PERCLOS: 0.00 | Yaw: 8.8° | Alerts: 1
2025-11-24 18:05:31,833 - INFO - Frame 342 | PERCLOS: 0.00 | Yaw: 8.8° | Alerts: 1
2025-11-24 18:05:31,834 - INFO - Frame 24 | PERCLOS: 0.00 | Yaw: 8.8° | Alerts: 1
2025-11-24 18:05:31,834 - INFO - Frame 520 | PERCLOS: 0.00 | Yaw: 8.7° | Alerts: 1
2025-11-24 18:05:31,939 - INFO - Frame 26 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:31,940 - INFO - Frame 344 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:32,050 - INFO - Frame 346 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:32,051 - INFO - Frame 28 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:32,165 - INFO - Frame 30 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:32,166 - INFO - Frame 348 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:32,169 - INFO - Frame 522 | PERCLOS: 0.00 | Yaw: 8.5° | Alerts: 1
2025-11-24 18:05:32,273 - INFO - Frame 350 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:32,273 - INFO - Frame 32 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:32,387 - INFO - Frame 352 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:32,392 - INFO - Frame 524 | PERCLOS: 0.00 | Yaw: 8.4° | Alerts: 1
2025-11-24 18:05:32,398 - INFO - Frame 34 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:32,430 - INFO - Frame 354 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:32,549 - INFO - Frame 356 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:32,640 - INFO - Frame 526 | PERCLOS: 0.00 | Yaw: 8.4° | Alerts: 1
2025-11-24 18:05:32,662 - INFO - Frame 358 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:32,757 - INFO - Frame 36 | PERCLOS: 0.00 | Yaw: 8.4° | Alerts: 0
2025-11-24 18:05:32,780 - INFO - Frame 360 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:32,888 - INFO - Frame 38 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:32,898 - INFO - Frame 362 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:32,991 - INFO - Frame 528 | PERCLOS: 0.00 | Yaw: 8.6° | Alerts: 1
2025-11-24 18:05:33,003 - INFO - Frame 364 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:33,004 - INFO - Frame 40 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:33,242 - INFO - Frame 530 | PERCLOS: 0.00 | Yaw: 8.8° | Alerts: 1
2025-11-24 18:05:33,461 - INFO - Frame 366 | PERCLOS: 0.00 | Yaw: 8.8° | Alerts: 0
2025-11-24 18:05:33,465 - INFO - Frame 42 | PERCLOS: 0.00 | Yaw: 8.8° | Alerts: 0
2025-11-24 18:05:33,467 - INFO - Frame 532 | PERCLOS: 0.00 | Yaw: 8.5° | Alerts: 1
2025-11-24 18:05:33,591 - INFO - Frame 44 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:33,591 - INFO - Frame 368 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:33,707 - INFO - Frame 370 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:33,708 - INFO - Frame 46 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:05:49,814 - INFO - Loading models...
2025-11-24 18:05:49,836 - INFO - ✓ YOLO ONNX loaded
2025-11-24 18:05:49,871 - INFO - ✓ MediaPipe Face Mesh loaded
2025-11-24 18:05:49,879 - INFO - ✓ MediaPipe Pose loaded (for smoke & seatbelt)
2025-11-24 18:05:49,881 - INFO - Video thread started with source: Camera
2025-11-24 18:05:50,002 - INFO - ✓ Camera 0 opened successfully
2025-11-24 18:05:50,535 - INFO - Frame 0 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 1
2025-11-24 18:05:50,769 - INFO - Frame 2 | PERCLOS: 0.00 | Yaw: -0.2° | Alerts: 1
2025-11-24 18:05:50,970 - INFO - Frame 4 | PERCLOS: 0.00 | Yaw: -0.2° | Alerts: 1
2025-11-24 18:05:51,259 - INFO - Frame 6 | PERCLOS: 0.00 | Yaw: 0.2° | Alerts: 1
2025-11-24 18:05:51,466 - INFO - Frame 8 | PERCLOS: 0.09 | Yaw: 0.7° | Alerts: 1
2025-11-24 18:05:51,669 - INFO - Frame 10 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 1
2025-11-24 18:05:51,972 - INFO - Frame 12 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 1
2025-11-24 18:05:52,180 - INFO - Frame 14 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 18:05:52,376 - INFO - Frame 16 | PERCLOS: 0.06 | Yaw: 3.6° | Alerts: 1
2025-11-24 18:05:52,647 - INFO - Frame 18 | PERCLOS: 0.00 | Yaw: 8.2° | Alerts: 1
2025-11-24 18:05:52,843 - INFO - Frame 20 | PERCLOS: 0.00 | Yaw: 9.9° | Alerts: 1
2025-11-24 18:05:53,039 - INFO - Frame 22 | PERCLOS: 0.00 | Yaw: 10.8° | Alerts: 1
2025-11-24 18:05:53,330 - INFO - Frame 24 | PERCLOS: 0.00 | Yaw: 11.2° | Alerts: 1
2025-11-24 18:05:53,606 - INFO - Frame 26 | PERCLOS: 0.00 | Yaw: 11.3° | Alerts: 1
2025-11-24 18:05:53,814 - INFO - Frame 28 | PERCLOS: 0.00 | Yaw: 11.3° | Alerts: 1
2025-11-24 18:05:54,112 - INFO - Frame 30 | PERCLOS: 0.00 | Yaw: 11.3° | Alerts: 1
2025-11-24 18:05:54,312 - INFO - Frame 32 | PERCLOS: 0.00 | Yaw: 11.4° | Alerts: 1
2025-11-24 18:05:54,507 - INFO - Frame 34 | PERCLOS: 0.00 | Yaw: 11.5° | Alerts: 1
2025-11-24 18:05:54,789 - INFO - Frame 36 | PERCLOS: 0.00 | Yaw: 11.3° | Alerts: 1
2025-11-24 18:05:54,985 - INFO - Frame 38 | PERCLOS: 0.00 | Yaw: 11.2° | Alerts: 1
2025-11-24 18:05:55,170 - INFO - Frame 40 | PERCLOS: 0.00 | Yaw: 10.9° | Alerts: 1
2025-11-24 18:05:55,452 - INFO - Frame 42 | PERCLOS: 0.00 | Yaw: 10.6° | Alerts: 1
2025-11-24 18:05:55,649 - INFO - Frame 44 | PERCLOS: 0.00 | Yaw: 9.5° | Alerts: 1
2025-11-24 18:05:55,844 - INFO - Frame 46 | PERCLOS: 0.00 | Yaw: 8.5° | Alerts: 1
2025-11-24 18:05:56,110 - INFO - Frame 48 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 1
2025-11-24 18:05:56,320 - INFO - Frame 50 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 1
2025-11-24 18:05:56,524 - INFO - Frame 52 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 1
2025-11-24 18:05:56,814 - INFO - Frame 54 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 1
2025-11-24 18:05:57,030 - INFO - Frame 56 | PERCLOS: 0.01 | Yaw: 6.0° | Alerts: 1
2025-11-24 18:05:57,228 - INFO - Frame 58 | PERCLOS: 0.00 | Yaw: 10.1° | Alerts: 1
2025-11-24 18:05:57,503 - INFO - Frame 60 | PERCLOS: 0.00 | Yaw: 11.3° | Alerts: 1
2025-11-24 18:05:57,643 - INFO - Frame 62 | PERCLOS: 0.00 | Yaw: 11.3° | Alerts: 1
2025-11-24 18:05:57,748 - INFO - Frame 64 | PERCLOS: 0.00 | Yaw: 11.3° | Alerts: 1
2025-11-24 18:05:57,779 - INFO - Video thread started with source: Camera
2025-11-24 18:05:57,781 - ERROR - ❌ No camera found!
2025-11-24 18:05:57,880 - INFO - Video thread started with source: Camera
2025-11-24 18:05:57,882 - ERROR - ❌ No camera found!
2025-11-24 18:05:57,985 - INFO - Video thread started with source: Camera
2025-11-24 18:05:57,986 - ERROR - ❌ No camera found!
2025-11-24 18:05:58,077 - INFO - Frame 66 | PERCLOS: 0.00 | Yaw: 11.2° | Alerts: 1
2025-11-24 18:05:58,079 - INFO - Video thread started with source: Camera
2025-11-24 18:05:58,080 - ERROR - ❌ No camera found!
2025-11-24 18:05:58,163 - INFO - Video thread started with source: Camera
2025-11-24 18:05:58,164 - ERROR - ❌ No camera found!
2025-11-24 18:05:58,197 - INFO - Frame 68 | PERCLOS: 0.00 | Yaw: 11.2° | Alerts: 1
2025-11-24 18:05:58,252 - INFO - Video thread started with source: Camera
2025-11-24 18:05:58,254 - ERROR - ❌ No camera found!
2025-11-24 18:05:58,350 - INFO - Video thread started with source: Camera
2025-11-24 18:05:58,351 - ERROR - ❌ No camera found!
2025-11-24 18:05:58,381 - INFO - Frame 70 | PERCLOS: 0.00 | Yaw: 11.2° | Alerts: 1
2025-11-24 18:05:58,450 - INFO - Video thread started with source: Camera
2025-11-24 18:05:58,451 - ERROR - ❌ No camera found!
2025-11-24 18:05:58,545 - INFO - Video thread started with source: Camera
2025-11-24 18:05:58,546 - ERROR - ❌ No camera found!
2025-11-24 18:05:58,642 - INFO - Video thread started with source: Camera
2025-11-24 18:05:58,643 - ERROR - ❌ No camera found!
2025-11-24 18:05:58,666 - INFO - Frame 72 | PERCLOS: 0.00 | Yaw: 11.0° | Alerts: 1
2025-11-24 18:05:58,738 - INFO - Video thread started with source: Camera
2025-11-24 18:05:58,739 - ERROR - ❌ No camera found!
2025-11-24 18:05:58,831 - INFO - Video thread started with source: Camera
2025-11-24 18:05:58,832 - ERROR - ❌ No camera found!
2025-11-24 18:05:58,862 - INFO - Frame 74 | PERCLOS: 0.00 | Yaw: 10.9° | Alerts: 1
2025-11-24 18:05:58,926 - INFO - Video thread started with source: Camera
2025-11-24 18:05:58,926 - ERROR - ❌ No camera found!
2025-11-24 18:05:59,022 - INFO - Video thread started with source: Camera
2025-11-24 18:05:59,023 - ERROR - ❌ No camera found!
2025-11-24 18:05:59,054 - INFO - Frame 76 | PERCLOS: 0.00 | Yaw: 11.0° | Alerts: 1
2025-11-24 18:05:59,117 - INFO - Video thread started with source: Camera
2025-11-24 18:05:59,119 - ERROR - ❌ No camera found!
2025-11-24 18:05:59,209 - INFO - Video thread started with source: Camera
2025-11-24 18:05:59,211 - ERROR - ❌ No camera found!
2025-11-24 18:05:59,312 - INFO - Video thread started with source: Camera
2025-11-24 18:05:59,313 - ERROR - ❌ No camera found!
2025-11-24 18:05:59,335 - INFO - Frame 78 | PERCLOS: 0.00 | Yaw: 10.9° | Alerts: 1
2025-11-24 18:05:59,413 - INFO - Video thread started with source: Camera
2025-11-24 18:05:59,414 - ERROR - ❌ No camera found!
2025-11-24 18:05:59,514 - INFO - Video thread started with source: Camera
2025-11-24 18:05:59,516 - ERROR - ❌ No camera found!
2025-11-24 18:05:59,544 - INFO - Frame 80 | PERCLOS: 0.00 | Yaw: 10.6° | Alerts: 1
2025-11-24 18:05:59,613 - INFO - Video thread started with source: Camera
2025-11-24 18:05:59,614 - ERROR - ❌ No camera found!
2025-11-24 18:05:59,708 - INFO - Video thread started with source: Camera
2025-11-24 18:05:59,709 - ERROR - ❌ No camera found!
2025-11-24 18:05:59,739 - INFO - Frame 82 | PERCLOS: 0.00 | Yaw: 10.0° | Alerts: 1
2025-11-24 18:05:59,805 - INFO - Video thread started with source: Camera
2025-11-24 18:05:59,806 - ERROR - ❌ No camera found!
2025-11-24 18:05:59,899 - INFO - Video thread started with source: Camera
2025-11-24 18:05:59,902 - ERROR - ❌ No camera found!
2025-11-24 18:05:59,995 - INFO - Video thread started with source: Camera
2025-11-24 18:05:59,996 - ERROR - ❌ No camera found!
2025-11-24 18:06:00,016 - INFO - Frame 84 | PERCLOS: 0.01 | Yaw: 10.3° | Alerts: 1
2025-11-24 18:06:00,092 - INFO - Video thread started with source: Camera
2025-11-24 18:06:00,093 - ERROR - ❌ No camera found!
2025-11-24 18:06:00,186 - INFO - Video thread started with source: Camera
2025-11-24 18:06:00,187 - ERROR - ❌ No camera found!
2025-11-24 18:06:00,217 - INFO - Frame 86 | PERCLOS: 0.00 | Yaw: 10.5° | Alerts: 1
2025-11-24 18:06:00,282 - INFO - Video thread started with source: Camera
2025-11-24 18:06:00,283 - ERROR - ❌ No camera found!
2025-11-24 18:06:00,377 - INFO - Video thread started with source: Camera
2025-11-24 18:06:00,378 - ERROR - ❌ No camera found!
2025-11-24 18:06:00,409 - INFO - Frame 88 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-24 18:06:00,473 - INFO - Video thread started with source: Camera
2025-11-24 18:06:00,473 - ERROR - ❌ No camera found!
2025-11-24 18:06:00,566 - INFO - Video thread started with source: Camera
2025-11-24 18:06:00,567 - ERROR - ❌ No camera found!
2025-11-24 18:06:00,661 - INFO - Video thread started with source: Camera
2025-11-24 18:06:00,661 - ERROR - ❌ No camera found!
2025-11-24 18:06:00,682 - INFO - Frame 90 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 1
2025-11-24 18:06:00,755 - INFO - Video thread started with source: Camera
2025-11-24 18:06:00,756 - ERROR - ❌ No camera found!
2025-11-24 18:06:00,850 - INFO - Video thread started with source: Camera
2025-11-24 18:06:00,851 - ERROR - ❌ No camera found!
2025-11-24 18:06:00,880 - INFO - Frame 92 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 1
2025-11-24 18:06:00,945 - INFO - Video thread started with source: Camera
2025-11-24 18:06:00,946 - ERROR - ❌ No camera found!
2025-11-24 18:06:01,039 - INFO - Video thread started with source: Camera
2025-11-24 18:06:01,040 - ERROR - ❌ No camera found!
2025-11-24 18:06:01,071 - INFO - Frame 94 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 1
2025-11-24 18:06:01,135 - INFO - Video thread started with source: Camera
2025-11-24 18:06:01,136 - ERROR - ❌ No camera found!
2025-11-24 18:06:01,230 - INFO - Video thread started with source: Camera
2025-11-24 18:06:01,231 - ERROR - ❌ No camera found!
2025-11-24 18:06:01,334 - INFO - Video thread started with source: Camera
2025-11-24 18:06:01,335 - ERROR - ❌ No camera found!
2025-11-24 18:06:01,357 - INFO - Frame 96 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 1
2025-11-24 18:06:01,429 - INFO - Video thread started with source: Camera
2025-11-24 18:06:01,430 - ERROR - ❌ No camera found!
2025-11-24 18:06:01,528 - INFO - Video thread started with source: Camera
2025-11-24 18:06:01,529 - ERROR - ❌ No camera found!
2025-11-24 18:06:01,557 - INFO - Frame 98 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 1
2025-11-24 18:06:01,624 - INFO - Video thread started with source: Camera
2025-11-24 18:06:01,625 - ERROR - ❌ No camera found!
2025-11-24 18:06:01,720 - INFO - Video thread started with source: Camera
2025-11-24 18:06:01,721 - ERROR - ❌ No camera found!
2025-11-24 18:06:01,750 - INFO - Frame 100 | PERCLOS: 0.15 | Yaw: 1.8° | Alerts: 1
2025-11-24 18:06:01,824 - INFO - Video thread started with source: Camera
2025-11-24 18:06:01,825 - ERROR - ❌ No camera found!
2025-11-24 18:06:01,911 - INFO - Video thread started with source: Camera
2025-11-24 18:06:01,912 - ERROR - ❌ No camera found!
2025-11-24 18:06:02,000 - INFO - Video thread started with source: Camera
2025-11-24 18:06:02,001 - ERROR - ❌ No camera found!
2025-11-24 18:06:02,019 - INFO - Frame 102 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-24 18:06:02,109 - INFO - Video thread started with source: Camera
2025-11-24 18:06:02,109 - ERROR - ❌ No camera found!
2025-11-24 18:06:02,217 - INFO - Video thread started with source: Camera
2025-11-24 18:06:02,219 - ERROR - ❌ No camera found!
2025-11-24 18:06:02,249 - INFO - Frame 104 | PERCLOS: 0.02 | Yaw: 5.9° | Alerts: 1
2025-11-24 18:06:02,319 - INFO - Video thread started with source: Camera
2025-11-24 18:06:02,320 - ERROR - ❌ No camera found!
2025-11-24 18:06:02,414 - INFO - Video thread started with source: Camera
2025-11-24 18:06:02,415 - ERROR - ❌ No camera found!
2025-11-24 18:06:02,446 - INFO - Frame 106 | PERCLOS: 0.00 | Yaw: 6.5° | Alerts: 1
2025-11-24 18:06:02,506 - INFO - Video thread started with source: Camera
2025-11-24 18:06:02,507 - ERROR - ❌ No camera found!
2025-11-24 18:06:02,593 - INFO - Video thread started with source: Camera
2025-11-24 18:06:02,594 - ERROR - ❌ No camera found!
2025-11-24 18:06:02,683 - INFO - Video thread started with source: Camera
2025-11-24 18:06:02,684 - ERROR - ❌ No camera found!
2025-11-24 18:06:02,704 - INFO - Frame 108 | PERCLOS: 0.00 | Yaw: 6.4° | Alerts: 1
2025-11-24 18:06:02,774 - INFO - Video thread started with source: Camera
2025-11-24 18:06:02,775 - ERROR - ❌ No camera found!
2025-11-24 18:06:02,864 - INFO - Video thread started with source: Camera
2025-11-24 18:06:02,866 - ERROR - ❌ No camera found!
2025-11-24 18:06:02,895 - INFO - Frame 110 | PERCLOS: 0.00 | Yaw: 6.1° | Alerts: 1
2025-11-24 18:06:02,956 - INFO - Video thread started with source: Camera
2025-11-24 18:06:02,957 - ERROR - ❌ No camera found!
2025-11-24 18:06:03,044 - INFO - Video thread started with source: Camera
2025-11-24 18:06:03,045 - ERROR - ❌ No camera found!
2025-11-24 18:06:03,078 - INFO - Frame 112 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 1
2025-11-24 18:06:03,133 - INFO - Video thread started with source: Camera
2025-11-24 18:06:03,134 - ERROR - ❌ No camera found!
2025-11-24 18:06:03,219 - INFO - Video thread started with source: Camera
2025-11-24 18:06:03,220 - ERROR - ❌ No camera found!
2025-11-24 18:06:03,312 - INFO - Video thread started with source: Camera
2025-11-24 18:06:03,313 - ERROR - ❌ No camera found!
2025-11-24 18:06:03,333 - INFO - Frame 114 | PERCLOS: 0.68 | Yaw: 6.6° | Alerts: 2
2025-11-24 18:06:03,402 - INFO - Video thread started with source: Camera
2025-11-24 18:06:03,403 - ERROR - ❌ No camera found!
2025-11-24 18:09:08,613 - INFO - Loading models...
2025-11-24 18:09:08,636 - INFO - ✓ YOLO ONNX loaded
2025-11-24 18:09:08,671 - INFO - ✓ MediaPipe Face Mesh loaded
2025-11-24 18:09:08,678 - INFO - ✓ MediaPipe Pose loaded (for smoke & seatbelt)
2025-11-24 18:09:08,681 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:08,797 - INFO - ✓ Camera 0 opened successfully
2025-11-24 18:09:09,182 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:09,185 - ERROR - ❌ No camera found!
2025-11-24 18:09:09,339 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:09,340 - ERROR - ❌ No camera found!
2025-11-24 18:09:09,353 - INFO - Frame 0 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 1
2025-11-24 18:09:09,481 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:09,483 - ERROR - ❌ No camera found!
2025-11-24 18:09:09,629 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:09,630 - ERROR - ❌ No camera found!
2025-11-24 18:09:09,660 - INFO - Frame 2 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 1
2025-11-24 18:09:09,782 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:09,784 - ERROR - ❌ No camera found!
2025-11-24 18:09:09,936 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:09,940 - ERROR - ❌ No camera found!
2025-11-24 18:09:09,964 - INFO - Frame 4 | PERCLOS: 0.00 | Yaw: -0.2° | Alerts: 1
2025-11-24 18:09:10,095 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:10,099 - ERROR - ❌ No camera found!
2025-11-24 18:09:10,253 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:10,254 - ERROR - ❌ No camera found!
2025-11-24 18:09:10,410 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:10,410 - INFO - Frame 6 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 1
2025-11-24 18:09:10,411 - ERROR - ❌ No camera found!
2025-11-24 18:09:10,550 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:10,551 - ERROR - ❌ No camera found!
2025-11-24 18:09:10,699 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:10,701 - ERROR - ❌ No camera found!
2025-11-24 18:09:10,732 - INFO - Frame 8 | PERCLOS: 0.00 | Yaw: -0.8° | Alerts: 1
2025-11-24 18:09:10,844 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:10,848 - ERROR - ❌ No camera found!
2025-11-24 18:09:11,019 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:11,019 - ERROR - ❌ No camera found!
2025-11-24 18:09:11,023 - INFO - Frame 10 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 1
2025-11-24 18:09:11,165 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:11,168 - ERROR - ❌ No camera found!
2025-11-24 18:09:11,312 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:11,314 - ERROR - ❌ No camera found!
2025-11-24 18:09:11,459 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:11,463 - ERROR - ❌ No camera found!
2025-11-24 18:09:11,481 - INFO - Frame 12 | PERCLOS: 0.54 | Yaw: -0.1° | Alerts: 2
2025-11-24 18:09:11,609 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:11,610 - ERROR - ❌ No camera found!
2025-11-24 18:09:11,767 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:11,768 - ERROR - ❌ No camera found!
2025-11-24 18:09:11,799 - INFO - Frame 14 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 1
2025-11-24 18:09:11,923 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:11,926 - ERROR - ❌ No camera found!
2025-11-24 18:09:12,095 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:12,098 - ERROR - ❌ No camera found!
2025-11-24 18:09:12,101 - INFO - Frame 16 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 1
2025-11-24 18:09:12,288 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:12,289 - ERROR - ❌ No camera found!
2025-11-24 18:09:12,469 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:12,472 - ERROR - ❌ No camera found!
2025-11-24 18:09:12,627 - INFO - Frame 18 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 1
2025-11-24 18:09:12,628 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:12,629 - ERROR - ❌ No camera found!
2025-11-24 18:09:12,780 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:12,781 - ERROR - ❌ No camera found!
2025-11-24 18:09:12,942 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:12,943 - ERROR - ❌ No camera found!
2025-11-24 18:09:12,967 - INFO - Frame 20 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 1
2025-11-24 18:09:13,103 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:13,106 - ERROR - ❌ No camera found!
2025-11-24 18:09:13,257 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:13,258 - ERROR - ❌ No camera found!
2025-11-24 18:09:13,292 - INFO - Frame 22 | PERCLOS: 0.00 | Yaw: 0.2° | Alerts: 1
2025-11-24 18:09:13,414 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:13,418 - ERROR - ❌ No camera found!
2025-11-24 18:09:13,569 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:13,573 - ERROR - ❌ No camera found!
2025-11-24 18:09:13,738 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:13,744 - ERROR - ❌ No camera found!
2025-11-24 18:09:13,759 - INFO - Frame 24 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-24 18:09:13,902 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:13,907 - ERROR - ❌ No camera found!
2025-11-24 18:09:14,065 - INFO - Frame 26 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:09:14,070 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:14,072 - ERROR - ❌ No camera found!
2025-11-24 18:09:14,230 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:14,233 - ERROR - ❌ No camera found!
2025-11-24 18:09:14,386 - INFO - Frame 28 | PERCLOS: 0.00 | Yaw: 5.9° | Alerts: 0
2025-11-24 18:09:14,390 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:14,394 - ERROR - ❌ No camera found!
2025-11-24 18:09:14,545 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:14,546 - ERROR - ❌ No camera found!
2025-11-24 18:09:14,698 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:14,700 - ERROR - ❌ No camera found!
2025-11-24 18:09:14,723 - INFO - Frame 30 | PERCLOS: 0.00 | Yaw: 7.4° | Alerts: 1
2025-11-24 18:09:14,852 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:14,853 - ERROR - ❌ No camera found!
2025-11-24 18:09:15,008 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:15,008 - INFO - Frame 32 | PERCLOS: 0.00 | Yaw: 7.4° | Alerts: 1
2025-11-24 18:09:15,010 - ERROR - ❌ No camera found!
2025-11-24 18:09:15,165 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:15,167 - ERROR - ❌ No camera found!
2025-11-24 18:09:15,319 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:15,321 - ERROR - ❌ No camera found!
2025-11-24 18:09:15,345 - INFO - Frame 34 | PERCLOS: 0.00 | Yaw: 7.2° | Alerts: 1
2025-11-24 18:09:15,481 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:15,486 - ERROR - ❌ No camera found!
2025-11-24 18:09:15,634 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:15,638 - ERROR - ❌ No camera found!
2025-11-24 18:09:15,798 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:15,798 - ERROR - ❌ No camera found!
2025-11-24 18:09:15,814 - INFO - Frame 36 | PERCLOS: 0.00 | Yaw: 7.8° | Alerts: 1
2025-11-24 18:09:15,953 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:15,955 - ERROR - ❌ No camera found!
2025-11-24 18:09:16,112 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:16,114 - ERROR - ❌ No camera found!
2025-11-24 18:09:16,114 - INFO - Frame 38 | PERCLOS: 0.00 | Yaw: 7.6° | Alerts: 1
2025-11-24 18:09:16,261 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:16,264 - ERROR - ❌ No camera found!
2025-11-24 18:09:16,300 - INFO - Frame 40 | PERCLOS: 0.00 | Yaw: 7.4° | Alerts: 1
2025-11-24 18:09:16,421 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:16,423 - ERROR - ❌ No camera found!
2025-11-24 18:09:16,581 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:16,583 - ERROR - ❌ No camera found!
2025-11-24 18:09:16,741 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:16,742 - ERROR - ❌ No camera found!
2025-11-24 18:09:16,763 - INFO - Frame 42 | PERCLOS: 0.00 | Yaw: 7.3° | Alerts: 1
2025-11-24 18:09:16,900 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:16,902 - ERROR - ❌ No camera found!
2025-11-24 18:09:17,059 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:17,062 - ERROR - ❌ No camera found!
2025-11-24 18:09:17,093 - INFO - Frame 44 | PERCLOS: 0.00 | Yaw: 7.0° | Alerts: 1
2025-11-24 18:09:17,219 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:17,220 - ERROR - ❌ No camera found!
2025-11-24 18:09:17,375 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:17,378 - ERROR - ❌ No camera found!
2025-11-24 18:09:17,402 - INFO - Frame 46 | PERCLOS: 0.00 | Yaw: 7.0° | Alerts: 1
2025-11-24 18:09:17,527 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:17,531 - ERROR - ❌ No camera found!
2025-11-24 18:09:17,682 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:17,685 - ERROR - ❌ No camera found!
2025-11-24 18:09:17,846 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:17,847 - ERROR - ❌ No camera found!
2025-11-24 18:09:17,862 - INFO - Frame 48 | PERCLOS: 0.00 | Yaw: 6.7° | Alerts: 1
2025-11-24 18:09:18,008 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:18,009 - ERROR - ❌ No camera found!
2025-11-24 18:09:18,165 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:18,170 - ERROR - ❌ No camera found!
2025-11-24 18:09:18,190 - INFO - Frame 50 | PERCLOS: 0.00 | Yaw: 6.7° | Alerts: 1
2025-11-24 18:09:18,310 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:18,311 - ERROR - ❌ No camera found!
2025-11-24 18:09:18,462 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:18,464 - ERROR - ❌ No camera found!
2025-11-24 18:09:18,486 - INFO - Frame 52 | PERCLOS: 0.00 | Yaw: 6.6° | Alerts: 1
2025-11-24 18:09:18,607 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:18,611 - ERROR - ❌ No camera found!
2025-11-24 18:09:18,837 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:18,843 - ERROR - ❌ No camera found!
2025-11-24 18:09:18,975 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:18,976 - ERROR - ❌ No camera found!
2025-11-24 18:09:18,992 - INFO - Frame 54 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 18:09:19,158 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:19,159 - ERROR - ❌ No camera found!
2025-11-24 18:09:19,317 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:19,319 - ERROR - ❌ No camera found!
2025-11-24 18:09:19,342 - INFO - Frame 56 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 1
2025-11-24 18:09:19,484 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:19,490 - ERROR - ❌ No camera found!
2025-11-24 18:09:19,658 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:19,659 - ERROR - ❌ No camera found!
2025-11-24 18:09:19,681 - INFO - Frame 58 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 18:09:19,814 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:19,815 - ERROR - ❌ No camera found!
2025-11-24 18:09:19,995 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:19,997 - ERROR - ❌ No camera found!
2025-11-24 18:09:20,186 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:20,188 - ERROR - ❌ No camera found!
2025-11-24 18:09:20,344 - INFO - Frame 60 | PERCLOS: 0.00 | Yaw: 4.9° | Alerts: 1
2025-11-24 18:09:20,351 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:20,352 - ERROR - ❌ No camera found!
2025-11-24 18:09:20,506 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:20,510 - ERROR - ❌ No camera found!
2025-11-24 18:09:20,664 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:20,666 - ERROR - ❌ No camera found!
2025-11-24 18:09:20,666 - INFO - Frame 62 | PERCLOS: 0.00 | Yaw: 5.4° | Alerts: 1
2025-11-24 18:09:20,818 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:20,819 - ERROR - ❌ No camera found!
2025-11-24 18:09:20,984 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:20,987 - ERROR - ❌ No camera found!
2025-11-24 18:09:21,009 - INFO - Frame 64 | PERCLOS: 0.00 | Yaw: 5.4° | Alerts: 1
2025-11-24 18:09:21,154 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:21,158 - ERROR - ❌ No camera found!
2025-11-24 18:09:21,314 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:21,319 - ERROR - ❌ No camera found!
2025-11-24 18:09:21,476 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:21,477 - ERROR - ❌ No camera found!
2025-11-24 18:09:21,499 - INFO - Frame 66 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-24 18:09:21,635 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:21,638 - ERROR - ❌ No camera found!
2025-11-24 18:09:21,788 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:21,790 - ERROR - ❌ No camera found!
2025-11-24 18:09:21,813 - INFO - Frame 68 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 1
2025-11-24 18:09:21,940 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:21,943 - ERROR - ❌ No camera found!
2025-11-24 18:09:22,101 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:22,101 - INFO - Frame 70 | PERCLOS: 0.00 | Yaw: 7.1° | Alerts: 1
2025-11-24 18:09:22,103 - ERROR - ❌ No camera found!
2025-11-24 18:09:22,251 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:22,252 - ERROR - ❌ No camera found!
2025-11-24 18:09:22,259 - INFO - Frame 72 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:09:22,403 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:22,421 - ERROR - ❌ No camera found!
2025-11-24 18:09:22,597 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:22,599 - ERROR - ❌ No camera found!
2025-11-24 18:09:22,625 - INFO - Frame 74 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 0
2025-11-24 18:09:22,756 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:22,758 - ERROR - ❌ No camera found!
2025-11-24 18:09:22,907 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:22,909 - ERROR - ❌ No camera found!
2025-11-24 18:09:22,931 - INFO - Frame 76 | PERCLOS: 0.13 | Yaw: 4.5° | Alerts: 0
2025-11-24 18:09:23,073 - INFO - Predictions disabled
2025-11-24 18:09:23,075 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:23,077 - ERROR - ❌ No camera found!
2025-11-24 18:09:23,298 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:23,299 - ERROR - ❌ No camera found!
2025-11-24 18:09:23,446 - INFO - Frame 78 | PERCLOS: 0.00 | Yaw: 7.5° | Alerts: 1
2025-11-24 18:09:23,453 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:23,455 - ERROR - ❌ No camera found!
2025-11-24 18:09:23,602 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:23,603 - ERROR - ❌ No camera found!
2025-11-24 18:09:23,759 - INFO - Frame 80 | PERCLOS: 0.00 | Yaw: 8.1° | Alerts: 1
2025-11-24 18:09:23,759 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:23,760 - ERROR - ❌ No camera found!
2025-11-24 18:09:23,915 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:23,918 - ERROR - ❌ No camera found!
2025-11-24 18:09:23,952 - INFO - Frame 82 | PERCLOS: 0.00 | Yaw: 8.0° | Alerts: 1
2025-11-24 18:09:24,091 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:24,094 - ERROR - ❌ No camera found!
2025-11-24 18:09:24,255 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:24,262 - ERROR - ❌ No camera found!
2025-11-24 18:09:24,414 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:24,416 - ERROR - ❌ No camera found!
2025-11-24 18:09:24,431 - INFO - Frame 84 | PERCLOS: 0.00 | Yaw: 7.5° | Alerts: 1
2025-11-24 18:09:24,573 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:24,576 - ERROR - ❌ No camera found!
2025-11-24 18:09:24,740 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:24,742 - ERROR - ❌ No camera found!
2025-11-24 18:09:24,764 - INFO - Frame 86 | PERCLOS: 0.00 | Yaw: 7.0° | Alerts: 1
2025-11-24 18:09:24,893 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:24,895 - ERROR - ❌ No camera found!
2025-11-24 18:09:25,058 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:25,059 - ERROR - ❌ No camera found!
2025-11-24 18:09:25,079 - INFO - Frame 88 | PERCLOS: 0.00 | Yaw: 5.9° | Alerts: 1
2025-11-24 18:09:25,207 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:25,211 - ERROR - ❌ No camera found!
2025-11-24 18:09:25,359 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:25,364 - ERROR - ❌ No camera found!
2025-11-24 18:09:25,522 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:25,524 - ERROR - ❌ No camera found!
2025-11-24 18:09:25,538 - INFO - Frame 90 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 18:09:25,678 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:25,680 - ERROR - ❌ No camera found!
2025-11-24 18:09:25,843 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:25,848 - ERROR - ❌ No camera found!
2025-11-24 18:09:26,005 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:26,006 - ERROR - ❌ No camera found!
2025-11-24 18:09:26,007 - INFO - Frame 92 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 1
2025-11-24 18:09:26,153 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:26,158 - ERROR - ❌ No camera found!
2025-11-24 18:09:26,312 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:26,314 - ERROR - ❌ No camera found!
2025-11-24 18:09:26,346 - INFO - Frame 94 | PERCLOS: 0.00 | Yaw: 6.4° | Alerts: 1
2025-11-24 18:09:26,484 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:26,486 - ERROR - ❌ No camera found!
2025-11-24 18:09:26,581 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:26,582 - ERROR - ❌ No camera found!
2025-11-24 18:09:26,685 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:26,686 - ERROR - ❌ No camera found!
2025-11-24 18:09:26,706 - INFO - Frame 96 | PERCLOS: 0.00 | Yaw: 6.7° | Alerts: 1
2025-11-24 18:09:26,783 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:26,784 - ERROR - ❌ No camera found!
2025-11-24 18:09:26,792 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:26,794 - ERROR - ❌ No camera found!
2025-11-24 18:09:26,963 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:26,963 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:26,964 - ERROR - ❌ No camera found!
2025-11-24 18:09:26,965 - ERROR - ❌ No camera found!
2025-11-24 18:09:26,991 - INFO - Frame 98 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-24 18:09:27,126 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:27,127 - ERROR - ❌ No camera found!
2025-11-24 18:09:27,127 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:27,128 - ERROR - ❌ No camera found!
2025-11-24 18:09:27,270 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:27,272 - ERROR - ❌ No camera found!
2025-11-24 18:09:27,276 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:27,277 - ERROR - ❌ No camera found!
2025-11-24 18:09:27,297 - INFO - Frame 100 | PERCLOS: 0.00 | Yaw: 4.7° | Alerts: 1
2025-11-24 18:09:27,421 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:27,424 - ERROR - ❌ No camera found!
2025-11-24 18:09:27,424 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:27,425 - ERROR - ❌ No camera found!
2025-11-24 18:09:27,580 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:27,581 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:27,582 - ERROR - ❌ No camera found!
2025-11-24 18:09:27,582 - ERROR - ❌ No camera found!
2025-11-24 18:09:27,724 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:27,724 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:27,725 - ERROR - ❌ No camera found!
2025-11-24 18:09:27,725 - ERROR - ❌ No camera found!
2025-11-24 18:09:27,743 - INFO - Frame 102 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 18:09:27,883 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:27,886 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:27,887 - ERROR - ❌ No camera found!
2025-11-24 18:09:27,887 - ERROR - ❌ No camera found!
2025-11-24 18:09:28,061 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:28,061 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:28,063 - ERROR - ❌ No camera found!
2025-11-24 18:09:28,063 - ERROR - ❌ No camera found!
2025-11-24 18:09:28,083 - INFO - Frame 104 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-24 18:09:28,220 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:28,222 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:28,223 - ERROR - ❌ No camera found!
2025-11-24 18:09:28,223 - ERROR - ❌ No camera found!
2025-11-24 18:09:28,388 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:28,391 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:28,391 - ERROR - ❌ No camera found!
2025-11-24 18:09:28,395 - ERROR - ❌ No camera found!
2025-11-24 18:09:28,414 - INFO - Frame 106 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 1
2025-11-24 18:09:28,536 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:28,538 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:28,539 - ERROR - ❌ No camera found!
2025-11-24 18:09:28,540 - ERROR - ❌ No camera found!
2025-11-24 18:09:28,696 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:28,696 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:28,697 - ERROR - ❌ No camera found!
2025-11-24 18:09:28,698 - ERROR - ❌ No camera found!
2025-11-24 18:09:28,845 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:28,845 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:28,846 - ERROR - ❌ No camera found!
2025-11-24 18:09:28,846 - ERROR - ❌ No camera found!
2025-11-24 18:09:28,864 - INFO - Frame 108 | PERCLOS: 0.00 | Yaw: 7.9° | Alerts: 1
2025-11-24 18:09:29,010 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:29,012 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:29,076 - ERROR - ❌ No camera found!
2025-11-24 18:09:29,077 - ERROR - ❌ No camera found!
2025-11-24 18:09:29,178 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:29,178 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:29,180 - ERROR - ❌ No camera found!
2025-11-24 18:09:29,180 - ERROR - ❌ No camera found!
2025-11-24 18:09:29,218 - INFO - Frame 110 | PERCLOS: 0.00 | Yaw: 7.7° | Alerts: 1
2025-11-24 18:09:29,342 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:29,342 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:29,343 - ERROR - ❌ No camera found!
2025-11-24 18:09:29,343 - ERROR - ❌ No camera found!
2025-11-24 18:09:29,489 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:29,492 - ERROR - ❌ No camera found!
2025-11-24 18:09:29,492 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:29,496 - ERROR - ❌ No camera found!
2025-11-24 18:09:29,520 - INFO - Frame 112 | PERCLOS: 0.00 | Yaw: 7.8° | Alerts: 1
2025-11-24 18:09:29,655 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:29,657 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:29,657 - ERROR - ❌ No camera found!
2025-11-24 18:09:29,658 - ERROR - ❌ No camera found!
2025-11-24 18:09:29,818 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:29,819 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:29,819 - ERROR - ❌ No camera found!
2025-11-24 18:09:29,820 - ERROR - ❌ No camera found!
2025-11-24 18:09:29,965 - INFO - Frame 114 | PERCLOS: 0.00 | Yaw: 8.1° | Alerts: 1
2025-11-24 18:09:29,969 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:29,969 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:29,970 - ERROR - ❌ No camera found!
2025-11-24 18:09:29,971 - ERROR - ❌ No camera found!
2025-11-24 18:09:30,119 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:30,120 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:30,121 - ERROR - ❌ No camera found!
2025-11-24 18:09:30,121 - ERROR - ❌ No camera found!
2025-11-24 18:09:30,156 - INFO - Frame 116 | PERCLOS: 0.00 | Yaw: 8.4° | Alerts: 1
2025-11-24 18:09:30,277 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:30,278 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:30,278 - ERROR - ❌ No camera found!
2025-11-24 18:09:30,279 - ERROR - ❌ No camera found!
2025-11-24 18:09:30,431 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:30,433 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:30,434 - ERROR - ❌ No camera found!
2025-11-24 18:09:30,435 - ERROR - ❌ No camera found!
2025-11-24 18:09:30,435 - INFO - Frame 118 | PERCLOS: 0.00 | Yaw: 8.2° | Alerts: 1
2025-11-24 18:09:30,588 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:30,590 - ERROR - ❌ No camera found!
2025-11-24 18:09:30,591 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:30,592 - ERROR - ❌ No camera found!
2025-11-24 18:09:30,783 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:30,786 - ERROR - ❌ No camera found!
2025-11-24 18:09:30,787 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:30,792 - ERROR - ❌ No camera found!
2025-11-24 18:09:30,940 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:30,941 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:30,941 - ERROR - ❌ No camera found!
2025-11-24 18:09:30,942 - ERROR - ❌ No camera found!
2025-11-24 18:09:30,957 - INFO - Frame 120 | PERCLOS: 0.00 | Yaw: 6.7° | Alerts: 1
2025-11-24 18:09:31,100 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:31,101 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:31,102 - ERROR - ❌ No camera found!
2025-11-24 18:09:31,102 - ERROR - ❌ No camera found!
2025-11-24 18:09:31,252 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:31,254 - INFO - Frame 122 | PERCLOS: 0.00 | Yaw: 6.6° | Alerts: 1
2025-11-24 18:09:31,255 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:31,258 - ERROR - ❌ No camera found!
2025-11-24 18:09:31,258 - ERROR - ❌ No camera found!
2025-11-24 18:09:31,435 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:31,436 - ERROR - ❌ No camera found!
2025-11-24 18:09:31,437 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:31,439 - ERROR - ❌ No camera found!
2025-11-24 18:09:31,598 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:31,601 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:31,602 - ERROR - ❌ No camera found!
2025-11-24 18:09:31,602 - ERROR - ❌ No camera found!
2025-11-24 18:09:31,625 - INFO - Frame 124 | PERCLOS: 0.00 | Yaw: 6.6° | Alerts: 1
2025-11-24 18:09:31,748 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:31,749 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:31,750 - ERROR - ❌ No camera found!
2025-11-24 18:09:31,750 - ERROR - ❌ No camera found!
2025-11-24 18:09:31,908 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:31,911 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:31,913 - ERROR - ❌ No camera found!
2025-11-24 18:09:31,913 - ERROR - ❌ No camera found!
2025-11-24 18:09:32,059 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:32,061 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:32,062 - ERROR - ❌ No camera found!
2025-11-24 18:09:32,063 - ERROR - ❌ No camera found!
2025-11-24 18:09:32,080 - INFO - Frame 126 | PERCLOS: 0.00 | Yaw: 6.6° | Alerts: 1
2025-11-24 18:09:32,216 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:32,218 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:32,219 - ERROR - ❌ No camera found!
2025-11-24 18:09:32,219 - ERROR - ❌ No camera found!
2025-11-24 18:09:32,376 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:32,436 - ERROR - ❌ No camera found!
2025-11-24 18:09:32,442 - INFO - Predictions disabled
2025-11-24 18:09:32,443 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:32,444 - ERROR - ❌ No camera found!
2025-11-24 18:09:32,444 - INFO - Frame 128 | PERCLOS: 0.00 | Yaw: 6.9° | Alerts: 1
2025-11-24 18:09:32,603 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:32,603 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:32,605 - ERROR - ❌ No camera found!
2025-11-24 18:09:32,605 - ERROR - ❌ No camera found!
2025-11-24 18:09:32,766 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:32,766 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:32,767 - INFO - Frame 130 | PERCLOS: 0.00 | Yaw: 7.4° | Alerts: 1
2025-11-24 18:09:32,768 - ERROR - ❌ No camera found!
2025-11-24 18:09:32,768 - ERROR - ❌ No camera found!
2025-11-24 18:09:32,917 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:32,917 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:32,919 - ERROR - ❌ No camera found!
2025-11-24 18:09:32,919 - ERROR - ❌ No camera found!
2025-11-24 18:09:33,066 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:33,066 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:33,067 - ERROR - ❌ No camera found!
2025-11-24 18:09:33,068 - ERROR - ❌ No camera found!
2025-11-24 18:09:33,085 - INFO - Frame 132 | PERCLOS: 0.00 | Yaw: 7.5° | Alerts: 1
2025-11-24 18:09:33,217 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:33,218 - ERROR - ❌ No camera found!
2025-11-24 18:09:33,220 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:33,220 - ERROR - ❌ No camera found!
2025-11-24 18:09:33,374 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:33,375 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:33,375 - ERROR - ❌ No camera found!
2025-11-24 18:09:33,376 - ERROR - ❌ No camera found!
2025-11-24 18:09:33,401 - INFO - Frame 134 | PERCLOS: 0.00 | Yaw: 7.4° | Alerts: 1
2025-11-24 18:09:33,532 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:33,533 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:33,533 - ERROR - ❌ No camera found!
2025-11-24 18:09:33,534 - ERROR - ❌ No camera found!
2025-11-24 18:09:33,681 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:33,683 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:33,683 - ERROR - ❌ No camera found!
2025-11-24 18:09:33,684 - ERROR - ❌ No camera found!
2025-11-24 18:09:33,708 - INFO - Frame 136 | PERCLOS: 0.00 | Yaw: 7.4° | Alerts: 1
2025-11-24 18:09:33,908 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:33,908 - INFO - Predictions enabled
2025-11-24 18:09:33,909 - ERROR - ❌ No camera found!
2025-11-24 18:09:33,910 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:33,913 - ERROR - ❌ No camera found!
2025-11-24 18:09:34,018 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:34,021 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:34,022 - ERROR - ❌ No camera found!
2025-11-24 18:09:34,022 - ERROR - ❌ No camera found!
2025-11-24 18:09:34,178 - INFO - Frame 138 | PERCLOS: 0.00 | Yaw: 7.5° | Alerts: 1
2025-11-24 18:09:34,182 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:34,183 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:34,183 - ERROR - ❌ No camera found!
2025-11-24 18:09:34,183 - ERROR - ❌ No camera found!
2025-11-24 18:09:34,331 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:34,333 - ERROR - ❌ No camera found!
2025-11-24 18:09:34,333 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:34,334 - ERROR - ❌ No camera found!
2025-11-24 18:09:34,368 - INFO - Frame 140 | PERCLOS: 0.00 | Yaw: 7.3° | Alerts: 1
2025-11-24 18:09:34,488 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:34,488 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:34,489 - ERROR - ❌ No camera found!
2025-11-24 18:09:34,490 - ERROR - ❌ No camera found!
2025-11-24 18:09:34,654 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:34,654 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:34,655 - ERROR - ❌ No camera found!
2025-11-24 18:09:34,656 - ERROR - ❌ No camera found!
2025-11-24 18:09:34,678 - INFO - Frame 142 | PERCLOS: 0.00 | Yaw: 7.6° | Alerts: 1
2025-11-24 18:09:34,813 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:34,814 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:34,814 - ERROR - ❌ No camera found!
2025-11-24 18:09:34,815 - ERROR - ❌ No camera found!
2025-11-24 18:09:34,958 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:34,961 - ERROR - ❌ No camera found!
2025-11-24 18:09:34,961 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:34,962 - ERROR - ❌ No camera found!
2025-11-24 18:09:35,135 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:35,135 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:35,137 - ERROR - ❌ No camera found!
2025-11-24 18:09:35,137 - ERROR - ❌ No camera found!
2025-11-24 18:09:35,154 - INFO - Frame 144 | PERCLOS: 0.00 | Yaw: 7.4° | Alerts: 1
2025-11-24 18:09:35,291 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:35,294 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:35,294 - ERROR - ❌ No camera found!
2025-11-24 18:09:35,296 - ERROR - ❌ No camera found!
2025-11-24 18:09:35,449 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:35,449 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:35,450 - ERROR - ❌ No camera found!
2025-11-24 18:09:35,450 - ERROR - ❌ No camera found!
2025-11-24 18:09:35,477 - INFO - Frame 146 | PERCLOS: 0.00 | Yaw: 7.5° | Alerts: 1
2025-11-24 18:09:35,619 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:35,619 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:35,620 - ERROR - ❌ No camera found!
2025-11-24 18:09:35,620 - ERROR - ❌ No camera found!
2025-11-24 18:09:35,780 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:35,782 - ERROR - ❌ No camera found!
2025-11-24 18:09:35,785 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:35,790 - ERROR - ❌ No camera found!
2025-11-24 18:09:35,811 - INFO - Frame 148 | PERCLOS: 0.00 | Yaw: 7.7° | Alerts: 1
2025-11-24 18:09:35,940 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:35,942 - ERROR - ❌ No camera found!
2025-11-24 18:09:35,943 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:35,944 - ERROR - ❌ No camera found!
2025-11-24 18:09:36,103 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:36,105 - ERROR - ❌ No camera found!
2025-11-24 18:09:36,107 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:36,110 - ERROR - ❌ No camera found!
2025-11-24 18:09:36,256 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:36,259 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:36,260 - ERROR - ❌ No camera found!
2025-11-24 18:09:36,260 - ERROR - ❌ No camera found!
2025-11-24 18:09:36,277 - INFO - Frame 150 | PERCLOS: 0.00 | Yaw: 7.7° | Alerts: 1
2025-11-24 18:09:36,413 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:36,413 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:36,414 - ERROR - ❌ No camera found!
2025-11-24 18:09:36,416 - ERROR - ❌ No camera found!
2025-11-24 18:09:36,567 - INFO - Frame 152 | PERCLOS: 0.00 | Yaw: 7.4° | Alerts: 1
2025-11-24 18:09:36,567 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:36,568 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:36,569 - ERROR - ❌ No camera found!
2025-11-24 18:09:36,569 - ERROR - ❌ No camera found!
2025-11-24 18:09:36,722 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:36,724 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:36,724 - ERROR - ❌ No camera found!
2025-11-24 18:09:36,724 - ERROR - ❌ No camera found!
2025-11-24 18:09:36,760 - INFO - Frame 154 | PERCLOS: 0.00 | Yaw: 7.3° | Alerts: 1
2025-11-24 18:09:36,890 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:36,892 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:36,894 - ERROR - ❌ No camera found!
2025-11-24 18:09:36,896 - ERROR - ❌ No camera found!
2025-11-24 18:09:37,050 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:37,054 - ERROR - ❌ No camera found!
2025-11-24 18:09:37,054 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:37,055 - ERROR - ❌ No camera found!
2025-11-24 18:09:37,214 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:37,214 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:37,216 - ERROR - ❌ No camera found!
2025-11-24 18:09:37,216 - ERROR - ❌ No camera found!
2025-11-24 18:09:37,230 - INFO - Frame 156 | PERCLOS: 0.00 | Yaw: 7.5° | Alerts: 1
2025-11-24 18:09:37,372 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:37,374 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:37,374 - ERROR - ❌ No camera found!
2025-11-24 18:09:37,377 - ERROR - ❌ No camera found!
2025-11-24 18:09:37,519 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:37,522 - ERROR - ❌ No camera found!
2025-11-24 18:09:37,522 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:37,523 - ERROR - ❌ No camera found!
2025-11-24 18:09:37,554 - INFO - Frame 158 | PERCLOS: 0.00 | Yaw: 5.2° | Alerts: 1
2025-11-24 18:09:37,674 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:37,676 - ERROR - ❌ No camera found!
2025-11-24 18:09:37,677 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:37,680 - ERROR - ❌ No camera found!
2025-11-24 18:09:37,846 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:37,848 - ERROR - ❌ No camera found!
2025-11-24 18:09:37,849 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:37,849 - INFO - Frame 160 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 18:09:37,851 - ERROR - ❌ No camera found!
2025-11-24 18:09:37,992 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:37,993 - ERROR - ❌ No camera found!
2025-11-24 18:09:37,995 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:37,997 - ERROR - ❌ No camera found!
2025-11-24 18:09:38,151 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:38,152 - ERROR - ❌ No camera found!
2025-11-24 18:09:38,155 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:38,157 - ERROR - ❌ No camera found!
2025-11-24 18:09:38,301 - INFO - Frame 162 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 18:09:38,304 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:38,305 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:38,306 - ERROR - ❌ No camera found!
2025-11-24 18:09:38,307 - ERROR - ❌ No camera found!
2025-11-24 18:09:38,464 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:38,465 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:38,466 - ERROR - ❌ No camera found!
2025-11-24 18:09:38,467 - ERROR - ❌ No camera found!
2025-11-24 18:09:38,610 - INFO - Frame 164 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 18:09:38,612 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:38,615 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:38,615 - ERROR - ❌ No camera found!
2025-11-24 18:09:38,618 - ERROR - ❌ No camera found!
2025-11-24 18:09:38,776 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:38,776 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:38,778 - ERROR - ❌ No camera found!
2025-11-24 18:09:38,778 - ERROR - ❌ No camera found!
2025-11-24 18:09:38,815 - INFO - Frame 166 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:09:38,928 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:38,930 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:38,930 - ERROR - ❌ No camera found!
2025-11-24 18:09:38,931 - ERROR - ❌ No camera found!
2025-11-24 18:09:39,089 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:39,090 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:39,090 - ERROR - ❌ No camera found!
2025-11-24 18:09:39,091 - ERROR - ❌ No camera found!
2025-11-24 18:09:39,251 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:39,252 - INFO - Frame 168 | PERCLOS: 0.00 | Yaw: 8.3° | Alerts: 1
2025-11-24 18:09:39,254 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:39,255 - ERROR - ❌ No camera found!
2025-11-24 18:09:39,255 - ERROR - ❌ No camera found!
2025-11-24 18:09:39,412 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:39,414 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:39,414 - ERROR - ❌ No camera found!
2025-11-24 18:09:39,415 - ERROR - ❌ No camera found!
2025-11-24 18:09:39,450 - INFO - Frame 170 | PERCLOS: 0.00 | Yaw: 9.5° | Alerts: 1
2025-11-24 18:09:39,567 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:39,569 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:39,569 - ERROR - ❌ No camera found!
2025-11-24 18:09:39,570 - ERROR - ❌ No camera found!
2025-11-24 18:09:39,726 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:39,730 - ERROR - ❌ No camera found!
2025-11-24 18:09:39,730 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:39,732 - ERROR - ❌ No camera found!
2025-11-24 18:09:39,751 - INFO - Frame 172 | PERCLOS: 0.00 | Yaw: 10.9° | Alerts: 1
2025-11-24 18:09:39,884 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:39,884 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:39,886 - ERROR - ❌ No camera found!
2025-11-24 18:09:39,886 - ERROR - ❌ No camera found!
2025-11-24 18:09:40,041 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:40,043 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:40,044 - ERROR - ❌ No camera found!
2025-11-24 18:09:40,045 - ERROR - ❌ No camera found!
2025-11-24 18:09:40,192 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:40,193 - ERROR - ❌ No camera found!
2025-11-24 18:09:40,194 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:40,198 - ERROR - ❌ No camera found!
2025-11-24 18:09:40,210 - INFO - Frame 174 | PERCLOS: 0.00 | Yaw: 13.4° | Alerts: 1
2025-11-24 18:09:40,350 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:40,350 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:40,351 - ERROR - ❌ No camera found!
2025-11-24 18:09:40,352 - ERROR - ❌ No camera found!
2025-11-24 18:09:40,567 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:40,569 - ERROR - ❌ No camera found!
2025-11-24 18:09:40,570 - INFO - Predictions disabled
2025-11-24 18:09:40,573 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:40,575 - ERROR - ❌ No camera found!
2025-11-24 18:09:40,593 - INFO - Frame 176 | PERCLOS: 0.00 | Yaw: 12.6° | Alerts: 1
2025-11-24 18:09:40,683 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:40,683 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:40,684 - ERROR - ❌ No camera found!
2025-11-24 18:09:40,684 - ERROR - ❌ No camera found!
2025-11-24 18:09:40,845 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:40,846 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:40,847 - ERROR - ❌ No camera found!
2025-11-24 18:09:40,849 - ERROR - ❌ No camera found!
2025-11-24 18:09:40,877 - INFO - Frame 178 | PERCLOS: 0.00 | Yaw: 12.9° | Alerts: 1
2025-11-24 18:09:41,015 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:41,019 - ERROR - ❌ No camera found!
2025-11-24 18:09:41,019 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:41,021 - ERROR - ❌ No camera found!
2025-11-24 18:09:41,180 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:41,181 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:41,181 - ERROR - ❌ No camera found!
2025-11-24 18:09:41,182 - ERROR - ❌ No camera found!
2025-11-24 18:09:41,342 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:41,345 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:41,345 - ERROR - ❌ No camera found!
2025-11-24 18:09:41,346 - ERROR - ❌ No camera found!
2025-11-24 18:09:41,361 - INFO - Frame 180 | PERCLOS: 0.00 | Yaw: 12.8° | Alerts: 1
2025-11-24 18:09:41,517 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:41,520 - ERROR - ❌ No camera found!
2025-11-24 18:09:41,520 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:41,521 - ERROR - ❌ No camera found!
2025-11-24 18:09:41,687 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:41,687 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:41,689 - ERROR - ❌ No camera found!
2025-11-24 18:09:41,689 - INFO - Frame 182 | PERCLOS: 0.00 | Yaw: 12.6° | Alerts: 1
2025-11-24 18:09:41,689 - ERROR - ❌ No camera found!
2025-11-24 18:09:41,844 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:41,846 - ERROR - ❌ No camera found!
2025-11-24 18:09:41,847 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:41,851 - ERROR - ❌ No camera found!
2025-11-24 18:09:42,028 - INFO - Frame 184 | PERCLOS: 0.00 | Yaw: 12.5° | Alerts: 1
2025-11-24 18:09:42,029 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:42,029 - ERROR - ❌ No camera found!
2025-11-24 18:09:42,031 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:42,034 - ERROR - ❌ No camera found!
2025-11-24 18:09:42,186 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:42,187 - ERROR - ❌ No camera found!
2025-11-24 18:09:42,189 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:42,191 - ERROR - ❌ No camera found!
2025-11-24 18:09:42,347 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:42,347 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:42,348 - ERROR - ❌ No camera found!
2025-11-24 18:09:42,349 - ERROR - ❌ No camera found!
2025-11-24 18:09:42,365 - INFO - Frame 186 | PERCLOS: 0.31 | Yaw: 12.6° | Alerts: 2
2025-11-24 18:09:42,505 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:42,508 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:42,508 - ERROR - ❌ No camera found!
2025-11-24 18:09:42,509 - ERROR - ❌ No camera found!
2025-11-24 18:09:42,664 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:42,666 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:42,667 - ERROR - ❌ No camera found!
2025-11-24 18:09:42,667 - ERROR - ❌ No camera found!
2025-11-24 18:09:42,696 - INFO - Frame 188 | PERCLOS: 0.00 | Yaw: 12.1° | Alerts: 1
2025-11-24 18:09:42,824 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:42,824 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:42,825 - ERROR - ❌ No camera found!
2025-11-24 18:09:42,825 - ERROR - ❌ No camera found!
2025-11-24 18:09:42,966 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:42,966 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:42,967 - ERROR - ❌ No camera found!
2025-11-24 18:09:42,968 - ERROR - ❌ No camera found!
2025-11-24 18:09:42,994 - INFO - Frame 190 | PERCLOS: 0.49 | Yaw: 9.9° | Alerts: 2
2025-11-24 18:09:43,128 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:43,128 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:43,130 - ERROR - ❌ No camera found!
2025-11-24 18:09:43,130 - ERROR - ❌ No camera found!
2025-11-24 18:09:43,279 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:43,279 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:43,280 - ERROR - ❌ No camera found!
2025-11-24 18:09:43,281 - ERROR - ❌ No camera found!
2025-11-24 18:09:43,427 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:43,429 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:43,431 - ERROR - ❌ No camera found!
2025-11-24 18:09:43,431 - ERROR - ❌ No camera found!
2025-11-24 18:09:43,448 - INFO - Frame 192 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 18:09:43,584 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:43,585 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:43,586 - ERROR - ❌ No camera found!
2025-11-24 18:09:43,586 - ERROR - ❌ No camera found!
2025-11-24 18:09:43,735 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:43,737 - ERROR - ❌ No camera found!
2025-11-24 18:09:43,738 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:43,739 - INFO - Frame 194 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 1
2025-11-24 18:09:43,741 - ERROR - ❌ No camera found!
2025-11-24 18:09:43,890 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:43,891 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:43,892 - ERROR - ❌ No camera found!
2025-11-24 18:09:43,892 - ERROR - ❌ No camera found!
2025-11-24 18:09:44,047 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:44,049 - INFO - Frame 196 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 1
2025-11-24 18:09:44,049 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:44,049 - ERROR - ❌ No camera found!
2025-11-24 18:09:44,049 - ERROR - ❌ No camera found!
2025-11-24 18:09:44,197 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:44,197 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:44,199 - ERROR - ❌ No camera found!
2025-11-24 18:09:44,199 - ERROR - ❌ No camera found!
2025-11-24 18:09:44,348 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:44,349 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:44,349 - ERROR - ❌ No camera found!
2025-11-24 18:09:44,350 - ERROR - ❌ No camera found!
2025-11-24 18:09:44,366 - INFO - Frame 198 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 1
2025-11-24 18:09:44,497 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:44,497 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:44,498 - ERROR - ❌ No camera found!
2025-11-24 18:09:44,498 - ERROR - ❌ No camera found!
2025-11-24 18:09:44,647 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:44,651 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:44,651 - ERROR - ❌ No camera found!
2025-11-24 18:09:44,653 - ERROR - ❌ No camera found!
2025-11-24 18:09:44,673 - INFO - Frame 200 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 1
2025-11-24 18:09:44,848 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:44,848 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:44,849 - ERROR - ❌ No camera found!
2025-11-24 18:09:44,850 - ERROR - ❌ No camera found!
2025-11-24 18:09:44,993 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:44,995 - ERROR - ❌ No camera found!
2025-11-24 18:09:44,995 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:44,999 - ERROR - ❌ No camera found!
2025-11-24 18:09:45,022 - INFO - Frame 202 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 1
2025-11-24 18:09:45,144 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:45,146 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:45,146 - ERROR - ❌ No camera found!
2025-11-24 18:09:45,147 - ERROR - ❌ No camera found!
2025-11-24 18:09:45,293 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:45,297 - ERROR - ❌ No camera found!
2025-11-24 18:09:45,297 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:45,300 - ERROR - ❌ No camera found!
2025-11-24 18:09:45,444 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:45,446 - ERROR - ❌ No camera found!
2025-11-24 18:09:45,446 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:45,447 - ERROR - ❌ No camera found!
2025-11-24 18:09:45,462 - INFO - Frame 204 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 1
2025-11-24 18:09:45,594 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:45,594 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:45,596 - ERROR - ❌ No camera found!
2025-11-24 18:09:45,596 - ERROR - ❌ No camera found!
2025-11-24 18:09:45,753 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:45,754 - ERROR - ❌ No camera found!
2025-11-24 18:09:45,755 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:45,757 - ERROR - ❌ No camera found!
2025-11-24 18:09:45,777 - INFO - Frame 206 | PERCLOS: 0.00 | Yaw: -0.3° | Alerts: 1
2025-11-24 18:09:45,907 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:45,907 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:45,909 - ERROR - ❌ No camera found!
2025-11-24 18:09:45,909 - ERROR - ❌ No camera found!
2025-11-24 18:09:46,064 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:46,067 - ERROR - ❌ No camera found!
2025-11-24 18:09:46,067 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:46,068 - ERROR - ❌ No camera found!
2025-11-24 18:09:46,070 - INFO - Frame 208 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 1
2025-11-24 18:09:46,208 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:46,208 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:46,209 - ERROR - ❌ No camera found!
2025-11-24 18:09:46,210 - ERROR - ❌ No camera found!
2025-11-24 18:09:46,366 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:46,366 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:46,367 - ERROR - ❌ No camera found!
2025-11-24 18:09:46,367 - ERROR - ❌ No camera found!
2025-11-24 18:09:46,518 - INFO - Frame 210 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 1
2025-11-24 18:09:46,521 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:46,521 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:46,521 - ERROR - ❌ No camera found!
2025-11-24 18:09:46,522 - ERROR - ❌ No camera found!
2025-11-24 18:09:46,673 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:46,673 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:46,675 - ERROR - ❌ No camera found!
2025-11-24 18:09:46,675 - ERROR - ❌ No camera found!
2025-11-24 18:09:46,707 - INFO - Frame 212 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 1
2025-11-24 18:09:46,827 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:46,829 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:46,829 - ERROR - ❌ No camera found!
2025-11-24 18:09:46,829 - ERROR - ❌ No camera found!
2025-11-24 18:09:46,971 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:46,975 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:46,975 - ERROR - ❌ No camera found!
2025-11-24 18:09:46,976 - ERROR - ❌ No camera found!
2025-11-24 18:09:47,000 - INFO - Frame 214 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 1
2025-11-24 18:09:47,131 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:47,131 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:47,131 - ERROR - ❌ No camera found!
2025-11-24 18:09:47,132 - ERROR - ❌ No camera found!
2025-11-24 18:09:47,280 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:47,283 - ERROR - ❌ No camera found!
2025-11-24 18:09:47,283 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:47,286 - ERROR - ❌ No camera found!
2025-11-24 18:09:47,429 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:47,429 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:47,430 - ERROR - ❌ No camera found!
2025-11-24 18:09:47,431 - ERROR - ❌ No camera found!
2025-11-24 18:09:47,449 - INFO - Frame 216 | PERCLOS: 0.43 | Yaw: -0.6° | Alerts: 2
2025-11-24 18:09:47,595 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:47,596 - ERROR - ❌ No camera found!
2025-11-24 18:09:47,597 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:47,598 - ERROR - ❌ No camera found!
2025-11-24 18:09:47,748 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:47,751 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:47,752 - ERROR - ❌ No camera found!
2025-11-24 18:09:47,753 - ERROR - ❌ No camera found!
2025-11-24 18:09:47,778 - INFO - Frame 218 | PERCLOS: 0.00 | Yaw: -0.9° | Alerts: 1
2025-11-24 18:09:47,918 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:47,920 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:47,922 - ERROR - ❌ No camera found!
2025-11-24 18:09:47,922 - ERROR - ❌ No camera found!
2025-11-24 18:09:48,087 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:48,088 - ERROR - ❌ No camera found!
2025-11-24 18:09:48,090 - INFO - Frame 220 | PERCLOS: 0.00 | Yaw: -0.8° | Alerts: 1
2025-11-24 18:09:48,090 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:48,092 - ERROR - ❌ No camera found!
2025-11-24 18:09:48,233 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:48,236 - ERROR - ❌ No camera found!
2025-11-24 18:09:48,236 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:48,237 - ERROR - ❌ No camera found!
2025-11-24 18:09:48,390 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:48,391 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:48,392 - ERROR - ❌ No camera found!
2025-11-24 18:09:48,393 - ERROR - ❌ No camera found!
2025-11-24 18:09:48,410 - INFO - Frame 222 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 1
2025-11-24 18:09:48,545 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:48,545 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:48,547 - ERROR - ❌ No camera found!
2025-11-24 18:09:48,547 - ERROR - ❌ No camera found!
2025-11-24 18:09:48,700 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:48,705 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:48,705 - ERROR - ❌ No camera found!
2025-11-24 18:09:48,706 - ERROR - ❌ No camera found!
2025-11-24 18:09:48,727 - INFO - Frame 224 | PERCLOS: 0.00 | Yaw: -0.3° | Alerts: 1
2025-11-24 18:09:48,848 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:48,849 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:48,850 - ERROR - ❌ No camera found!
2025-11-24 18:09:48,851 - ERROR - ❌ No camera found!
2025-11-24 18:09:49,000 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:49,004 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:49,004 - ERROR - ❌ No camera found!
2025-11-24 18:09:49,005 - ERROR - ❌ No camera found!
2025-11-24 18:09:49,029 - INFO - Frame 226 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 1
2025-11-24 18:09:49,157 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:49,157 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:49,159 - ERROR - ❌ No camera found!
2025-11-24 18:09:49,159 - ERROR - ❌ No camera found!
2025-11-24 18:09:49,195 - INFO - Frame 228 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:09:49,311 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:49,311 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:49,312 - ERROR - ❌ No camera found!
2025-11-24 18:09:49,312 - ERROR - ❌ No camera found!
2025-11-24 18:09:49,467 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:49,470 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:49,470 - ERROR - ❌ No camera found!
2025-11-24 18:09:49,472 - ERROR - ❌ No camera found!
2025-11-24 18:09:49,505 - INFO - Frame 230 | PERCLOS: 0.31 | Yaw: 8.0° | Alerts: 1
2025-11-24 18:09:49,627 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:49,627 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:49,628 - ERROR - ❌ No camera found!
2025-11-24 18:09:49,628 - ERROR - ❌ No camera found!
2025-11-24 18:09:49,781 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:49,781 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:49,782 - ERROR - ❌ No camera found!
2025-11-24 18:09:49,782 - ERROR - ❌ No camera found!
2025-11-24 18:09:49,782 - INFO - Frame 232 | PERCLOS: 0.24 | Yaw: 8.8° | Alerts: 0
2025-11-24 18:09:49,925 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:49,927 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:49,927 - ERROR - ❌ No camera found!
2025-11-24 18:09:49,928 - ERROR - ❌ No camera found!
2025-11-24 18:09:50,080 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:50,080 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:50,082 - ERROR - ❌ No camera found!
2025-11-24 18:09:50,083 - ERROR - ❌ No camera found!
2025-11-24 18:09:50,239 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:50,240 - ERROR - ❌ No camera found!
2025-11-24 18:09:50,242 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:50,243 - ERROR - ❌ No camera found!
2025-11-24 18:09:50,261 - INFO - Frame 234 | PERCLOS: 0.14 | Yaw: 9.3° | Alerts: 1
2025-11-24 18:09:50,384 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:50,386 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:50,387 - ERROR - ❌ No camera found!
2025-11-24 18:09:50,388 - ERROR - ❌ No camera found!
2025-11-24 18:09:50,538 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:50,540 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:50,540 - ERROR - ❌ No camera found!
2025-11-24 18:09:50,542 - ERROR - ❌ No camera found!
2025-11-24 18:09:50,567 - INFO - Frame 236 | PERCLOS: 0.29 | Yaw: 8.6° | Alerts: 1
2025-11-24 18:09:50,696 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:50,696 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:50,697 - ERROR - ❌ No camera found!
2025-11-24 18:09:50,697 - ERROR - ❌ No camera found!
2025-11-24 18:09:50,847 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:50,847 - INFO - Frame 238 | PERCLOS: 0.15 | Yaw: 7.6° | Alerts: 1
2025-11-24 18:09:50,848 - ERROR - ❌ No camera found!
2025-11-24 18:09:50,850 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:50,851 - ERROR - ❌ No camera found!
2025-11-24 18:09:50,996 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:50,999 - ERROR - ❌ No camera found!
2025-11-24 18:09:50,999 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:51,000 - ERROR - ❌ No camera found!
2025-11-24 18:09:51,154 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:51,154 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:51,155 - ERROR - ❌ No camera found!
2025-11-24 18:09:51,156 - ERROR - ❌ No camera found!
2025-11-24 18:09:51,174 - INFO - Frame 240 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 18:09:51,302 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:51,302 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:51,303 - ERROR - ❌ No camera found!
2025-11-24 18:09:51,303 - ERROR - ❌ No camera found!
2025-11-24 18:09:51,452 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:51,455 - ERROR - ❌ No camera found!
2025-11-24 18:09:51,456 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:51,458 - ERROR - ❌ No camera found!
2025-11-24 18:09:51,459 - INFO - Frame 242 | PERCLOS: 0.00 | Yaw: 4.1° | Alerts: 1
2025-11-24 18:09:51,614 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:51,614 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:51,615 - ERROR - ❌ No camera found!
2025-11-24 18:09:51,615 - ERROR - ❌ No camera found!
2025-11-24 18:09:51,765 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:51,767 - INFO - Frame 244 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-24 18:09:51,768 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:51,768 - ERROR - ❌ No camera found!
2025-11-24 18:09:51,768 - ERROR - ❌ No camera found!
2025-11-24 18:09:51,927 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:51,928 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:51,929 - ERROR - ❌ No camera found!
2025-11-24 18:09:51,929 - ERROR - ❌ No camera found!
2025-11-24 18:09:52,090 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:52,091 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:52,092 - ERROR - ❌ No camera found!
2025-11-24 18:09:52,093 - ERROR - ❌ No camera found!
2025-11-24 18:09:52,106 - INFO - Frame 246 | PERCLOS: 0.00 | Yaw: 8.3° | Alerts: 1
2025-11-24 18:09:52,241 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:52,241 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:52,242 - ERROR - ❌ No camera found!
2025-11-24 18:09:52,242 - ERROR - ❌ No camera found!
2025-11-24 18:09:52,398 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:52,398 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:52,399 - ERROR - ❌ No camera found!
2025-11-24 18:09:52,399 - ERROR - ❌ No camera found!
2025-11-24 18:09:52,400 - INFO - Frame 248 | PERCLOS: 0.00 | Yaw: 8.3° | Alerts: 1
2025-11-24 18:09:52,550 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:52,550 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:52,552 - ERROR - ❌ No camera found!
2025-11-24 18:09:52,552 - ERROR - ❌ No camera found!
2025-11-24 18:09:52,586 - INFO - Frame 250 | PERCLOS: 0.01 | Yaw: 8.1° | Alerts: 1
2025-11-24 18:09:52,713 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:52,713 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:52,714 - ERROR - ❌ No camera found!
2025-11-24 18:09:52,714 - ERROR - ❌ No camera found!
2025-11-24 18:09:52,869 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:52,871 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:52,872 - ERROR - ❌ No camera found!
2025-11-24 18:09:52,873 - ERROR - ❌ No camera found!
2025-11-24 18:09:53,018 - INFO - Frame 252 | PERCLOS: 0.00 | Yaw: 7.5° | Alerts: 1
2025-11-24 18:09:53,021 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:53,021 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:53,022 - ERROR - ❌ No camera found!
2025-11-24 18:09:53,022 - ERROR - ❌ No camera found!
2025-11-24 18:09:53,170 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:53,170 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:53,172 - ERROR - ❌ No camera found!
2025-11-24 18:09:53,172 - ERROR - ❌ No camera found!
2025-11-24 18:09:53,208 - INFO - Frame 254 | PERCLOS: 0.35 | Yaw: 4.8° | Alerts: 2
2025-11-24 18:09:53,326 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:53,326 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:53,327 - ERROR - ❌ No camera found!
2025-11-24 18:09:53,328 - ERROR - ❌ No camera found!
2025-11-24 18:09:53,470 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:53,471 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:53,473 - ERROR - ❌ No camera found!
2025-11-24 18:09:53,473 - ERROR - ❌ No camera found!
2025-11-24 18:09:53,494 - INFO - Frame 256 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 1
2025-11-24 18:09:53,623 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:53,625 - ERROR - ❌ No camera found!
2025-11-24 18:09:53,625 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:53,626 - ERROR - ❌ No camera found!
2025-11-24 18:09:53,774 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:53,776 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:53,777 - ERROR - ❌ No camera found!
2025-11-24 18:09:53,781 - ERROR - ❌ No camera found!
2025-11-24 18:09:53,934 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:53,934 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:53,934 - ERROR - ❌ No camera found!
2025-11-24 18:09:53,935 - ERROR - ❌ No camera found!
2025-11-24 18:09:53,952 - INFO - Frame 258 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 1
2025-11-24 18:09:54,095 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:54,097 - ERROR - ❌ No camera found!
2025-11-24 18:09:54,098 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:54,101 - ERROR - ❌ No camera found!
2025-11-24 18:09:54,255 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:54,255 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:54,256 - ERROR - ❌ No camera found!
2025-11-24 18:09:54,257 - ERROR - ❌ No camera found!
2025-11-24 18:09:54,283 - INFO - Frame 260 | PERCLOS: 0.00 | Yaw: -0.2° | Alerts: 1
2025-11-24 18:09:54,418 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:54,421 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:54,421 - ERROR - ❌ No camera found!
2025-11-24 18:09:54,423 - ERROR - ❌ No camera found!
2025-11-24 18:09:54,560 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:54,560 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:54,560 - ERROR - ❌ No camera found!
2025-11-24 18:09:54,563 - ERROR - ❌ No camera found!
2025-11-24 18:09:54,591 - INFO - Frame 262 | PERCLOS: 0.51 | Yaw: 4.2° | Alerts: 2
2025-11-24 18:09:54,714 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:54,716 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:54,716 - ERROR - ❌ No camera found!
2025-11-24 18:09:54,716 - ERROR - ❌ No camera found!
2025-11-24 18:09:54,865 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:54,868 - ERROR - ❌ No camera found!
2025-11-24 18:09:54,869 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:54,870 - ERROR - ❌ No camera found!
2025-11-24 18:09:55,069 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:55,071 - ERROR - ❌ No camera found!
2025-11-24 18:09:55,072 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:55,072 - ERROR - ❌ No camera found!
2025-11-24 18:09:55,088 - INFO - Frame 264 | PERCLOS: 0.32 | Yaw: 6.3° | Alerts: 2
2025-11-24 18:09:55,228 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:55,228 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:55,229 - ERROR - ❌ No camera found!
2025-11-24 18:09:55,230 - ERROR - ❌ No camera found!
2025-11-24 18:09:55,392 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:55,392 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:55,393 - ERROR - ❌ No camera found!
2025-11-24 18:09:55,393 - ERROR - ❌ No camera found!
2025-11-24 18:09:55,423 - INFO - Frame 266 | PERCLOS: 0.30 | Yaw: 6.7° | Alerts: 1
2025-11-24 18:09:55,545 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:55,545 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:55,546 - ERROR - ❌ No camera found!
2025-11-24 18:09:55,546 - ERROR - ❌ No camera found!
2025-11-24 18:09:55,690 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:55,691 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:55,693 - ERROR - ❌ No camera found!
2025-11-24 18:09:55,694 - ERROR - ❌ No camera found!
2025-11-24 18:09:55,721 - INFO - Frame 268 | PERCLOS: 0.32 | Yaw: 6.7° | Alerts: 2
2025-11-24 18:09:55,848 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:55,848 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:55,849 - ERROR - ❌ No camera found!
2025-11-24 18:09:55,849 - ERROR - ❌ No camera found!
2025-11-24 18:09:55,994 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:55,994 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:55,995 - ERROR - ❌ No camera found!
2025-11-24 18:09:55,996 - ERROR - ❌ No camera found!
2025-11-24 18:09:56,145 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:56,145 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:56,146 - ERROR - ❌ No camera found!
2025-11-24 18:09:56,146 - ERROR - ❌ No camera found!
2025-11-24 18:09:56,169 - INFO - Frame 270 | PERCLOS: 0.31 | Yaw: 6.5° | Alerts: 2
2025-11-24 18:09:56,313 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:56,313 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:56,314 - ERROR - ❌ No camera found!
2025-11-24 18:09:56,315 - ERROR - ❌ No camera found!
2025-11-24 18:09:56,465 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:56,467 - ERROR - ❌ No camera found!
2025-11-24 18:09:56,467 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:56,468 - ERROR - ❌ No camera found!
2025-11-24 18:09:56,496 - INFO - Frame 272 | PERCLOS: 0.27 | Yaw: 7.2° | Alerts: 1
2025-11-24 18:09:56,619 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:56,621 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:56,622 - ERROR - ❌ No camera found!
2025-11-24 18:09:56,622 - ERROR - ❌ No camera found!
2025-11-24 18:09:56,764 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:56,764 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:56,765 - ERROR - ❌ No camera found!
2025-11-24 18:09:56,765 - ERROR - ❌ No camera found!
2025-11-24 18:09:56,790 - INFO - Frame 274 | PERCLOS: 0.32 | Yaw: 7.1° | Alerts: 2
2025-11-24 18:09:56,917 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:56,919 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:56,920 - ERROR - ❌ No camera found!
2025-11-24 18:09:56,920 - ERROR - ❌ No camera found!
2025-11-24 18:09:57,067 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:57,068 - ERROR - ❌ No camera found!
2025-11-24 18:09:57,069 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:57,070 - ERROR - ❌ No camera found!
2025-11-24 18:09:57,235 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:57,235 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:57,236 - ERROR - ❌ No camera found!
2025-11-24 18:09:57,236 - ERROR - ❌ No camera found!
2025-11-24 18:09:57,252 - INFO - Frame 276 | PERCLOS: 0.13 | Yaw: 7.0° | Alerts: 1
2025-11-24 18:09:57,390 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:57,391 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:57,392 - ERROR - ❌ No camera found!
2025-11-24 18:09:57,392 - ERROR - ❌ No camera found!
2025-11-24 18:09:57,539 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:57,541 - ERROR - ❌ No camera found!
2025-11-24 18:09:57,542 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:57,545 - ERROR - ❌ No camera found!
2025-11-24 18:09:57,565 - INFO - Frame 278 | PERCLOS: 0.24 | Yaw: 7.4° | Alerts: 1
2025-11-24 18:09:57,695 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:57,696 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:57,697 - ERROR - ❌ No camera found!
2025-11-24 18:09:57,698 - ERROR - ❌ No camera found!
2025-11-24 18:09:57,849 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:57,852 - ERROR - ❌ No camera found!
2025-11-24 18:09:57,852 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:57,853 - ERROR - ❌ No camera found!
2025-11-24 18:09:57,875 - INFO - Frame 280 | PERCLOS: 0.28 | Yaw: 7.4° | Alerts: 1
2025-11-24 18:09:58,010 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:58,013 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:58,013 - ERROR - ❌ No camera found!
2025-11-24 18:09:58,013 - ERROR - ❌ No camera found!
2025-11-24 18:09:58,166 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:58,168 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:58,169 - ERROR - ❌ No camera found!
2025-11-24 18:09:58,169 - ERROR - ❌ No camera found!
2025-11-24 18:09:58,316 - INFO - Frame 282 | PERCLOS: 0.29 | Yaw: 6.9° | Alerts: 1
2025-11-24 18:09:58,318 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:58,320 - ERROR - ❌ No camera found!
2025-11-24 18:09:58,320 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:58,321 - ERROR - ❌ No camera found!
2025-11-24 18:09:58,475 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:58,475 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:58,476 - ERROR - ❌ No camera found!
2025-11-24 18:09:58,477 - ERROR - ❌ No camera found!
2025-11-24 18:09:58,510 - INFO - Frame 284 | PERCLOS: 0.30 | Yaw: 7.4° | Alerts: 2
2025-11-24 18:09:58,627 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:58,630 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:58,630 - ERROR - ❌ No camera found!
2025-11-24 18:09:58,632 - ERROR - ❌ No camera found!
2025-11-24 18:09:58,781 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:58,781 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:58,782 - ERROR - ❌ No camera found!
2025-11-24 18:09:58,783 - ERROR - ❌ No camera found!
2025-11-24 18:09:58,806 - INFO - Frame 286 | PERCLOS: 0.26 | Yaw: 7.7° | Alerts: 1
2025-11-24 18:09:58,938 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:58,940 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:58,941 - ERROR - ❌ No camera found!
2025-11-24 18:09:58,941 - ERROR - ❌ No camera found!
2025-11-24 18:09:59,096 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:59,097 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:59,098 - ERROR - ❌ No camera found!
2025-11-24 18:09:59,098 - ERROR - ❌ No camera found!
2025-11-24 18:09:59,251 - INFO - Frame 288 | PERCLOS: 0.31 | Yaw: 7.4° | Alerts: 2
2025-11-24 18:09:59,254 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:59,254 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:59,256 - ERROR - ❌ No camera found!
2025-11-24 18:09:59,256 - ERROR - ❌ No camera found!
2025-11-24 18:09:59,407 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:59,407 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:59,408 - ERROR - ❌ No camera found!
2025-11-24 18:09:59,409 - ERROR - ❌ No camera found!
2025-11-24 18:09:59,443 - INFO - Frame 290 | PERCLOS: 0.31 | Yaw: 7.4° | Alerts: 2
2025-11-24 18:09:59,571 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:59,571 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:59,572 - ERROR - ❌ No camera found!
2025-11-24 18:09:59,572 - ERROR - ❌ No camera found!
2025-11-24 18:09:59,727 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:59,727 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:59,728 - ERROR - ❌ No camera found!
2025-11-24 18:09:59,729 - ERROR - ❌ No camera found!
2025-11-24 18:09:59,756 - INFO - Frame 292 | PERCLOS: 0.08 | Yaw: 7.5° | Alerts: 1
2025-11-24 18:09:59,890 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:09:59,891 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:09:59,892 - ERROR - ❌ No camera found!
2025-11-24 18:09:59,893 - ERROR - ❌ No camera found!
2025-11-24 18:10:00,043 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:00,044 - ERROR - ❌ No camera found!
2025-11-24 18:10:00,046 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:00,051 - ERROR - ❌ No camera found!
2025-11-24 18:10:00,187 - INFO - Frame 294 | PERCLOS: 0.23 | Yaw: 7.5° | Alerts: 1
2025-11-24 18:10:00,189 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:00,191 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:00,192 - ERROR - ❌ No camera found!
2025-11-24 18:10:00,192 - ERROR - ❌ No camera found!
2025-11-24 18:10:00,341 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:00,341 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:00,341 - ERROR - ❌ No camera found!
2025-11-24 18:10:00,341 - ERROR - ❌ No camera found!
2025-11-24 18:10:00,377 - INFO - Frame 296 | PERCLOS: 0.21 | Yaw: 7.7° | Alerts: 1
2025-11-24 18:10:00,490 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:00,492 - ERROR - ❌ No camera found!
2025-11-24 18:10:00,493 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:00,494 - ERROR - ❌ No camera found!
2025-11-24 18:10:00,649 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:00,651 - ERROR - ❌ No camera found!
2025-11-24 18:10:00,652 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:00,653 - ERROR - ❌ No camera found!
2025-11-24 18:10:00,657 - INFO - Frame 298 | PERCLOS: 0.25 | Yaw: 7.5° | Alerts: 1
2025-11-24 18:10:00,817 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:00,819 - ERROR - ❌ No camera found!
2025-11-24 18:10:00,820 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:00,820 - ERROR - ❌ No camera found!
2025-11-24 18:10:00,971 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:00,972 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:00,973 - ERROR - ❌ No camera found!
2025-11-24 18:10:00,974 - ERROR - ❌ No camera found!
2025-11-24 18:10:01,131 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:01,135 - ERROR - ❌ No camera found!
2025-11-24 18:10:01,137 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:01,137 - ERROR - ❌ No camera found!
2025-11-24 18:10:01,155 - INFO - Frame 300 | PERCLOS: 0.26 | Yaw: 7.7° | Alerts: 1
2025-11-24 18:10:01,280 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:01,282 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:01,282 - ERROR - ❌ No camera found!
2025-11-24 18:10:01,283 - ERROR - ❌ No camera found!
2025-11-24 18:10:01,448 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:01,448 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:01,449 - INFO - Frame 302 | PERCLOS: 0.09 | Yaw: 7.1° | Alerts: 1
2025-11-24 18:10:01,449 - ERROR - ❌ No camera found!
2025-11-24 18:10:01,449 - ERROR - ❌ No camera found!
2025-11-24 18:10:01,599 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:01,599 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:01,600 - ERROR - ❌ No camera found!
2025-11-24 18:10:01,601 - ERROR - ❌ No camera found!
2025-11-24 18:10:01,767 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:01,770 - INFO - Frame 304 | PERCLOS: 0.30 | Yaw: 7.5° | Alerts: 1
2025-11-24 18:10:01,770 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:01,770 - ERROR - ❌ No camera found!
2025-11-24 18:10:01,771 - ERROR - ❌ No camera found!
2025-11-24 18:10:01,917 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:01,919 - ERROR - ❌ No camera found!
2025-11-24 18:10:01,922 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:01,925 - ERROR - ❌ No camera found!
2025-11-24 18:10:02,075 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:02,077 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:02,078 - ERROR - ❌ No camera found!
2025-11-24 18:10:02,078 - ERROR - ❌ No camera found!
2025-11-24 18:10:02,232 - INFO - Frame 306 | PERCLOS: 0.15 | Yaw: 7.4° | Alerts: 1
2025-11-24 18:10:02,236 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:02,237 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:02,237 - ERROR - ❌ No camera found!
2025-11-24 18:10:02,238 - ERROR - ❌ No camera found!
2025-11-24 18:10:02,392 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:02,395 - ERROR - ❌ No camera found!
2025-11-24 18:10:02,395 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:02,396 - ERROR - ❌ No camera found!
2025-11-24 18:10:02,428 - INFO - Frame 308 | PERCLOS: 0.13 | Yaw: 7.6° | Alerts: 1
2025-11-24 18:10:02,546 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:02,547 - ERROR - ❌ No camera found!
2025-11-24 18:10:02,548 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:02,549 - ERROR - ❌ No camera found!
2025-11-24 18:10:02,704 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:02,704 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:02,705 - ERROR - ❌ No camera found!
2025-11-24 18:10:02,705 - ERROR - ❌ No camera found!
2025-11-24 18:10:02,728 - INFO - Frame 310 | PERCLOS: 0.39 | Yaw: 7.4° | Alerts: 2
2025-11-24 18:10:02,860 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:02,862 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:02,863 - ERROR - ❌ No camera found!
2025-11-24 18:10:02,864 - ERROR - ❌ No camera found!
2025-11-24 18:10:03,020 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:03,020 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:03,021 - ERROR - ❌ No camera found!
2025-11-24 18:10:03,022 - ERROR - ❌ No camera found!
2025-11-24 18:10:03,166 - INFO - Frame 312 | PERCLOS: 0.32 | Yaw: 7.3° | Alerts: 2
2025-11-24 18:10:03,171 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:03,171 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:03,171 - ERROR - ❌ No camera found!
2025-11-24 18:10:03,172 - ERROR - ❌ No camera found!
2025-11-24 18:10:03,324 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:03,327 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:03,328 - ERROR - ❌ No camera found!
2025-11-24 18:10:03,329 - ERROR - ❌ No camera found!
2025-11-24 18:10:03,479 - INFO - Frame 314 | PERCLOS: 0.26 | Yaw: 7.3° | Alerts: 1
2025-11-24 18:10:03,482 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:03,483 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:03,484 - ERROR - ❌ No camera found!
2025-11-24 18:10:03,484 - ERROR - ❌ No camera found!
2025-11-24 18:10:03,642 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:03,643 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:03,644 - ERROR - ❌ No camera found!
2025-11-24 18:10:03,645 - ERROR - ❌ No camera found!
2025-11-24 18:10:03,678 - INFO - Frame 316 | PERCLOS: 0.49 | Yaw: 7.1° | Alerts: 2
2025-11-24 18:10:03,800 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:03,800 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:03,801 - ERROR - ❌ No camera found!
2025-11-24 18:10:03,801 - ERROR - ❌ No camera found!
2025-11-24 18:10:03,956 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:03,957 - ERROR - ❌ No camera found!
2025-11-24 18:10:03,959 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:03,961 - ERROR - ❌ No camera found!
2025-11-24 18:10:04,109 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:04,109 - INFO - Frame 318 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 1
2025-11-24 18:10:04,111 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:04,112 - ERROR - ❌ No camera found!
2025-11-24 18:10:04,112 - ERROR - ❌ No camera found!
2025-11-24 18:10:04,259 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:04,259 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:04,260 - ERROR - ❌ No camera found!
2025-11-24 18:10:04,261 - ERROR - ❌ No camera found!
2025-11-24 18:10:04,422 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:04,422 - INFO - Frame 320 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 1
2025-11-24 18:10:04,424 - ERROR - ❌ No camera found!
2025-11-24 18:10:04,425 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:04,427 - ERROR - ❌ No camera found!
2025-11-24 18:10:04,576 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:04,576 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:04,577 - ERROR - ❌ No camera found!
2025-11-24 18:10:04,577 - ERROR - ❌ No camera found!
2025-11-24 18:10:04,612 - INFO - Frame 322 | PERCLOS: 0.00 | Yaw: -0.0° | Alerts: 1
2025-11-24 18:10:04,732 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:04,733 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:04,733 - ERROR - ❌ No camera found!
2025-11-24 18:10:04,734 - ERROR - ❌ No camera found!
2025-11-24 18:10:04,880 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:04,880 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:04,881 - ERROR - ❌ No camera found!
2025-11-24 18:10:04,881 - ERROR - ❌ No camera found!
2025-11-24 18:10:05,033 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:05,033 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:05,034 - ERROR - ❌ No camera found!
2025-11-24 18:10:05,035 - ERROR - ❌ No camera found!
2025-11-24 18:10:05,053 - INFO - Frame 324 | PERCLOS: 0.50 | Yaw: 3.8° | Alerts: 2
2025-11-24 18:10:05,199 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:05,199 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:05,200 - ERROR - ❌ No camera found!
2025-11-24 18:10:05,201 - ERROR - ❌ No camera found!
2025-11-24 18:10:05,344 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:05,345 - ERROR - ❌ No camera found!
2025-11-24 18:10:05,347 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:05,348 - ERROR - ❌ No camera found!
2025-11-24 18:10:05,374 - INFO - Frame 326 | PERCLOS: 0.30 | Yaw: 6.3° | Alerts: 2
2025-11-24 18:10:05,500 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:05,503 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:05,503 - ERROR - ❌ No camera found!
2025-11-24 18:10:05,504 - ERROR - ❌ No camera found!
2025-11-24 18:10:05,652 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:05,653 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:05,654 - ERROR - ❌ No camera found!
2025-11-24 18:10:05,654 - ERROR - ❌ No camera found!
2025-11-24 18:10:05,683 - INFO - Frame 328 | PERCLOS: 0.41 | Yaw: 6.7° | Alerts: 2
2025-11-24 18:10:05,809 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:05,809 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:05,810 - ERROR - ❌ No camera found!
2025-11-24 18:10:05,810 - ERROR - ❌ No camera found!
2025-11-24 18:10:05,962 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:05,965 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:05,965 - ERROR - ❌ No camera found!
2025-11-24 18:10:05,966 - ERROR - ❌ No camera found!
2025-11-24 18:10:06,156 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:06,158 - ERROR - ❌ No camera found!
2025-11-24 18:10:06,163 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:06,165 - ERROR - ❌ No camera found!
2025-11-24 18:10:06,177 - INFO - Frame 330 | PERCLOS: 0.26 | Yaw: 6.9° | Alerts: 1
2025-11-24 18:10:06,319 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:06,321 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:06,322 - ERROR - ❌ No camera found!
2025-11-24 18:10:06,322 - ERROR - ❌ No camera found!
2025-11-24 18:10:06,468 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:06,470 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:06,472 - ERROR - ❌ No camera found!
2025-11-24 18:10:06,472 - ERROR - ❌ No camera found!
2025-11-24 18:10:06,496 - INFO - Frame 332 | PERCLOS: 0.14 | Yaw: 7.1° | Alerts: 1
2025-11-24 18:10:06,624 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:06,624 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:06,625 - ERROR - ❌ No camera found!
2025-11-24 18:10:06,625 - ERROR - ❌ No camera found!
2025-11-24 18:10:06,779 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:06,781 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:06,782 - ERROR - ❌ No camera found!
2025-11-24 18:10:06,784 - ERROR - ❌ No camera found!
2025-11-24 18:10:06,813 - INFO - Frame 334 | PERCLOS: 0.23 | Yaw: 7.1° | Alerts: 1
2025-11-24 18:10:06,929 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:06,930 - ERROR - ❌ No camera found!
2025-11-24 18:10:06,931 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:06,932 - ERROR - ❌ No camera found!
2025-11-24 18:10:07,089 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:07,091 - ERROR - ❌ No camera found!
2025-11-24 18:10:07,093 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:07,096 - ERROR - ❌ No camera found!
2025-11-24 18:10:07,245 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:07,246 - ERROR - ❌ No camera found!
2025-11-24 18:10:07,248 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:07,249 - ERROR - ❌ No camera found!
2025-11-24 18:10:07,264 - INFO - Frame 336 | PERCLOS: 0.17 | Yaw: 6.9° | Alerts: 1
2025-11-24 18:10:07,401 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:07,401 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:07,403 - ERROR - ❌ No camera found!
2025-11-24 18:10:07,403 - ERROR - ❌ No camera found!
2025-11-24 18:10:07,555 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:07,557 - ERROR - ❌ No camera found!
2025-11-24 18:10:07,559 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:07,560 - ERROR - ❌ No camera found!
2025-11-24 18:10:07,581 - INFO - Frame 338 | PERCLOS: 0.26 | Yaw: 6.8° | Alerts: 1
2025-11-24 18:10:07,712 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:07,714 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:07,715 - ERROR - ❌ No camera found!
2025-11-24 18:10:07,716 - ERROR - ❌ No camera found!
2025-11-24 18:10:07,864 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:07,865 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:07,865 - ERROR - ❌ No camera found!
2025-11-24 18:10:07,866 - ERROR - ❌ No camera found!
2025-11-24 18:10:07,868 - INFO - Frame 340 | PERCLOS: 0.15 | Yaw: 7.1° | Alerts: 1
2025-11-24 18:10:08,028 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:08,030 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:08,030 - ERROR - ❌ No camera found!
2025-11-24 18:10:08,031 - ERROR - ❌ No camera found!
2025-11-24 18:10:08,180 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:08,180 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:08,183 - ERROR - ❌ No camera found!
2025-11-24 18:10:08,184 - ERROR - ❌ No camera found!
2025-11-24 18:10:08,334 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:08,337 - ERROR - ❌ No camera found!
2025-11-24 18:10:08,338 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:08,341 - ERROR - ❌ No camera found!
2025-11-24 18:10:08,359 - INFO - Frame 342 | PERCLOS: 0.47 | Yaw: 6.0° | Alerts: 2
2025-11-24 18:10:08,481 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:08,481 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:08,482 - ERROR - ❌ No camera found!
2025-11-24 18:10:08,482 - ERROR - ❌ No camera found!
2025-11-24 18:10:08,633 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:08,634 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:08,635 - ERROR - ❌ No camera found!
2025-11-24 18:10:08,636 - ERROR - ❌ No camera found!
2025-11-24 18:10:08,664 - INFO - Frame 344 | PERCLOS: 0.00 | Yaw: -0.2° | Alerts: 1
2025-11-24 18:10:08,789 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:08,790 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:08,791 - ERROR - ❌ No camera found!
2025-11-24 18:10:08,792 - ERROR - ❌ No camera found!
2025-11-24 18:10:08,944 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:08,946 - ERROR - ❌ No camera found!
2025-11-24 18:10:08,946 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:08,947 - ERROR - ❌ No camera found!
2025-11-24 18:10:08,975 - INFO - Frame 346 | PERCLOS: 0.00 | Yaw: -0.8° | Alerts: 1
2025-11-24 18:10:09,093 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:09,093 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:09,093 - ERROR - ❌ No camera found!
2025-11-24 18:10:09,094 - ERROR - ❌ No camera found!
2025-11-24 18:10:09,251 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:09,252 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:09,253 - ERROR - ❌ No camera found!
2025-11-24 18:10:09,254 - ERROR - ❌ No camera found!
2025-11-24 18:10:09,403 - INFO - Frame 348 | PERCLOS: 0.55 | Yaw: -0.2° | Alerts: 2
2025-11-24 18:10:09,407 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:09,407 - ERROR - ❌ No camera found!
2025-11-24 18:10:09,407 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:09,408 - ERROR - ❌ No camera found!
2025-11-24 18:10:09,574 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:09,576 - ERROR - ❌ No camera found!
2025-11-24 18:10:09,576 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:09,578 - ERROR - ❌ No camera found!
2025-11-24 18:10:09,608 - INFO - Frame 350 | PERCLOS: 0.49 | Yaw: 3.0° | Alerts: 2
2025-11-24 18:10:09,730 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:09,731 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:09,731 - ERROR - ❌ No camera found!
2025-11-24 18:10:09,732 - ERROR - ❌ No camera found!
2025-11-24 18:10:09,893 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:09,894 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:09,895 - ERROR - ❌ No camera found!
2025-11-24 18:10:09,896 - ERROR - ❌ No camera found!
2025-11-24 18:10:09,918 - INFO - Frame 352 | PERCLOS: 0.63 | Yaw: 2.4° | Alerts: 2
2025-11-24 18:10:10,042 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:10,042 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:10,044 - ERROR - ❌ No camera found!
2025-11-24 18:10:10,044 - ERROR - ❌ No camera found!
2025-11-24 18:10:10,204 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:10,204 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:10,206 - ERROR - ❌ No camera found!
2025-11-24 18:10:10,206 - ERROR - ❌ No camera found!
2025-11-24 18:10:10,351 - INFO - Frame 354 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-24 18:10:10,353 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:10,353 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:10,354 - ERROR - ❌ No camera found!
2025-11-24 18:10:10,355 - ERROR - ❌ No camera found!
2025-11-24 18:10:10,508 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:10,509 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:10,510 - ERROR - ❌ No camera found!
2025-11-24 18:10:10,511 - ERROR - ❌ No camera found!
2025-11-24 18:10:10,548 - INFO - Frame 356 | PERCLOS: 0.58 | Yaw: 3.9° | Alerts: 2
2025-11-24 18:10:10,664 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:10,666 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:10,666 - ERROR - ❌ No camera found!
2025-11-24 18:10:10,667 - ERROR - ❌ No camera found!
2025-11-24 18:10:10,832 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:10,833 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:10,835 - ERROR - ❌ No camera found!
2025-11-24 18:10:10,835 - ERROR - ❌ No camera found!
2025-11-24 18:10:10,871 - INFO - Frame 358 | PERCLOS: 0.37 | Yaw: 6.1° | Alerts: 2
2025-11-24 18:10:10,994 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:10,994 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:10,996 - ERROR - ❌ No camera found!
2025-11-24 18:10:10,998 - ERROR - ❌ No camera found!
2025-11-24 18:10:11,134 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:11,136 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:11,136 - ERROR - ❌ No camera found!
2025-11-24 18:10:11,141 - ERROR - ❌ No camera found!
2025-11-24 18:10:11,300 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:11,300 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:11,301 - ERROR - ❌ No camera found!
2025-11-24 18:10:11,302 - ERROR - ❌ No camera found!
2025-11-24 18:10:11,318 - INFO - Frame 360 | PERCLOS: 0.52 | Yaw: 5.6° | Alerts: 2
2025-11-24 18:10:11,443 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:11,445 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:11,446 - ERROR - ❌ No camera found!
2025-11-24 18:10:11,446 - ERROR - ❌ No camera found!
2025-11-24 18:10:11,607 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:11,609 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:11,610 - ERROR - ❌ No camera found!
2025-11-24 18:10:11,611 - ERROR - ❌ No camera found!
2025-11-24 18:10:11,632 - INFO - Frame 362 | PERCLOS: 0.38 | Yaw: 5.4° | Alerts: 2
2025-11-24 18:10:11,768 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:11,768 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:11,769 - ERROR - ❌ No camera found!
2025-11-24 18:10:11,769 - ERROR - ❌ No camera found!
2025-11-24 18:10:11,914 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:11,916 - ERROR - ❌ No camera found!
2025-11-24 18:10:11,916 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:11,916 - ERROR - ❌ No camera found!
2025-11-24 18:10:11,943 - INFO - Frame 364 | PERCLOS: 0.46 | Yaw: 5.5° | Alerts: 2
2025-11-24 18:10:12,071 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:12,071 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:12,072 - ERROR - ❌ No camera found!
2025-11-24 18:10:12,074 - ERROR - ❌ No camera found!
2025-11-24 18:10:12,231 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:12,233 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:12,234 - ERROR - ❌ No camera found!
2025-11-24 18:10:12,234 - ERROR - ❌ No camera found!
2025-11-24 18:10:12,397 - INFO - Frame 366 | PERCLOS: 0.50 | Yaw: 5.0° | Alerts: 2
2025-11-24 18:10:12,399 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:12,401 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:12,402 - ERROR - ❌ No camera found!
2025-11-24 18:10:12,402 - ERROR - ❌ No camera found!
2025-11-24 18:10:12,549 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:12,551 - ERROR - ❌ No camera found!
2025-11-24 18:10:12,552 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:12,553 - ERROR - ❌ No camera found!
2025-11-24 18:10:12,588 - INFO - Frame 368 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 1
2025-11-24 18:10:12,722 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:12,722 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:12,722 - ERROR - ❌ No camera found!
2025-11-24 18:10:12,723 - ERROR - ❌ No camera found!
2025-11-24 18:10:12,961 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:12,961 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:12,963 - ERROR - ❌ No camera found!
2025-11-24 18:10:12,963 - INFO - Frame 370 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 1
2025-11-24 18:10:12,964 - ERROR - ❌ No camera found!
2025-11-24 18:10:13,147 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:13,147 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:13,148 - ERROR - ❌ No camera found!
2025-11-24 18:10:13,148 - ERROR - ❌ No camera found!
2025-11-24 18:10:13,421 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:13,422 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:13,422 - ERROR - ❌ No camera found!
2025-11-24 18:10:13,423 - ERROR - ❌ No camera found!
2025-11-24 18:10:13,583 - INFO - Frame 372 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 18:10:13,586 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:13,587 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:13,588 - ERROR - ❌ No camera found!
2025-11-24 18:10:13,589 - ERROR - ❌ No camera found!
2025-11-24 18:10:13,763 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:13,766 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:13,767 - ERROR - ❌ No camera found!
2025-11-24 18:10:13,767 - ERROR - ❌ No camera found!
2025-11-24 18:10:13,942 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:13,943 - INFO - Frame 374 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 18:10:13,944 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:13,947 - ERROR - ❌ No camera found!
2025-11-24 18:10:13,948 - ERROR - ❌ No camera found!
2025-11-24 18:10:14,115 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:14,115 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:14,117 - ERROR - ❌ No camera found!
2025-11-24 18:10:14,117 - ERROR - ❌ No camera found!
2025-11-24 18:10:14,292 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:14,292 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:14,294 - ERROR - ❌ No camera found!
2025-11-24 18:10:14,294 - ERROR - ❌ No camera found!
2025-11-24 18:10:14,295 - INFO - Frame 376 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 18:10:14,468 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:14,470 - ERROR - ❌ No camera found!
2025-11-24 18:10:14,472 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:14,472 - ERROR - ❌ No camera found!
2025-11-24 18:10:14,647 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:14,650 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:14,650 - ERROR - ❌ No camera found!
2025-11-24 18:10:14,651 - ERROR - ❌ No camera found!
2025-11-24 18:10:14,827 - INFO - Frame 378 | PERCLOS: 0.00 | Yaw: 6.1° | Alerts: 1
2025-11-24 18:10:14,830 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:14,831 - ERROR - ❌ No camera found!
2025-11-24 18:10:14,833 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:14,838 - ERROR - ❌ No camera found!
2025-11-24 18:10:15,012 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:15,012 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:15,013 - ERROR - ❌ No camera found!
2025-11-24 18:10:15,015 - ERROR - ❌ No camera found!
2025-11-24 18:10:15,052 - INFO - Frame 380 | PERCLOS: 0.00 | Yaw: 6.8° | Alerts: 1
2025-11-24 18:10:15,191 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:15,194 - ERROR - ❌ No camera found!
2025-11-24 18:10:15,195 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:15,195 - ERROR - ❌ No camera found!
2025-11-24 18:10:15,367 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:15,367 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:15,369 - ERROR - ❌ No camera found!
2025-11-24 18:10:15,370 - ERROR - ❌ No camera found!
2025-11-24 18:10:15,392 - INFO - Frame 382 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 1
2025-11-24 18:10:15,550 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:15,550 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:15,552 - ERROR - ❌ No camera found!
2025-11-24 18:10:15,552 - ERROR - ❌ No camera found!
2025-11-24 18:10:15,724 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:15,726 - ERROR - ❌ No camera found!
2025-11-24 18:10:15,730 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:15,731 - ERROR - ❌ No camera found!
2025-11-24 18:10:15,906 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:15,907 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:15,908 - ERROR - ❌ No camera found!
2025-11-24 18:10:15,909 - ERROR - ❌ No camera found!
2025-11-24 18:10:15,926 - INFO - Frame 384 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-24 18:10:16,074 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:16,076 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:16,076 - ERROR - ❌ No camera found!
2025-11-24 18:10:16,077 - ERROR - ❌ No camera found!
2025-11-24 18:10:16,242 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:16,244 - ERROR - ❌ No camera found!
2025-11-24 18:10:16,245 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:16,245 - ERROR - ❌ No camera found!
2025-11-24 18:10:16,273 - INFO - Frame 386 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-24 18:10:16,425 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:16,425 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:16,426 - ERROR - ❌ No camera found!
2025-11-24 18:10:16,427 - ERROR - ❌ No camera found!
2025-11-24 18:10:16,602 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:16,603 - ERROR - ❌ No camera found!
2025-11-24 18:10:16,609 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:16,611 - ERROR - ❌ No camera found!
2025-11-24 18:10:16,631 - INFO - Frame 388 | PERCLOS: 0.00 | Yaw: 4.9° | Alerts: 1
2025-11-24 18:10:16,787 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:16,789 - ERROR - ❌ No camera found!
2025-11-24 18:10:16,790 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:16,793 - ERROR - ❌ No camera found!
2025-11-24 18:10:16,954 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:16,957 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:16,957 - ERROR - ❌ No camera found!
2025-11-24 18:10:16,959 - ERROR - ❌ No camera found!
2025-11-24 18:10:17,123 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:17,125 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:17,126 - ERROR - ❌ No camera found!
2025-11-24 18:10:17,127 - ERROR - ❌ No camera found!
2025-11-24 18:10:17,144 - INFO - Frame 390 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 1
2025-11-24 18:10:17,298 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:17,298 - ERROR - ❌ No camera found!
2025-11-24 18:10:17,300 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:17,305 - ERROR - ❌ No camera found!
2025-11-24 18:10:17,476 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:17,479 - ERROR - ❌ No camera found!
2025-11-24 18:10:17,479 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:17,480 - ERROR - ❌ No camera found!
2025-11-24 18:10:17,502 - INFO - Frame 392 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 1
2025-11-24 18:10:17,653 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:17,654 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:17,655 - ERROR - ❌ No camera found!
2025-11-24 18:10:17,655 - ERROR - ❌ No camera found!
2025-11-24 18:10:17,820 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:17,824 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:17,826 - ERROR - ❌ No camera found!
2025-11-24 18:10:17,827 - ERROR - ❌ No camera found!
2025-11-24 18:10:17,849 - INFO - Frame 394 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 1
2025-11-24 18:10:17,994 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:17,994 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:17,995 - ERROR - ❌ No camera found!
2025-11-24 18:10:17,995 - ERROR - ❌ No camera found!
2025-11-24 18:10:18,165 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:18,165 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:18,165 - ERROR - ❌ No camera found!
2025-11-24 18:10:18,166 - ERROR - ❌ No camera found!
2025-11-24 18:10:18,337 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:18,337 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:18,338 - ERROR - ❌ No camera found!
2025-11-24 18:10:18,338 - ERROR - ❌ No camera found!
2025-11-24 18:10:18,357 - INFO - Frame 396 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 1
2025-11-24 18:10:18,518 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:18,518 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:18,520 - ERROR - ❌ No camera found!
2025-11-24 18:10:18,520 - ERROR - ❌ No camera found!
2025-11-24 18:10:18,679 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:18,680 - ERROR - ❌ No camera found!
2025-11-24 18:10:18,683 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:18,689 - ERROR - ❌ No camera found!
2025-11-24 18:10:18,708 - INFO - Frame 398 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 1
2025-11-24 18:10:18,855 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:18,856 - ERROR - ❌ No camera found!
2025-11-24 18:10:18,858 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:18,859 - ERROR - ❌ No camera found!
2025-11-24 18:10:19,031 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:19,031 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:19,032 - ERROR - ❌ No camera found!
2025-11-24 18:10:19,033 - ERROR - ❌ No camera found!
2025-11-24 18:10:19,059 - INFO - Frame 400 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 1
2025-11-24 18:10:19,210 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:19,210 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:19,211 - ERROR - ❌ No camera found!
2025-11-24 18:10:19,211 - ERROR - ❌ No camera found!
2025-11-24 18:10:19,383 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:19,386 - ERROR - ❌ No camera found!
2025-11-24 18:10:19,392 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:19,395 - ERROR - ❌ No camera found!
2025-11-24 18:10:19,557 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:19,557 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:19,559 - ERROR - ❌ No camera found!
2025-11-24 18:10:19,559 - ERROR - ❌ No camera found!
2025-11-24 18:10:19,575 - INFO - Frame 402 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 1
2025-11-24 18:10:19,729 - INFO - Video thread started with source: Camera, predictions: False
2025-11-24 18:10:19,730 - INFO - Video thread started with source: Camera, predictions: True
2025-11-24 18:10:19,731 - ERROR - ❌ No camera found!
2025-11-24 18:10:19,731 - ERROR - ❌ No camera found!
2025-11-24 18:10:20,031 - INFO - Frame 404 | PERCLOS: 0.43 | Yaw: 6.7° | Alerts: 2
2025-11-24 18:12:05,207 - INFO - Loading models...
2025-11-24 18:12:05,235 - INFO - ✓ YOLO ONNX loaded
2025-11-24 18:12:05,269 - INFO - ✓ MediaPipe Face Mesh loaded
2025-11-24 18:12:05,276 - INFO - ✓ MediaPipe Pose loaded (for smoke & seatbelt)
2025-11-24 18:12:05,282 - INFO - Video thread started with source: Camera
2025-11-24 18:12:05,282 - INFO - Video thread started with source: Camera
2025-11-24 18:12:05,285 - INFO - Video thread started with source: Camera
2025-11-24 18:12:05,285 - ERROR - ❌ No camera found!
2025-11-24 18:12:05,290 - ERROR - ❌ No camera found!
2025-11-24 18:12:05,507 - INFO - ✓ Camera 0 opened successfully
2025-11-24 18:12:05,513 - INFO - Video thread started with source: Camera
2025-11-24 18:12:05,515 - ERROR - ❌ No camera found!
2025-11-24 18:12:05,515 - INFO - Video thread started with source: Camera
2025-11-24 18:12:05,521 - ERROR - ❌ No camera found!
2025-11-24 18:12:05,715 - INFO - Video thread started with source: Camera
2025-11-24 18:12:05,715 - INFO - Video thread started with source: Camera
2025-11-24 18:12:05,716 - ERROR - ❌ No camera found!
2025-11-24 18:12:05,719 - ERROR - ❌ No camera found!
2025-11-24 18:12:05,891 - INFO - Video thread started with source: Camera
2025-11-24 18:12:05,891 - INFO - Video thread started with source: Camera
2025-11-24 18:12:05,893 - ERROR - ❌ No camera found!
2025-11-24 18:12:05,893 - ERROR - ❌ No camera found!
2025-11-24 18:12:06,116 - INFO - Video thread started with source: Camera
2025-11-24 18:12:06,118 - INFO - Video thread started with source: Camera
2025-11-24 18:12:06,119 - ERROR - ❌ No camera found!
2025-11-24 18:12:06,120 - ERROR - ❌ No camera found!
2025-11-24 18:12:06,323 - INFO - Video thread started with source: Camera
2025-11-24 18:12:06,325 - INFO - Video thread started with source: Camera
2025-11-24 18:12:06,326 - ERROR - ❌ No camera found!
2025-11-24 18:12:06,326 - ERROR - ❌ No camera found!
2025-11-24 18:12:06,335 - INFO - Frame 0 | PERCLOS: 0.37 | Yaw: 6.5° | Alerts: 2
2025-11-24 18:12:06,511 - INFO - Video thread started with source: Camera
2025-11-24 18:12:06,513 - INFO - Video thread started with source: Camera
2025-11-24 18:12:06,513 - ERROR - ❌ No camera found!
2025-11-24 18:12:06,514 - ERROR - ❌ No camera found!
2025-11-24 18:12:06,716 - INFO - Video thread started with source: Camera
2025-11-24 18:12:06,718 - ERROR - ❌ No camera found!
2025-11-24 18:12:06,718 - INFO - Video thread started with source: Camera
2025-11-24 18:12:06,718 - ERROR - ❌ No camera found!
2025-11-24 18:12:06,719 - INFO - Frame 2 | PERCLOS: 0.26 | Yaw: 6.4° | Alerts: 1
2025-11-24 18:12:06,913 - INFO - Video thread started with source: Camera
2025-11-24 18:12:06,915 - INFO - Video thread started with source: Camera
2025-11-24 18:12:06,915 - ERROR - ❌ No camera found!
2025-11-24 18:12:06,918 - ERROR - ❌ No camera found!
2025-11-24 18:12:06,949 - INFO - Frame 4 | PERCLOS: 0.12 | Yaw: 6.4° | Alerts: 1
2025-11-24 18:12:07,120 - INFO - Video thread started with source: Camera
2025-11-24 18:12:07,121 - INFO - Video thread started with source: Camera
2025-11-24 18:12:07,124 - ERROR - ❌ No camera found!
2025-11-24 18:12:07,125 - ERROR - ❌ No camera found!
2025-11-24 18:12:07,318 - INFO - Video thread started with source: Camera
2025-11-24 18:12:07,319 - INFO - Video thread started with source: Camera
2025-11-24 18:12:07,320 - ERROR - ❌ No camera found!
2025-11-24 18:12:07,320 - ERROR - ❌ No camera found!
2025-11-24 18:12:07,523 - INFO - Video thread started with source: Camera
2025-11-24 18:12:07,523 - INFO - Video thread started with source: Camera
2025-11-24 18:12:07,525 - ERROR - ❌ No camera found!
2025-11-24 18:12:07,525 - ERROR - ❌ No camera found!
2025-11-24 18:12:07,539 - INFO - Frame 6 | PERCLOS: 0.02 | Yaw: 6.9° | Alerts: 1
2025-11-24 18:12:07,718 - INFO - Video thread started with source: Camera
2025-11-24 18:12:07,720 - INFO - Video thread started with source: Camera
2025-11-24 18:12:07,721 - ERROR - ❌ No camera found!
2025-11-24 18:12:07,723 - ERROR - ❌ No camera found!
2025-11-24 18:12:07,913 - INFO - Video thread started with source: Camera
2025-11-24 18:12:07,913 - INFO - Video thread started with source: Camera
2025-11-24 18:12:07,916 - ERROR - ❌ No camera found!
2025-11-24 18:12:07,917 - ERROR - ❌ No camera found!
2025-11-24 18:12:07,944 - INFO - Frame 8 | PERCLOS: 0.00 | Yaw: 5.9° | Alerts: 1
2025-11-24 18:12:08,124 - INFO - Video thread started with source: Camera
2025-11-24 18:12:08,124 - INFO - Video thread started with source: Camera
2025-11-24 18:12:08,125 - ERROR - ❌ No camera found!
2025-11-24 18:12:08,126 - ERROR - ❌ No camera found!
2025-11-24 18:12:08,358 - INFO - Video thread started with source: Camera
2025-11-24 18:12:08,358 - INFO - Video thread started with source: Camera
2025-11-24 18:12:08,359 - ERROR - ❌ No camera found!
2025-11-24 18:12:08,363 - ERROR - ❌ No camera found!
2025-11-24 18:12:08,384 - INFO - Frame 10 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 18:12:08,564 - INFO - Video thread started with source: Camera
2025-11-24 18:12:08,569 - ERROR - ❌ No camera found!
2025-11-24 18:12:08,571 - INFO - Video thread started with source: Camera
2025-11-24 18:12:08,571 - ERROR - ❌ No camera found!
2025-11-24 18:12:08,778 - INFO - Video thread started with source: Camera
2025-11-24 18:12:08,780 - INFO - Video thread started with source: Camera
2025-11-24 18:12:08,782 - ERROR - ❌ No camera found!
2025-11-24 18:12:08,844 - ERROR - ❌ No camera found!
2025-11-24 18:12:09,035 - INFO - Video thread started with source: Camera
2025-11-24 18:12:09,036 - INFO - Video thread started with source: Camera
2025-11-24 18:12:09,036 - ERROR - ❌ No camera found!
2025-11-24 18:12:09,037 - ERROR - ❌ No camera found!
2025-11-24 18:12:09,053 - INFO - Frame 12 | PERCLOS: 0.02 | Yaw: 5.2° | Alerts: 1
2025-11-24 18:12:09,202 - INFO - Video thread started with source: Camera
2025-11-24 18:12:09,202 - INFO - Video thread started with source: Camera
2025-11-24 18:12:09,203 - ERROR - ❌ No camera found!
2025-11-24 18:12:09,204 - ERROR - ❌ No camera found!
2025-11-24 18:12:09,363 - INFO - Video thread started with source: Camera
2025-11-24 18:12:09,366 - ERROR - ❌ No camera found!
2025-11-24 18:12:09,366 - INFO - Video thread started with source: Camera
2025-11-24 18:12:09,368 - ERROR - ❌ No camera found!
2025-11-24 18:12:09,368 - INFO - Frame 14 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-24 18:12:09,510 - INFO - Video thread started with source: Camera
2025-11-24 18:12:09,510 - INFO - Video thread started with source: Camera
2025-11-24 18:12:09,510 - ERROR - ❌ No camera found!
2025-11-24 18:12:09,511 - ERROR - ❌ No camera found!
2025-11-24 18:12:09,666 - INFO - Video thread started with source: Camera
2025-11-24 18:12:09,666 - INFO - Video thread started with source: Camera
2025-11-24 18:12:09,667 - ERROR - ❌ No camera found!
2025-11-24 18:12:09,668 - ERROR - ❌ No camera found!
2025-11-24 18:12:09,690 - INFO - Frame 16 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 18:12:09,832 - INFO - Video thread started with source: Camera
2025-11-24 18:12:09,832 - INFO - Video thread started with source: Camera
2025-11-24 18:12:09,834 - ERROR - ❌ No camera found!
2025-11-24 18:12:09,834 - ERROR - ❌ No camera found!
2025-11-24 18:12:10,007 - INFO - Video thread started with source: Camera
2025-11-24 18:12:10,009 - INFO - Video thread started with source: Camera
2025-11-24 18:12:10,009 - ERROR - ❌ No camera found!
2025-11-24 18:12:10,010 - ERROR - ❌ No camera found!
2025-11-24 18:12:10,164 - INFO - Frame 18 | PERCLOS: 0.33 | Yaw: 3.8° | Alerts: 2
2025-11-24 18:12:10,169 - INFO - Video thread started with source: Camera
2025-11-24 18:12:10,169 - INFO - Video thread started with source: Camera
2025-11-24 18:12:10,170 - ERROR - ❌ No camera found!
2025-11-24 18:12:10,170 - ERROR - ❌ No camera found!
2025-11-24 18:12:10,335 - INFO - Video thread started with source: Camera
2025-11-24 18:12:10,335 - INFO - Video thread started with source: Camera
2025-11-24 18:12:10,337 - ERROR - ❌ No camera found!
2025-11-24 18:12:10,338 - ERROR - ❌ No camera found!
2025-11-24 18:12:10,374 - INFO - Frame 20 | PERCLOS: 0.05 | Yaw: 5.0° | Alerts: 1
2025-11-24 18:12:10,498 - INFO - Video thread started with source: Camera
2025-11-24 18:12:10,498 - INFO - Video thread started with source: Camera
2025-11-24 18:12:10,499 - ERROR - ❌ No camera found!
2025-11-24 18:12:10,500 - ERROR - ❌ No camera found!
2025-11-24 18:12:10,662 - INFO - Video thread started with source: Camera
2025-11-24 18:12:10,665 - INFO - Video thread started with source: Camera
2025-11-24 18:12:10,665 - ERROR - ❌ No camera found!
2025-11-24 18:12:10,666 - ERROR - ❌ No camera found!
2025-11-24 18:12:10,666 - INFO - Frame 22 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 1
2025-11-24 18:12:10,816 - INFO - Video thread started with source: Camera
2025-11-24 18:12:10,818 - INFO - Video thread started with source: Camera
2025-11-24 18:12:10,818 - ERROR - ❌ No camera found!
2025-11-24 18:12:10,820 - ERROR - ❌ No camera found!
2025-11-24 18:12:10,988 - INFO - Video thread started with source: Camera
2025-11-24 18:12:11,053 - ERROR - ❌ No camera found!
2025-11-24 18:12:11,147 - INFO - Frame 24 | PERCLOS: 0.33 | Yaw: 4.5° | Alerts: 2
2025-11-24 18:12:11,149 - INFO - Video thread started with source: Camera
2025-11-24 18:12:11,150 - ERROR - ❌ No camera found!
2025-11-24 18:12:11,242 - INFO - Video thread started with source: Camera
2025-11-24 18:12:11,243 - ERROR - ❌ No camera found!
2025-11-24 18:12:11,277 - INFO - Frame 26 | PERCLOS: 0.12 | Yaw: 4.9° | Alerts: 1
2025-11-24 18:12:11,332 - INFO - Video thread started with source: Camera
2025-11-24 18:12:11,333 - ERROR - ❌ No camera found!
2025-11-24 18:12:11,420 - INFO - Video thread started with source: Camera
2025-11-24 18:12:11,422 - ERROR - ❌ No camera found!
2025-11-24 18:12:11,448 - INFO - Frame 28 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-24 18:12:11,513 - INFO - Video thread started with source: Camera
2025-11-24 18:12:11,514 - ERROR - ❌ No camera found!
2025-11-24 18:12:11,607 - INFO - Video thread started with source: Camera
2025-11-24 18:12:11,608 - ERROR - ❌ No camera found!
2025-11-24 18:12:11,705 - INFO - Video thread started with source: Camera
2025-11-24 18:12:11,706 - ERROR - ❌ No camera found!
2025-11-24 18:12:11,727 - INFO - Frame 30 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 18:12:11,800 - INFO - Video thread started with source: Camera
2025-11-24 18:12:11,801 - ERROR - ❌ No camera found!
2025-11-24 18:12:11,894 - INFO - Video thread started with source: Camera
2025-11-24 18:12:11,896 - ERROR - ❌ No camera found!
2025-11-24 18:12:11,924 - INFO - Frame 32 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-24 18:12:11,983 - INFO - Video thread started with source: Camera
2025-11-24 18:12:11,984 - ERROR - ❌ No camera found!
2025-11-24 18:12:12,077 - INFO - Video thread started with source: Camera
2025-11-24 18:12:12,078 - ERROR - ❌ No camera found!
2025-11-24 18:12:12,106 - INFO - Frame 34 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-24 18:12:12,167 - INFO - Video thread started with source: Camera
2025-11-24 18:12:12,168 - ERROR - ❌ No camera found!
2025-11-24 18:12:12,255 - INFO - Video thread started with source: Camera
2025-11-24 18:12:12,257 - ERROR - ❌ No camera found!
2025-11-24 18:12:12,348 - INFO - Video thread started with source: Camera
2025-11-24 18:12:12,349 - ERROR - ❌ No camera found!
2025-11-24 18:12:12,369 - INFO - Frame 36 | PERCLOS: 0.00 | Yaw: 5.9° | Alerts: 1
2025-11-24 18:12:12,442 - INFO - Video thread started with source: Camera
2025-11-24 18:12:12,443 - ERROR - ❌ No camera found!
2025-11-24 18:12:12,531 - INFO - Video thread started with source: Camera
2025-11-24 18:12:12,533 - ERROR - ❌ No camera found!
2025-11-24 18:12:12,562 - INFO - Frame 38 | PERCLOS: 0.00 | Yaw: 6.9° | Alerts: 1
2025-11-24 18:12:12,630 - INFO - Video thread started with source: Camera
2025-11-24 18:12:12,631 - ERROR - ❌ No camera found!
2025-11-24 18:12:12,724 - INFO - Video thread started with source: Camera
2025-11-24 18:12:12,725 - ERROR - ❌ No camera found!
2025-11-24 18:12:12,757 - INFO - Frame 40 | PERCLOS: 0.00 | Yaw: 7.2° | Alerts: 1
2025-11-24 18:12:12,827 - INFO - Video thread started with source: Camera
2025-11-24 18:12:12,828 - ERROR - ❌ No camera found!
2025-11-24 18:12:12,916 - INFO - Video thread started with source: Camera
2025-11-24 18:12:12,918 - ERROR - ❌ No camera found!
2025-11-24 18:12:13,011 - INFO - Video thread started with source: Camera
2025-11-24 18:12:13,012 - ERROR - ❌ No camera found!
2025-11-24 18:12:13,030 - INFO - Frame 42 | PERCLOS: 0.00 | Yaw: 7.5° | Alerts: 1
2025-11-24 18:12:13,110 - INFO - Video thread started with source: Camera
2025-11-24 18:12:13,111 - ERROR - ❌ No camera found!
2025-11-24 18:12:13,200 - INFO - Video thread started with source: Camera
2025-11-24 18:12:13,201 - ERROR - ❌ No camera found!
2025-11-24 18:12:13,232 - INFO - Frame 44 | PERCLOS: 0.00 | Yaw: 7.5° | Alerts: 1
2025-11-24 18:12:13,290 - INFO - Video thread started with source: Camera
2025-11-24 18:12:13,291 - ERROR - ❌ No camera found!
2025-11-24 18:12:13,378 - INFO - Video thread started with source: Camera
2025-11-24 18:12:13,379 - ERROR - ❌ No camera found!
2025-11-24 18:12:13,410 - INFO - Frame 46 | PERCLOS: 0.00 | Yaw: 6.5° | Alerts: 1
2025-11-24 18:12:13,474 - INFO - Video thread started with source: Camera
2025-11-24 18:12:13,475 - ERROR - ❌ No camera found!
2025-11-24 18:12:13,575 - INFO - Video thread started with source: Camera
2025-11-24 18:12:13,576 - ERROR - ❌ No camera found!
2025-11-24 18:12:13,680 - INFO - Video thread started with source: Camera
2025-11-24 18:12:13,681 - ERROR - ❌ No camera found!
2025-11-24 18:12:13,702 - INFO - Frame 48 | PERCLOS: 0.00 | Yaw: 7.7° | Alerts: 1
2025-11-24 18:12:13,785 - INFO - Video thread started with source: Camera
2025-11-24 18:12:13,785 - ERROR - ❌ No camera found!
2025-11-24 18:12:13,890 - INFO - Video thread started with source: Camera
2025-11-24 18:12:13,891 - ERROR - ❌ No camera found!
2025-11-24 18:12:13,919 - INFO - Frame 50 | PERCLOS: 0.00 | Yaw: 9.4° | Alerts: 1
2025-11-24 18:12:13,995 - INFO - Video thread started with source: Camera
2025-11-24 18:12:13,996 - ERROR - ❌ No camera found!
2025-11-24 18:12:14,096 - INFO - Video thread started with source: Camera
2025-11-24 18:12:14,097 - ERROR - ❌ No camera found!
2025-11-24 18:12:14,132 - INFO - Frame 52 | PERCLOS: 0.00 | Yaw: 9.3° | Alerts: 1
2025-11-24 18:12:14,234 - INFO - Video thread started with source: Camera
2025-11-24 18:12:14,235 - ERROR - ❌ No camera found!
2025-11-24 18:12:14,331 - INFO - Video thread started with source: Camera
2025-11-24 18:12:14,333 - ERROR - ❌ No camera found!
2025-11-24 18:12:14,429 - INFO - Video thread started with source: Camera
2025-11-24 18:12:14,430 - ERROR - ❌ No camera found!
2025-11-24 18:12:14,450 - INFO - Frame 54 | PERCLOS: 0.00 | Yaw: 11.6° | Alerts: 1
2025-11-24 18:12:14,525 - INFO - Video thread started with source: Camera
2025-11-24 18:12:14,526 - ERROR - ❌ No camera found!
2025-11-24 18:12:14,621 - INFO - Video thread started with source: Camera
2025-11-24 18:12:14,622 - ERROR - ❌ No camera found!
2025-11-24 18:12:14,655 - INFO - Frame 56 | PERCLOS: 0.00 | Yaw: 13.2° | Alerts: 1
2025-11-24 18:12:14,716 - INFO - Video thread started with source: Camera
2025-11-24 18:12:14,718 - ERROR - ❌ No camera found!
2025-11-24 18:12:14,811 - INFO - Video thread started with source: Camera
2025-11-24 18:12:14,813 - ERROR - ❌ No camera found!
2025-11-24 18:12:14,844 - INFO - Frame 58 | PERCLOS: 0.00 | Yaw: 14.3° | Alerts: 1
2025-11-24 18:12:14,930 - INFO - Video thread started with source: Camera
2025-11-24 18:12:14,934 - ERROR - ❌ No camera found!
2025-11-24 18:12:15,099 - INFO - Camera disabled
2025-11-24 18:12:15,222 - INFO - Frame 60 | PERCLOS: 0.00 | Yaw: 13.8° | Alerts: 1
2025-11-24 18:12:15,422 - INFO - Frame 62 | PERCLOS: 0.00 | Yaw: 13.7° | Alerts: 1
2025-11-24 18:12:15,607 - INFO - Frame 64 | PERCLOS: 0.00 | Yaw: 13.5° | Alerts: 1
2025-11-24 18:12:15,877 - INFO - Frame 66 | PERCLOS: 0.00 | Yaw: 12.9° | Alerts: 1
2025-11-24 18:12:16,071 - INFO - Frame 68 | PERCLOS: 0.00 | Yaw: 13.8° | Alerts: 1
2025-11-24 18:12:16,320 - INFO - Frame 70 | PERCLOS: 0.00 | Yaw: 12.5° | Alerts: 1
2025-11-24 18:12:16,598 - INFO - Frame 72 | PERCLOS: 0.00 | Yaw: 13.0° | Alerts: 1
2025-11-24 18:12:16,785 - INFO - Frame 74 | PERCLOS: 0.00 | Yaw: 12.1° | Alerts: 1
2025-11-24 18:12:16,974 - INFO - Frame 76 | PERCLOS: 0.00 | Yaw: 12.0° | Alerts: 1
2025-11-24 18:12:17,244 - INFO - Frame 78 | PERCLOS: 0.00 | Yaw: 12.2° | Alerts: 1
2025-11-24 18:12:17,442 - INFO - Frame 80 | PERCLOS: 0.00 | Yaw: 11.3° | Alerts: 1
2025-11-24 18:12:17,625 - INFO - Frame 82 | PERCLOS: 0.00 | Yaw: 10.7° | Alerts: 1
2025-11-24 18:12:17,887 - INFO - Frame 84 | PERCLOS: 0.00 | Yaw: 10.9° | Alerts: 1
2025-11-24 18:12:18,089 - INFO - Frame 86 | PERCLOS: 0.00 | Yaw: 10.2° | Alerts: 1
2025-11-24 18:12:18,269 - INFO - Frame 88 | PERCLOS: 0.00 | Yaw: 8.6° | Alerts: 1
2025-11-24 18:12:18,536 - INFO - Frame 90 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 1
2025-11-24 18:12:18,736 - INFO - Frame 92 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 1
2025-11-24 18:12:18,922 - INFO - Frame 94 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 18:12:19,250 - INFO - Frame 96 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-24 18:12:19,532 - INFO - Frame 98 | PERCLOS: 0.37 | Yaw: 5.3° | Alerts: 2
2025-11-24 18:12:19,763 - INFO - Frame 100 | PERCLOS: 0.00 | Yaw: 8.2° | Alerts: 1
2025-11-24 18:12:20,053 - INFO - Frame 102 | PERCLOS: 0.00 | Yaw: 10.5° | Alerts: 1
2025-11-24 18:12:20,256 - INFO - Frame 104 | PERCLOS: 0.00 | Yaw: 10.9° | Alerts: 1
2025-11-24 18:12:20,442 - INFO - Frame 106 | PERCLOS: 0.00 | Yaw: 11.6° | Alerts: 1
2025-11-24 18:12:20,714 - INFO - Frame 108 | PERCLOS: 0.00 | Yaw: 10.7° | Alerts: 1
2025-11-24 18:12:20,981 - INFO - Frame 110 | PERCLOS: 0.00 | Yaw: 10.8° | Alerts: 1
2025-11-24 18:12:21,182 - INFO - Frame 112 | PERCLOS: 0.00 | Yaw: 10.4° | Alerts: 1
2025-11-24 18:12:21,455 - INFO - Frame 114 | PERCLOS: 0.00 | Yaw: 10.2° | Alerts: 1
2025-11-24 18:12:21,719 - INFO - Frame 116 | PERCLOS: 0.00 | Yaw: 10.5° | Alerts: 1
2025-11-24 18:12:21,949 - INFO - Frame 118 | PERCLOS: 0.00 | Yaw: 10.4° | Alerts: 1
2025-11-24 18:12:22,299 - INFO - Frame 120 | PERCLOS: 0.00 | Yaw: 10.4° | Alerts: 1
2025-11-24 18:12:22,518 - INFO - Frame 122 | PERCLOS: 0.00 | Yaw: 10.9° | Alerts: 1
2025-11-24 18:12:22,707 - INFO - Frame 124 | PERCLOS: 0.00 | Yaw: 11.3° | Alerts: 1
2025-11-24 18:12:22,972 - INFO - Frame 126 | PERCLOS: 0.00 | Yaw: 10.9° | Alerts: 1
2025-11-24 18:12:23,174 - INFO - Frame 128 | PERCLOS: 0.00 | Yaw: 10.9° | Alerts: 1
2025-11-24 18:12:23,422 - INFO - Frame 130 | PERCLOS: 0.00 | Yaw: 10.9° | Alerts: 1
2025-11-24 18:12:23,704 - INFO - Frame 132 | PERCLOS: 0.00 | Yaw: 10.9° | Alerts: 1
2025-11-24 18:12:23,909 - INFO - Frame 134 | PERCLOS: 0.00 | Yaw: 11.4° | Alerts: 1
2025-11-24 18:12:24,111 - INFO - Frame 136 | PERCLOS: 0.00 | Yaw: 10.6° | Alerts: 1
2025-11-24 18:12:24,395 - INFO - Frame 138 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 1
2025-11-24 18:12:24,664 - INFO - Frame 140 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 18:12:24,890 - INFO - Frame 142 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 18:12:25,159 - INFO - Frame 144 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 18:12:25,432 - INFO - Frame 146 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 18:12:25,669 - INFO - Frame 148 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 18:12:26,040 - INFO - Frame 150 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 18:12:26,273 - INFO - Frame 152 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-24 18:12:26,460 - INFO - Frame 154 | PERCLOS: 0.00 | Yaw: 7.1° | Alerts: 1
2025-11-24 18:12:26,725 - INFO - Frame 156 | PERCLOS: 0.00 | Yaw: 7.2° | Alerts: 1
2025-11-24 18:12:26,913 - INFO - Frame 158 | PERCLOS: 0.00 | Yaw: 7.6° | Alerts: 1
2025-11-24 18:12:27,103 - INFO - Frame 160 | PERCLOS: 0.00 | Yaw: 7.9° | Alerts: 1
2025-11-24 18:12:27,370 - INFO - Frame 162 | PERCLOS: 0.00 | Yaw: 7.5° | Alerts: 1
2025-11-24 18:12:27,633 - INFO - Frame 164 | PERCLOS: 0.00 | Yaw: 7.0° | Alerts: 1
2025-11-24 18:12:27,843 - INFO - Frame 166 | PERCLOS: 0.00 | Yaw: 6.1° | Alerts: 1
2025-11-24 18:12:28,113 - INFO - Frame 168 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 1
2025-11-24 18:12:28,312 - INFO - Frame 170 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 1
2025-11-24 18:12:28,514 - INFO - Frame 172 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 1
2025-11-24 18:12:28,773 - INFO - Frame 174 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 1
2025-11-24 18:12:28,961 - INFO - Frame 176 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 1
2025-11-24 18:12:29,144 - INFO - Frame 178 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 1
2025-11-24 18:12:29,414 - INFO - Frame 180 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 1
2025-11-24 18:12:29,609 - INFO - Frame 182 | PERCLOS: 0.00 | Yaw: 5.4° | Alerts: 1
2025-11-24 18:12:29,871 - INFO - Frame 184 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 1
2025-11-24 18:12:30,181 - INFO - Frame 186 | PERCLOS: 0.00 | Yaw: 5.4° | Alerts: 1
2025-11-24 18:12:30,411 - INFO - Frame 188 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-24 18:12:30,646 - INFO - Frame 190 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-24 18:12:30,946 - INFO - Frame 192 | PERCLOS: 0.00 | Yaw: 4.8° | Alerts: 1
2025-11-24 18:12:31,144 - INFO - Frame 194 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 1
2025-11-24 18:12:31,412 - INFO - Frame 196 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 1
2025-11-24 18:12:31,715 - INFO - Frame 198 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 1
2025-11-24 18:12:31,949 - INFO - Frame 200 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 1
2025-11-24 18:12:32,140 - INFO - Frame 202 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 1
2025-11-24 18:12:32,478 - INFO - Frame 204 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 1
2025-11-24 18:12:32,701 - INFO - Frame 206 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 1
2025-11-24 18:12:32,891 - INFO - Frame 208 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 1
2025-11-24 18:12:33,306 - INFO - Frame 210 | PERCLOS: 0.15 | Yaw: 1.4° | Alerts: 1
2025-11-24 18:12:33,513 - INFO - Frame 212 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 1
2025-11-24 18:12:33,735 - INFO - Frame 214 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 1
2025-11-24 18:12:34,017 - INFO - Frame 216 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 1
2025-11-24 18:12:34,219 - INFO - Frame 218 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 1
2025-11-24 18:12:34,414 - INFO - Frame 220 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 18:12:34,760 - INFO - Frame 222 | PERCLOS: 0.00 | Yaw: 6.3° | Alerts: 1
2025-11-24 18:12:34,982 - INFO - Frame 224 | PERCLOS: 0.00 | Yaw: 8.4° | Alerts: 1
2025-11-24 18:12:35,170 - INFO - Frame 226 | PERCLOS: 0.00 | Yaw: 9.3° | Alerts: 1
2025-11-24 18:12:35,425 - INFO - Frame 228 | PERCLOS: 0.00 | Yaw: 9.2° | Alerts: 1
2025-11-24 18:12:35,615 - INFO - Frame 230 | PERCLOS: 0.00 | Yaw: 9.0° | Alerts: 1
2025-11-24 18:12:35,844 - INFO - Frame 232 | PERCLOS: 0.00 | Yaw: 9.3° | Alerts: 1
2025-11-24 18:12:36,145 - INFO - Frame 234 | PERCLOS: 0.00 | Yaw: 8.9° | Alerts: 1
2025-11-24 18:12:36,282 - INFO - Video file uploaded: assets/temp_videos/Screen Recording 2025-11-24 at 6.07.31 PM.mov
2025-11-24 18:12:36,442 - INFO - Frame 236 | PERCLOS: 0.00 | Yaw: 9.3° | Alerts: 1
2025-11-24 18:12:36,638 - INFO - Frame 238 | PERCLOS: 0.00 | Yaw: 9.1° | Alerts: 1
2025-11-24 18:12:36,908 - INFO - Frame 240 | PERCLOS: 0.00 | Yaw: 8.9° | Alerts: 1
2025-11-24 18:12:37,108 - INFO - Frame 242 | PERCLOS: 0.00 | Yaw: 9.2° | Alerts: 1
2025-11-24 18:12:37,298 - INFO - Frame 244 | PERCLOS: 0.00 | Yaw: 8.9° | Alerts: 1
2025-11-24 18:12:37,575 - INFO - Frame 246 | PERCLOS: 0.15 | Yaw: 9.3° | Alerts: 1
2025-11-24 18:12:37,780 - INFO - Frame 248 | PERCLOS: 0.00 | Yaw: 10.0° | Alerts: 1
2025-11-24 18:12:38,034 - INFO - Frame 250 | PERCLOS: 0.00 | Yaw: 9.9° | Alerts: 1
2025-11-24 18:12:38,334 - INFO - Frame 252 | PERCLOS: 0.00 | Yaw: 9.8° | Alerts: 1
2025-11-24 18:12:38,547 - INFO - Frame 254 | PERCLOS: 0.00 | Yaw: 9.2° | Alerts: 1
2025-11-24 18:12:38,752 - INFO - Frame 256 | PERCLOS: 0.00 | Yaw: 9.3° | Alerts: 1
2025-11-24 18:12:39,041 - INFO - Frame 258 | PERCLOS: 0.00 | Yaw: 9.4° | Alerts: 1
2025-11-24 18:12:39,258 - INFO - Frame 260 | PERCLOS: 0.02 | Yaw: 7.7° | Alerts: 1
2025-11-24 18:12:39,448 - INFO - Frame 262 | PERCLOS: 0.00 | Yaw: 4.9° | Alerts: 1
2025-11-24 18:12:39,718 - INFO - Frame 264 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-24 18:12:39,924 - INFO - Frame 266 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 1
2025-11-24 18:12:40,114 - INFO - Frame 268 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 1
2025-11-24 18:12:40,392 - INFO - Frame 270 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 1
2025-11-24 18:12:40,663 - INFO - Frame 272 | PERCLOS: 0.41 | Yaw: 4.1° | Alerts: 2
2025-11-24 18:12:40,942 - INFO - Frame 274 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 1
2025-11-24 18:12:41,312 - INFO - Frame 276 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 1
2025-11-24 18:12:41,505 - INFO - Frame 278 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-24 18:12:41,712 - INFO - Frame 280 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-24 18:12:41,980 - INFO - Frame 282 | PERCLOS: 0.00 | Yaw: 7.6° | Alerts: 1
2025-11-24 18:12:42,187 - INFO - Frame 284 | PERCLOS: 0.00 | Yaw: 8.5° | Alerts: 1
2025-11-24 18:12:42,385 - INFO - Frame 286 | PERCLOS: 0.00 | Yaw: 9.0° | Alerts: 1
2025-11-24 18:12:42,666 - INFO - Frame 288 | PERCLOS: 0.00 | Yaw: 9.8° | Alerts: 1
2025-11-24 18:12:42,853 - INFO - Frame 290 | PERCLOS: 0.00 | Yaw: 10.8° | Alerts: 1
2025-11-24 18:12:43,045 - INFO - Frame 292 | PERCLOS: 0.00 | Yaw: 11.1° | Alerts: 1
2025-11-24 18:12:43,325 - INFO - Frame 294 | PERCLOS: 0.00 | Yaw: 11.2° | Alerts: 1
2025-11-24 18:12:43,544 - INFO - Frame 296 | PERCLOS: 0.00 | Yaw: 10.8° | Alerts: 1
2025-11-24 18:12:43,737 - INFO - Frame 298 | PERCLOS: 0.00 | Yaw: 10.3° | Alerts: 1
2025-11-24 18:12:44,088 - INFO - Frame 300 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 1
2025-11-24 18:12:44,300 - INFO - Frame 302 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 1
2025-11-24 18:12:44,529 - INFO - Frame 304 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 1
2025-11-24 18:12:44,838 - INFO - Frame 306 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 1
2025-11-24 18:12:45,053 - INFO - Frame 308 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 1
2025-11-24 18:12:45,252 - INFO - Frame 310 | PERCLOS: 0.00 | Yaw: 4.1° | Alerts: 1
2025-11-24 18:12:45,512 - INFO - Frame 312 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-24 18:12:45,710 - INFO - Frame 314 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 1
2025-11-24 18:12:45,902 - INFO - Frame 316 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 1
2025-11-24 18:12:46,175 - INFO - Frame 318 | PERCLOS: 0.00 | Yaw: 4.7° | Alerts: 1
2025-11-24 18:12:46,372 - INFO - Frame 320 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-24 18:12:46,579 - INFO - Frame 322 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-24 18:12:46,864 - INFO - Frame 324 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 18:12:47,180 - INFO - Frame 326 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 18:12:47,447 - INFO - Frame 328 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 18:12:47,733 - INFO - Frame 330 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 18:12:47,937 - INFO - Frame 332 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 18:12:48,125 - INFO - Frame 334 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 18:12:48,397 - INFO - Frame 336 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 18:12:48,593 - INFO - Frame 338 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 18:12:48,770 - INFO - Frame 340 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 1
2025-11-24 18:12:49,034 - INFO - Frame 342 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 18:12:49,240 - INFO - Frame 344 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 18:12:49,537 - INFO - Frame 346 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 1
2025-11-24 18:12:49,867 - INFO - Frame 348 | PERCLOS: 0.16 | Yaw: 4.4° | Alerts: 1
2025-11-24 18:12:50,161 - INFO - Frame 350 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 18:12:50,417 - INFO - Frame 352 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 1
2025-11-24 18:12:50,727 - INFO - Frame 354 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-24 18:12:50,933 - INFO - Frame 356 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:12:51,189 - INFO - Frame 358 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 18:12:51,523 - INFO - Frame 360 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 1
2025-11-24 18:12:51,740 - INFO - Frame 362 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 1
2025-11-24 18:12:51,920 - INFO - Frame 364 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 1
2025-11-24 18:12:52,196 - INFO - Frame 366 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 1
2025-11-24 18:12:52,466 - INFO - Frame 368 | PERCLOS: 0.00 | Yaw: -0.8° | Alerts: 1
2025-11-24 18:12:52,684 - INFO - Frame 370 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 1
2025-11-24 18:12:52,974 - INFO - Frame 372 | PERCLOS: 0.00 | Yaw: -1.1° | Alerts: 1
2025-11-24 18:12:53,245 - INFO - Frame 374 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 1
2025-11-24 18:12:53,454 - INFO - Frame 376 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 1
2025-11-24 18:12:53,720 - INFO - Frame 378 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 1
2025-11-24 18:12:53,917 - INFO - Frame 380 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 1
2025-11-24 18:12:54,149 - INFO - Frame 382 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 1
2025-11-24 18:12:54,451 - INFO - Frame 384 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 1
2025-11-24 18:12:54,657 - INFO - Frame 386 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 1
2025-11-24 18:12:54,842 - INFO - Frame 388 | PERCLOS: 0.00 | Yaw: -1.1° | Alerts: 1
2025-11-24 18:12:55,108 - INFO - Frame 390 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 1
2025-11-24 18:12:55,437 - INFO - Frame 392 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 1
2025-11-24 18:12:55,719 - INFO - Frame 394 | PERCLOS: 0.00 | Yaw: -0.3° | Alerts: 1
2025-11-24 18:12:56,024 - INFO - Frame 396 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 1
2025-11-24 18:12:56,235 - INFO - Frame 398 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 1
2025-11-24 18:12:56,426 - INFO - Frame 400 | PERCLOS: 0.00 | Yaw: 9.1° | Alerts: 1
2025-11-24 18:12:56,686 - INFO - Frame 402 | PERCLOS: 0.00 | Yaw: 12.7° | Alerts: 1
2025-11-24 18:12:56,950 - INFO - Frame 404 | PERCLOS: 0.00 | Yaw: 12.9° | Alerts: 1
2025-11-24 18:12:57,097 - INFO - Frame 406 | PERCLOS: 0.00 | Yaw: 13.9° | Alerts: 1
2025-11-24 18:12:57,464 - INFO - Frame 408 | PERCLOS: 0.00 | Yaw: 13.6° | Alerts: 1
2025-11-24 18:12:57,656 - INFO - Frame 410 | PERCLOS: 0.00 | Yaw: 15.4° | Alerts: 1
2025-11-24 18:12:57,860 - INFO - Frame 412 | PERCLOS: 0.00 | Yaw: 16.0° | Alerts: 1
2025-11-24 18:12:58,116 - INFO - Frame 414 | PERCLOS: 0.00 | Yaw: 15.2° | Alerts: 1
2025-11-24 18:12:58,289 - INFO - Camera enabled
2025-11-24 18:12:58,299 - INFO - Video thread started with source: assets/temp_videos/Screen Recording 2025-11-24 at 6.07.31 PM.mov
2025-11-24 18:12:58,366 - INFO - ✓ Video file opened: assets/temp_videos/Screen Recording 2025-11-24 at 6.07.31 PM.mov
2025-11-24 18:12:58,370 - INFO - Frame 416 | PERCLOS: 0.00 | Yaw: 15.9° | Alerts: 1
2025-11-24 18:12:58,540 - INFO - Frame 0 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:12:58,655 - INFO - Frame 418 | PERCLOS: 0.00 | Yaw: 17.4° | Alerts: 1
2025-11-24 18:12:58,708 - INFO - Frame 2 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:12:58,877 - INFO - Frame 420 | PERCLOS: 0.00 | Yaw: 17.5° | Alerts: 1
2025-11-24 18:12:58,882 - INFO - Frame 4 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:12:58,990 - INFO - Frame 6 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:12:58,991 - INFO - Frame 422 | PERCLOS: 0.00 | Yaw: 16.9° | Alerts: 1
2025-11-24 18:12:59,160 - INFO - Frame 8 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:12:59,184 - INFO - Frame 424 | PERCLOS: 0.00 | Yaw: 17.0° | Alerts: 1
2025-11-24 18:12:59,304 - INFO - Frame 10 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:12:59,413 - INFO - Frame 426 | PERCLOS: 0.00 | Yaw: 16.4° | Alerts: 1
2025-11-24 18:12:59,416 - INFO - Frame 12 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:12:59,593 - INFO - Frame 14 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:12:59,616 - INFO - Frame 428 | PERCLOS: 0.00 | Yaw: 13.9° | Alerts: 1
2025-11-24 18:12:59,744 - INFO - Frame 16 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:12:59,795 - INFO - Frame 430 | PERCLOS: 0.00 | Yaw: 13.2° | Alerts: 1
2025-11-24 18:12:59,851 - INFO - Frame 18 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:00,019 - INFO - Frame 432 | PERCLOS: 0.00 | Yaw: 12.8° | Alerts: 1
2025-11-24 18:13:00,043 - INFO - Frame 20 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:00,186 - INFO - Frame 434 | PERCLOS: 0.00 | Yaw: 12.8° | Alerts: 1
2025-11-24 18:13:00,188 - INFO - Frame 22 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:00,293 - INFO - Frame 24 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:00,300 - INFO - Frame 436 | PERCLOS: 0.00 | Yaw: 11.5° | Alerts: 1
2025-11-24 18:13:00,456 - INFO - Frame 26 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:00,527 - INFO - Frame 438 | PERCLOS: 0.00 | Yaw: 10.5° | Alerts: 1
2025-11-24 18:13:00,613 - INFO - Frame 28 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:00,677 - INFO - Frame 440 | PERCLOS: 0.00 | Yaw: 10.2° | Alerts: 1
2025-11-24 18:13:00,728 - INFO - Frame 30 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:00,866 - INFO - Frame 442 | PERCLOS: 0.00 | Yaw: 10.3° | Alerts: 1
2025-11-24 18:13:00,891 - INFO - Frame 32 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:01,044 - INFO - Frame 34 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:01,114 - INFO - Frame 444 | PERCLOS: 0.00 | Yaw: 9.9° | Alerts: 1
2025-11-24 18:13:01,146 - INFO - Frame 36 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:01,294 - INFO - Frame 38 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:01,297 - INFO - Frame 446 | PERCLOS: 0.00 | Yaw: 10.4° | Alerts: 1
2025-11-24 18:13:01,409 - INFO - Frame 40 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:01,410 - INFO - Frame 448 | PERCLOS: 0.00 | Yaw: 10.1° | Alerts: 1
2025-11-24 18:13:01,558 - INFO - Frame 42 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:01,630 - INFO - Frame 450 | PERCLOS: 0.00 | Yaw: 9.2° | Alerts: 1
2025-11-24 18:13:01,718 - INFO - Frame 44 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:01,804 - INFO - Frame 452 | PERCLOS: 0.00 | Yaw: 9.8° | Alerts: 1
2025-11-24 18:13:01,825 - INFO - Frame 46 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:01,979 - INFO - Frame 48 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:01,983 - INFO - Frame 454 | PERCLOS: 0.00 | Yaw: 9.5° | Alerts: 1
2025-11-24 18:13:02,080 - INFO - Frame 50 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:02,214 - INFO - Frame 456 | PERCLOS: 0.00 | Yaw: 10.1° | Alerts: 1
2025-11-24 18:13:02,265 - INFO - Frame 52 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:02,415 - INFO - Frame 458 | PERCLOS: 0.00 | Yaw: 10.5° | Alerts: 1
2025-11-24 18:13:02,444 - INFO - Frame 54 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:02,596 - INFO - Frame 460 | PERCLOS: 0.00 | Yaw: 10.8° | Alerts: 1
2025-11-24 18:13:02,599 - INFO - Frame 56 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:02,702 - INFO - Frame 58 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:02,844 - INFO - Frame 462 | PERCLOS: 0.00 | Yaw: 11.0° | Alerts: 1
2025-11-24 18:13:02,861 - INFO - Frame 60 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:03,015 - INFO - Frame 62 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:03,017 - INFO - Frame 464 | PERCLOS: 0.00 | Yaw: 10.9° | Alerts: 1
2025-11-24 18:13:03,121 - INFO - Frame 64 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:03,145 - INFO - Frame 466 | PERCLOS: 0.00 | Yaw: 10.9° | Alerts: 1
2025-11-24 18:13:03,294 - INFO - Frame 66 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:03,374 - INFO - Frame 468 | PERCLOS: 0.00 | Yaw: 10.5° | Alerts: 1
2025-11-24 18:13:03,454 - INFO - Frame 68 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:03,541 - INFO - Frame 470 | PERCLOS: 0.00 | Yaw: 10.7° | Alerts: 1
2025-11-24 18:13:03,560 - INFO - Frame 70 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:03,712 - INFO - Frame 72 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:03,714 - INFO - Frame 472 | PERCLOS: 0.00 | Yaw: 9.9° | Alerts: 1
2025-11-24 18:13:03,805 - INFO - Frame 474 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:03,807 - INFO - Frame 74 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:03,966 - INFO - Frame 76 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:03,989 - INFO - Frame 476 | PERCLOS: 0.00 | Yaw: 9.6° | Alerts: 0
2025-11-24 18:13:04,117 - INFO - Frame 78 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:04,170 - INFO - Frame 478 | PERCLOS: 0.00 | Yaw: 10.3° | Alerts: 0
2025-11-24 18:13:04,229 - INFO - Frame 80 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:04,380 - INFO - Frame 480 | PERCLOS: 0.00 | Yaw: 10.4° | Alerts: 1
2025-11-24 18:13:04,399 - INFO - Frame 82 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:04,548 - INFO - Frame 84 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:04,548 - INFO - Frame 482 | PERCLOS: 0.00 | Yaw: 10.5° | Alerts: 1
2025-11-24 18:13:04,645 - INFO - Frame 86 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:04,669 - INFO - Frame 484 | PERCLOS: 0.00 | Yaw: 10.6° | Alerts: 1
2025-11-24 18:13:04,805 - INFO - Frame 88 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:04,897 - INFO - Frame 486 | PERCLOS: 0.00 | Yaw: 10.8° | Alerts: 1
2025-11-24 18:13:04,900 - INFO - Frame 90 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:05,038 - INFO - Frame 488 | PERCLOS: 0.00 | Yaw: 10.5° | Alerts: 1
2025-11-24 18:13:05,063 - INFO - Frame 92 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:05,227 - INFO - Frame 94 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:05,228 - INFO - Frame 490 | PERCLOS: 0.00 | Yaw: 11.2° | Alerts: 1
2025-11-24 18:13:05,383 - INFO - Frame 96 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:05,450 - INFO - Frame 492 | PERCLOS: 0.00 | Yaw: 11.7° | Alerts: 1
2025-11-24 18:13:05,483 - INFO - Frame 98 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:05,626 - INFO - Frame 100 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:05,634 - INFO - Frame 494 | PERCLOS: 0.00 | Yaw: 11.7° | Alerts: 1
2025-11-24 18:13:05,730 - INFO - Frame 102 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:05,756 - INFO - Frame 496 | PERCLOS: 0.00 | Yaw: 11.3° | Alerts: 1
2025-11-24 18:13:05,893 - INFO - Frame 104 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:05,946 - INFO - Frame 498 | PERCLOS: 0.00 | Yaw: 11.8° | Alerts: 1
2025-11-24 18:13:06,034 - INFO - Frame 106 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:06,121 - INFO - Frame 500 | PERCLOS: 0.00 | Yaw: 11.5° | Alerts: 1
2025-11-24 18:13:06,146 - INFO - Frame 108 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:06,291 - INFO - Frame 502 | PERCLOS: 0.00 | Yaw: 11.7° | Alerts: 1
2025-11-24 18:13:06,316 - INFO - Frame 110 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:06,472 - INFO - Frame 112 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:06,517 - INFO - Frame 504 | PERCLOS: 0.00 | Yaw: 11.5° | Alerts: 1
2025-11-24 18:13:06,575 - INFO - Frame 114 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:06,679 - INFO - Frame 506 | PERCLOS: 0.00 | Yaw: 11.3° | Alerts: 1
2025-11-24 18:13:06,722 - INFO - Frame 116 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:06,794 - INFO - Frame 508 | PERCLOS: 0.00 | Yaw: 11.4° | Alerts: 1
2025-11-24 18:13:06,868 - INFO - Frame 118 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:06,983 - INFO - Frame 120 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:07,004 - INFO - Frame 510 | PERCLOS: 0.00 | Yaw: 11.4° | Alerts: 1
2025-11-24 18:13:07,146 - INFO - Frame 122 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:07,168 - INFO - Frame 512 | PERCLOS: 0.00 | Yaw: 11.8° | Alerts: 1
2025-11-24 18:13:07,233 - INFO - Frame 124 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:07,337 - INFO - Frame 514 | PERCLOS: 0.00 | Yaw: 12.0° | Alerts: 1
2025-11-24 18:13:07,393 - INFO - Frame 126 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:07,546 - INFO - Frame 516 | PERCLOS: 0.00 | Yaw: 11.1° | Alerts: 1
2025-11-24 18:13:07,550 - INFO - Frame 128 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:07,652 - INFO - Frame 130 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:07,662 - INFO - Frame 518 | PERCLOS: 0.00 | Yaw: 11.3° | Alerts: 1
2025-11-24 18:13:07,808 - INFO - Frame 520 | PERCLOS: 0.00 | Yaw: 10.9° | Alerts: 1
2025-11-24 18:13:07,837 - INFO - Frame 132 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:07,933 - INFO - Frame 134 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:08,022 - INFO - Frame 522 | PERCLOS: 0.00 | Yaw: 10.9° | Alerts: 1
2025-11-24 18:13:08,093 - INFO - Frame 136 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:08,142 - INFO - Frame 524 | PERCLOS: 0.00 | Yaw: 10.9° | Alerts: 1
2025-11-24 18:13:08,194 - INFO - Frame 138 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:08,323 - INFO - Frame 526 | PERCLOS: 0.00 | Yaw: 10.5° | Alerts: 1
2025-11-24 18:13:08,364 - INFO - Frame 140 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:08,552 - INFO - Frame 142 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:08,553 - INFO - Frame 528 | PERCLOS: 0.00 | Yaw: 10.1° | Alerts: 1
2025-11-24 18:13:08,727 - INFO - Frame 144 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:08,727 - INFO - Frame 530 | PERCLOS: 0.00 | Yaw: 10.0° | Alerts: 1
2025-11-24 18:13:08,836 - INFO - Frame 146 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:08,861 - INFO - Frame 532 | PERCLOS: 0.00 | Yaw: 10.3° | Alerts: 1
2025-11-24 18:13:09,011 - INFO - Frame 148 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:09,090 - INFO - Frame 534 | PERCLOS: 0.00 | Yaw: 10.2° | Alerts: 1
2025-11-24 18:13:09,109 - INFO - Frame 150 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:09,269 - INFO - Frame 152 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:09,278 - INFO - Frame 536 | PERCLOS: 0.00 | Yaw: 10.5° | Alerts: 1
2025-11-24 18:13:09,413 - INFO - Frame 154 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:09,457 - INFO - Frame 538 | PERCLOS: 0.00 | Yaw: 10.2° | Alerts: 1
2025-11-24 18:13:09,514 - INFO - Frame 156 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:09,695 - INFO - Frame 158 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:09,695 - INFO - Frame 540 | PERCLOS: 0.00 | Yaw: 10.5° | Alerts: 1
2025-11-24 18:13:09,785 - INFO - Frame 542 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:09,787 - INFO - Frame 160 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:09,943 - INFO - Frame 162 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:09,965 - INFO - Frame 544 | PERCLOS: 0.00 | Yaw: 10.3° | Alerts: 0
2025-11-24 18:13:10,033 - INFO - Frame 164 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:10,200 - INFO - Frame 166 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:10,201 - INFO - Frame 546 | PERCLOS: 0.00 | Yaw: 10.2° | Alerts: 1
2025-11-24 18:13:10,347 - INFO - Frame 168 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:10,389 - INFO - Frame 548 | PERCLOS: 0.00 | Yaw: 11.1° | Alerts: 1
2025-11-24 18:13:10,447 - INFO - Frame 170 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:10,572 - INFO - Frame 550 | PERCLOS: 0.00 | Yaw: 11.2° | Alerts: 1
2025-11-24 18:13:10,590 - INFO - Frame 172 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:10,683 - INFO - Frame 174 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:10,817 - INFO - Frame 552 | PERCLOS: 0.00 | Yaw: 11.1° | Alerts: 1
2025-11-24 18:13:10,819 - INFO - Frame 176 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:10,931 - INFO - Frame 554 | PERCLOS: 0.00 | Yaw: 10.9° | Alerts: 1
2025-11-24 18:13:10,938 - INFO - Frame 178 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:11,081 - INFO - Frame 180 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:11,107 - INFO - Frame 556 | PERCLOS: 0.00 | Yaw: 11.5° | Alerts: 1
2025-11-24 18:13:11,171 - INFO - Frame 182 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:11,311 - INFO - Frame 184 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:11,339 - INFO - Frame 558 | PERCLOS: 0.00 | Yaw: 11.7° | Alerts: 1
2025-11-24 18:13:11,406 - INFO - Frame 186 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:11,539 - INFO - Frame 560 | PERCLOS: 0.00 | Yaw: 9.6° | Alerts: 1
2025-11-24 18:13:11,558 - INFO - Frame 188 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:11,722 - INFO - Frame 190 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:11,729 - INFO - Frame 562 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 1
2025-11-24 18:13:11,830 - INFO - Frame 192 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:11,986 - INFO - Frame 194 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:11,990 - INFO - Frame 564 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-24 18:13:12,089 - INFO - Frame 196 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:12,111 - INFO - Frame 566 | PERCLOS: 0.00 | Yaw: 4.1° | Alerts: 1
2025-11-24 18:13:12,276 - INFO - Frame 198 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:12,281 - INFO - Frame 568 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 18:13:12,489 - INFO - Frame 200 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 0
2025-11-24 18:13:12,534 - INFO - Frame 570 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:13:12,582 - INFO - Frame 202 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:12,721 - INFO - Frame 572 | PERCLOS: 0.40 | Yaw: 7.3° | Alerts: 2
2025-11-24 18:13:12,747 - INFO - Frame 204 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:12,946 - INFO - Frame 574 | PERCLOS: 0.00 | Yaw: 8.7° | Alerts: 1
2025-11-24 18:13:12,946 - INFO - Frame 206 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:13,053 - INFO - Frame 208 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:13,200 - INFO - Frame 576 | PERCLOS: 0.00 | Yaw: 11.6° | Alerts: 1
2025-11-24 18:13:13,221 - INFO - Frame 210 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:13,381 - INFO - Frame 212 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:13,382 - INFO - Frame 578 | PERCLOS: 0.00 | Yaw: 11.8° | Alerts: 1
2025-11-24 18:13:13,483 - INFO - Frame 214 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:13,512 - INFO - Frame 580 | PERCLOS: 0.00 | Yaw: 12.1° | Alerts: 1
2025-11-24 18:13:13,630 - INFO - Frame 216 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:13,736 - INFO - Frame 582 | PERCLOS: 0.00 | Yaw: 10.6° | Alerts: 1
2025-11-24 18:13:13,737 - INFO - Frame 218 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:13,885 - INFO - Frame 220 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:13,906 - INFO - Frame 584 | PERCLOS: 0.00 | Yaw: 9.9° | Alerts: 1
2025-11-24 18:13:13,981 - INFO - Frame 222 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:14,092 - INFO - Frame 586 | PERCLOS: 0.00 | Yaw: 10.0° | Alerts: 1
2025-11-24 18:13:14,150 - INFO - Frame 224 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:14,313 - INFO - Frame 588 | PERCLOS: 0.00 | Yaw: 9.4° | Alerts: 1
2025-11-24 18:13:14,323 - INFO - Frame 226 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:14,429 - INFO - Frame 228 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:14,454 - INFO - Frame 590 | PERCLOS: 0.00 | Yaw: 9.4° | Alerts: 1
2025-11-24 18:13:14,586 - INFO - Frame 592 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:14,589 - INFO - Frame 230 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:14,728 - INFO - Frame 232 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:14,825 - INFO - Frame 594 | PERCLOS: 0.00 | Yaw: 9.4° | Alerts: 1
2025-11-24 18:13:14,850 - INFO - Frame 234 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:15,008 - INFO - Frame 236 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:15,010 - INFO - Frame 596 | PERCLOS: 0.00 | Yaw: 9.3° | Alerts: 1
2025-11-24 18:13:15,111 - INFO - Frame 238 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:15,200 - INFO - Frame 598 | PERCLOS: 0.00 | Yaw: 9.5° | Alerts: 1
2025-11-24 18:13:15,273 - INFO - Frame 240 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:15,433 - INFO - Frame 242 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:15,479 - INFO - Frame 600 | PERCLOS: 0.00 | Yaw: 9.0° | Alerts: 1
2025-11-24 18:13:15,534 - INFO - Frame 244 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:15,655 - INFO - Frame 602 | PERCLOS: 0.00 | Yaw: 9.5° | Alerts: 1
2025-11-24 18:13:15,730 - INFO - Frame 246 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:15,782 - INFO - Frame 604 | PERCLOS: 0.00 | Yaw: 10.6° | Alerts: 1
2025-11-24 18:13:15,892 - INFO - Frame 248 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:15,999 - INFO - Frame 250 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:16,025 - INFO - Frame 606 | PERCLOS: 0.00 | Yaw: 11.1° | Alerts: 1
2025-11-24 18:13:16,134 - INFO - Frame 252 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:16,205 - INFO - Frame 608 | PERCLOS: 0.00 | Yaw: 11.2° | Alerts: 1
2025-11-24 18:13:16,233 - INFO - Frame 254 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:16,354 - INFO - Frame 610 | PERCLOS: 0.00 | Yaw: 11.3° | Alerts: 1
2025-11-24 18:13:16,399 - INFO - Frame 256 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:16,499 - INFO - Frame 258 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:16,519 - INFO - Frame 612 | PERCLOS: 0.00 | Yaw: 11.0° | Alerts: 1
2025-11-24 18:13:16,665 - INFO - Frame 260 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:16,691 - INFO - Frame 614 | PERCLOS: 0.00 | Yaw: 10.1° | Alerts: 1
2025-11-24 18:13:16,757 - INFO - Frame 262 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:16,840 - INFO - Frame 616 | PERCLOS: 0.00 | Yaw: 10.4° | Alerts: 1
2025-11-24 18:13:16,911 - INFO - Frame 264 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:17,002 - INFO - Frame 618 | PERCLOS: 0.00 | Yaw: 9.6° | Alerts: 1
2025-11-24 18:13:17,005 - INFO - Frame 266 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:17,163 - INFO - Frame 268 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:17,167 - INFO - Frame 620 | PERCLOS: 0.00 | Yaw: 10.3° | Alerts: 1
2025-11-24 18:13:17,253 - INFO - Frame 622 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:17,313 - INFO - Frame 270 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:17,421 - INFO - Frame 272 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:17,447 - INFO - Frame 624 | PERCLOS: 0.00 | Yaw: 9.8° | Alerts: 1
2025-11-24 18:13:17,580 - INFO - Frame 274 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:17,623 - INFO - Frame 626 | PERCLOS: 0.00 | Yaw: 10.6° | Alerts: 1
2025-11-24 18:13:17,676 - INFO - Frame 276 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:17,818 - INFO - Frame 628 | PERCLOS: 0.00 | Yaw: 11.0° | Alerts: 1
2025-11-24 18:13:17,841 - INFO - Frame 278 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:17,941 - INFO - Frame 280 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:18,037 - INFO - Frame 630 | PERCLOS: 0.00 | Yaw: 12.3° | Alerts: 1
2025-11-24 18:13:18,094 - INFO - Frame 282 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:18,152 - INFO - Frame 632 | PERCLOS: 0.00 | Yaw: 12.9° | Alerts: 1
2025-11-24 18:13:18,259 - INFO - Frame 284 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:18,345 - INFO - Frame 634 | PERCLOS: 0.00 | Yaw: 13.2° | Alerts: 1
2025-11-24 18:13:18,371 - INFO - Frame 286 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:18,529 - INFO - Frame 288 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:18,603 - INFO - Frame 636 | PERCLOS: 0.00 | Yaw: 13.4° | Alerts: 1
2025-11-24 18:13:18,627 - INFO - Frame 290 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:18,786 - INFO - Frame 292 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:18,794 - INFO - Frame 638 | PERCLOS: 0.00 | Yaw: 13.2° | Alerts: 1
2025-11-24 18:13:18,884 - INFO - Frame 640 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:18,886 - INFO - Frame 294 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:19,032 - INFO - Frame 296 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:19,106 - INFO - Frame 642 | PERCLOS: 0.00 | Yaw: 12.9° | Alerts: 1
2025-11-24 18:13:19,127 - INFO - Frame 298 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:19,277 - INFO - Frame 300 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:19,286 - INFO - Frame 644 | PERCLOS: 0.00 | Yaw: 13.3° | Alerts: 1
2025-11-24 18:13:19,499 - INFO - Frame 646 | PERCLOS: 0.00 | Yaw: 13.1° | Alerts: 1
2025-11-24 18:13:19,505 - INFO - Frame 302 | PERCLOS: 0.00 | Yaw: 13.1° | Alerts: 0
2025-11-24 18:13:19,601 - INFO - Frame 304 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:19,749 - INFO - Frame 306 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:19,751 - INFO - Frame 648 | PERCLOS: 0.00 | Yaw: 14.1° | Alerts: 1
2025-11-24 18:13:19,893 - INFO - Frame 650 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:19,903 - INFO - Frame 308 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:20,004 - INFO - Frame 652 | PERCLOS: 0.00 | Yaw: 13.9° | Alerts: 0
2025-11-24 18:13:20,011 - INFO - Frame 310 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:20,205 - INFO - Frame 312 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:20,261 - INFO - Frame 654 | PERCLOS: 0.00 | Yaw: 13.0° | Alerts: 1
2025-11-24 18:13:20,306 - INFO - Frame 314 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:20,480 - INFO - Frame 656 | PERCLOS: 0.00 | Yaw: 12.2° | Alerts: 1
2025-11-24 18:13:20,489 - INFO - Frame 316 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:20,610 - INFO - Frame 318 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:20,706 - INFO - Frame 658 | PERCLOS: 0.00 | Yaw: 12.0° | Alerts: 1
2025-11-24 18:13:20,807 - INFO - Frame 320 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:20,924 - INFO - Frame 660 | PERCLOS: 0.00 | Yaw: 10.1° | Alerts: 1
2025-11-24 18:13:20,991 - INFO - Frame 322 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:21,045 - INFO - Frame 662 | PERCLOS: 0.00 | Yaw: 9.8° | Alerts: 1
2025-11-24 18:13:21,095 - INFO - Frame 324 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:21,220 - INFO - Frame 664 | PERCLOS: 0.00 | Yaw: 9.5° | Alerts: 1
2025-11-24 18:13:21,243 - INFO - Frame 326 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:21,341 - INFO - Frame 328 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:21,440 - INFO - Frame 666 | PERCLOS: 0.00 | Yaw: 9.1° | Alerts: 1
2025-11-24 18:13:21,495 - INFO - Frame 330 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:21,549 - INFO - Frame 668 | PERCLOS: 0.00 | Yaw: 6.6° | Alerts: 1
2025-11-24 18:13:21,594 - INFO - Frame 332 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:21,716 - INFO - Frame 670 | PERCLOS: 0.00 | Yaw: 5.8° | Alerts: 1
2025-11-24 18:13:21,746 - INFO - Frame 334 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:21,905 - INFO - Frame 336 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:21,978 - INFO - Frame 672 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-24 18:13:22,013 - INFO - Frame 338 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:22,137 - INFO - Frame 674 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 18:13:22,183 - INFO - Frame 340 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:22,277 - INFO - Frame 676 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:13:22,284 - INFO - Frame 342 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:22,462 - INFO - Frame 344 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:22,540 - INFO - Frame 678 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 1
2025-11-24 18:13:22,562 - INFO - Frame 346 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:22,717 - INFO - Frame 348 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:22,739 - INFO - Frame 680 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 1
2025-11-24 18:13:22,871 - INFO - Frame 350 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:22,925 - INFO - Frame 682 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 1
2025-11-24 18:13:22,979 - INFO - Frame 352 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:23,155 - INFO - Frame 354 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:23,179 - INFO - Frame 684 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 1
2025-11-24 18:13:23,246 - INFO - Frame 356 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:23,350 - INFO - Frame 686 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 1
2025-11-24 18:13:23,415 - INFO - Frame 358 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:23,471 - INFO - Frame 688 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 1
2025-11-24 18:13:23,514 - INFO - Frame 360 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:23,669 - INFO - Frame 362 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:23,691 - INFO - Frame 690 | PERCLOS: 0.00 | Yaw: -0.3° | Alerts: 1
2025-11-24 18:13:23,758 - INFO - Frame 364 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:23,861 - INFO - Frame 692 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 1
2025-11-24 18:13:23,923 - INFO - Frame 366 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:23,975 - INFO - Frame 694 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 1
2025-11-24 18:13:24,021 - INFO - Frame 368 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:24,179 - INFO - Frame 370 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:24,203 - INFO - Frame 696 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 18:13:24,336 - INFO - Frame 372 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:24,393 - INFO - Frame 698 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 1
2025-11-24 18:13:24,449 - INFO - Frame 374 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:24,579 - INFO - Frame 700 | PERCLOS: 0.00 | Yaw: 7.9° | Alerts: 1
2025-11-24 18:13:24,630 - INFO - Frame 376 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:24,729 - INFO - Frame 378 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:24,752 - INFO - Frame 702 | PERCLOS: 0.00 | Yaw: 8.1° | Alerts: 1
2025-11-24 18:13:24,896 - INFO - Frame 380 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:24,922 - INFO - Frame 704 | PERCLOS: 0.00 | Yaw: 7.7° | Alerts: 1
2025-11-24 18:13:24,992 - INFO - Frame 382 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:25,074 - INFO - Frame 706 | PERCLOS: 0.00 | Yaw: 9.4° | Alerts: 1
2025-11-24 18:13:25,145 - INFO - Frame 384 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:25,240 - INFO - Frame 386 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:25,241 - INFO - Frame 708 | PERCLOS: 0.00 | Yaw: 9.6° | Alerts: 1
2025-11-24 18:13:25,396 - INFO - Frame 388 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:25,415 - INFO - Frame 710 | PERCLOS: 0.00 | Yaw: 9.1° | Alerts: 1
2025-11-24 18:13:25,541 - INFO - Frame 390 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:25,594 - INFO - Frame 712 | PERCLOS: 0.00 | Yaw: 10.0° | Alerts: 1
2025-11-24 18:13:25,649 - INFO - Frame 392 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:25,815 - INFO - Frame 394 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:25,835 - INFO - Frame 714 | PERCLOS: 0.00 | Yaw: 11.8° | Alerts: 1
2025-11-24 18:13:25,990 - INFO - Frame 716 | PERCLOS: 0.00 | Yaw: 15.7° | Alerts: 1
2025-11-24 18:13:26,068 - INFO - Frame 718 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:26,107 - INFO - Frame 396 | PERCLOS: 0.00 | Yaw: 15.7° | Alerts: 1
2025-11-24 18:13:26,207 - INFO - Frame 720 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:26,275 - INFO - Frame 398 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:26,328 - INFO - Frame 722 | PERCLOS: 0.00 | Yaw: 18.4° | Alerts: 0
2025-11-24 18:13:26,431 - INFO - Frame 400 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:26,512 - INFO - Frame 724 | PERCLOS: 0.00 | Yaw: 10.5° | Alerts: 0
2025-11-24 18:13:26,540 - INFO - Frame 402 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:26,701 - INFO - Frame 404 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:26,770 - INFO - Frame 726 | PERCLOS: 0.00 | Yaw: 5.8° | Alerts: 1
2025-11-24 18:13:26,799 - INFO - Frame 406 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:26,923 - INFO - Frame 728 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 1
2025-11-24 18:13:26,946 - INFO - Frame 408 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:27,041 - INFO - Frame 730 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 1
2025-11-24 18:13:27,044 - INFO - Frame 410 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:27,186 - INFO - Frame 412 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:27,271 - INFO - Frame 732 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 1
2025-11-24 18:13:27,280 - INFO - Frame 414 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:27,433 - INFO - Frame 734 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 1
2025-11-24 18:13:27,455 - INFO - Frame 416 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:27,551 - INFO - Frame 736 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 1
2025-11-24 18:13:27,630 - INFO - Frame 418 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:27,738 - INFO - Frame 420 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:27,764 - INFO - End of video file reached
2025-11-24 18:13:27,766 - INFO - Video capture loop ended
2025-11-24 18:13:27,775 - INFO - Frame 738 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 1
2025-11-24 18:13:27,859 - INFO - Video thread started with source: assets/temp_videos/Screen Recording 2025-11-24 at 6.07.31 PM.mov
2025-11-24 18:13:27,888 - INFO - ✓ Video file opened: assets/temp_videos/Screen Recording 2025-11-24 at 6.07.31 PM.mov
2025-11-24 18:13:27,973 - INFO - Frame 740 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 1
2025-11-24 18:13:28,030 - INFO - Frame 0 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:28,176 - INFO - Frame 742 | PERCLOS: 0.34 | Yaw: 1.2° | Alerts: 2
2025-11-24 18:13:28,196 - INFO - Frame 2 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:28,360 - INFO - Frame 4 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:28,422 - INFO - Frame 744 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 18:13:28,466 - INFO - Frame 6 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:28,579 - INFO - Frame 746 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 18:13:28,632 - INFO - Frame 8 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:28,698 - INFO - Frame 748 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-24 18:13:28,794 - INFO - Frame 10 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:28,913 - INFO - Frame 12 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:28,934 - INFO - Frame 750 | PERCLOS: 0.00 | Yaw: 4.1° | Alerts: 1
2025-11-24 18:13:29,084 - INFO - Frame 14 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:29,109 - INFO - Frame 752 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 18:13:29,231 - INFO - Frame 16 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:29,297 - INFO - Frame 754 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 18:13:29,351 - INFO - Frame 18 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:29,526 - INFO - Frame 756 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 18:13:29,527 - INFO - Frame 20 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:29,727 - INFO - Frame 758 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 18:13:29,729 - INFO - Frame 22 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 0
2025-11-24 18:13:29,886 - INFO - Frame 24 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:29,893 - INFO - Frame 760 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 1
2025-11-24 18:13:30,006 - INFO - Frame 26 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:30,098 - INFO - Frame 762 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-24 18:13:30,181 - INFO - Frame 28 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:30,235 - INFO - Frame 764 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 1
2025-11-24 18:13:30,279 - INFO - Frame 30 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:30,408 - INFO - Frame 766 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 1
2025-11-24 18:13:30,434 - INFO - Frame 32 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:30,585 - INFO - Frame 34 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:30,634 - INFO - Frame 768 | PERCLOS: 0.00 | Yaw: 4.1° | Alerts: 1
2025-11-24 18:13:30,689 - INFO - Frame 36 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:30,800 - INFO - Frame 770 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 1
2025-11-24 18:13:30,843 - INFO - Frame 38 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:30,922 - INFO - Frame 772 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 18:13:31,011 - INFO - Frame 40 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:31,115 - INFO - Frame 42 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:31,152 - INFO - Frame 774 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-24 18:13:31,294 - INFO - Frame 44 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:31,316 - INFO - Frame 776 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-24 18:13:31,428 - INFO - Frame 46 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:31,475 - INFO - Frame 778 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-24 18:13:31,533 - INFO - Frame 48 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:31,694 - INFO - Frame 780 | PERCLOS: 0.00 | Yaw: 4.7° | Alerts: 1
2025-11-24 18:13:31,694 - INFO - Frame 50 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:31,829 - INFO - Frame 782 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:31,832 - INFO - Frame 52 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:31,935 - INFO - Frame 54 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:31,941 - INFO - Frame 784 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 0
2025-11-24 18:13:32,096 - INFO - Frame 56 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:32,171 - INFO - Frame 786 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 18:13:32,249 - INFO - Frame 58 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:32,333 - INFO - Frame 788 | PERCLOS: 0.00 | Yaw: 4.1° | Alerts: 1
2025-11-24 18:13:32,356 - INFO - Frame 60 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:32,509 - INFO - Frame 62 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:32,511 - INFO - Frame 790 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 1
2025-11-24 18:13:32,602 - INFO - Frame 64 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:32,737 - INFO - Frame 792 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 1
2025-11-24 18:13:32,769 - INFO - Frame 66 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:32,925 - INFO - Frame 68 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:32,926 - INFO - Frame 794 | PERCLOS: 0.19 | Yaw: 3.4° | Alerts: 1
2025-11-24 18:13:33,076 - INFO - Frame 70 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:33,083 - INFO - Frame 796 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:13:33,184 - INFO - Frame 72 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:33,330 - INFO - Frame 798 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:13:33,348 - INFO - Frame 74 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:33,501 - INFO - Frame 76 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:33,501 - INFO - Frame 800 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 1
2025-11-24 18:13:33,601 - INFO - Frame 78 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:33,626 - INFO - Frame 802 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 1
2025-11-24 18:13:33,750 - INFO - Frame 804 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:33,753 - INFO - Frame 80 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:33,898 - INFO - Frame 82 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:33,942 - INFO - Frame 806 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 0
2025-11-24 18:13:33,999 - INFO - Frame 84 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:34,104 - INFO - Frame 808 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 0
2025-11-24 18:13:34,158 - INFO - Frame 86 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:34,305 - INFO - Frame 88 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:34,348 - INFO - Frame 810 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 18:13:34,403 - INFO - Frame 90 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:34,518 - INFO - Frame 812 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-24 18:13:34,581 - INFO - Frame 92 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:34,633 - INFO - Frame 814 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-24 18:13:34,730 - INFO - Frame 94 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:34,844 - INFO - Frame 96 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:34,865 - INFO - Frame 816 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 1
2025-11-24 18:13:35,011 - INFO - Frame 98 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:35,017 - INFO - Frame 818 | PERCLOS: 0.42 | Yaw: 5.6° | Alerts: 2
2025-11-24 18:13:35,151 - INFO - Frame 820 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:35,156 - INFO - Frame 100 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:35,261 - INFO - Frame 102 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:35,352 - INFO - Frame 822 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 1
2025-11-24 18:13:35,424 - INFO - Frame 104 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:35,476 - INFO - Frame 824 | PERCLOS: 0.00 | Yaw: 6.3° | Alerts: 1
2025-11-24 18:13:35,577 - INFO - Frame 106 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:35,659 - INFO - Frame 826 | PERCLOS: 0.00 | Yaw: 6.6° | Alerts: 1
2025-11-24 18:13:35,688 - INFO - Frame 108 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:35,853 - INFO - Frame 110 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:35,884 - INFO - Frame 828 | PERCLOS: 0.00 | Yaw: 7.1° | Alerts: 1
2025-11-24 18:13:35,994 - INFO - Frame 112 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:36,048 - INFO - Frame 830 | PERCLOS: 0.00 | Yaw: 7.3° | Alerts: 1
2025-11-24 18:13:36,104 - INFO - Frame 114 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:36,210 - INFO - Frame 832 | PERCLOS: 0.00 | Yaw: 7.2° | Alerts: 1
2025-11-24 18:13:36,274 - INFO - Frame 116 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:36,427 - INFO - Frame 834 | PERCLOS: 0.00 | Yaw: 7.0° | Alerts: 1
2025-11-24 18:13:36,428 - INFO - Frame 118 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:36,535 - INFO - Frame 120 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:36,545 - INFO - Frame 836 | PERCLOS: 0.00 | Yaw: 6.9° | Alerts: 1
2025-11-24 18:13:36,686 - INFO - Frame 838 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:36,688 - INFO - Frame 122 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:36,833 - INFO - Frame 124 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:36,935 - INFO - Frame 840 | PERCLOS: 0.00 | Yaw: 6.6° | Alerts: 1
2025-11-24 18:13:36,940 - INFO - Frame 126 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:37,098 - INFO - Frame 128 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:37,099 - INFO - Frame 842 | PERCLOS: 0.32 | Yaw: 6.8° | Alerts: 2
2025-11-24 18:13:37,254 - INFO - Frame 130 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:37,261 - INFO - Frame 844 | PERCLOS: 0.00 | Yaw: 6.4° | Alerts: 1
2025-11-24 18:13:37,360 - INFO - Frame 132 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:37,510 - INFO - Frame 846 | PERCLOS: 0.00 | Yaw: 6.3° | Alerts: 1
2025-11-24 18:13:37,527 - INFO - Frame 134 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:37,719 - INFO - Frame 848 | PERCLOS: 0.00 | Yaw: 6.3° | Alerts: 1
2025-11-24 18:13:37,728 - INFO - Frame 136 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:37,833 - INFO - Frame 850 | PERCLOS: 0.00 | Yaw: 6.4° | Alerts: 1
2025-11-24 18:13:37,839 - INFO - Frame 138 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:37,989 - INFO - Frame 140 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:38,048 - INFO - Frame 852 | PERCLOS: 0.00 | Yaw: 6.7° | Alerts: 1
2025-11-24 18:13:38,127 - INFO - Frame 142 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:38,203 - INFO - Frame 854 | PERCLOS: 0.00 | Yaw: 7.8° | Alerts: 1
2025-11-24 18:13:38,231 - INFO - Frame 144 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:38,369 - INFO - Frame 856 | PERCLOS: 0.00 | Yaw: 7.8° | Alerts: 1
2025-11-24 18:13:38,381 - INFO - Frame 146 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:38,540 - INFO - Frame 148 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:38,604 - INFO - Frame 858 | PERCLOS: 0.00 | Yaw: 7.9° | Alerts: 1
2025-11-24 18:13:38,642 - INFO - Frame 150 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:38,755 - INFO - Frame 860 | PERCLOS: 0.00 | Yaw: 7.9° | Alerts: 1
2025-11-24 18:13:38,800 - INFO - Frame 152 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:38,879 - INFO - Frame 862 | PERCLOS: 0.00 | Yaw: 8.1° | Alerts: 1
2025-11-24 18:13:38,900 - INFO - Frame 154 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:39,065 - INFO - Frame 156 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:39,094 - INFO - Frame 864 | PERCLOS: 0.00 | Yaw: 8.6° | Alerts: 1
2025-11-24 18:13:39,222 - INFO - Frame 866 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:39,224 - INFO - Frame 158 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:39,376 - INFO - Frame 160 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:39,432 - INFO - Frame 868 | PERCLOS: 0.00 | Yaw: 8.3° | Alerts: 0
2025-11-24 18:13:39,491 - INFO - Frame 162 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:39,677 - INFO - Frame 164 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:39,677 - INFO - Frame 870 | PERCLOS: 0.09 | Yaw: 7.3° | Alerts: 1
2025-11-24 18:13:39,823 - INFO - Frame 166 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:39,876 - INFO - Frame 872 | PERCLOS: 0.00 | Yaw: 6.1° | Alerts: 1
2025-11-24 18:13:39,929 - INFO - Frame 168 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:40,039 - INFO - Frame 874 | PERCLOS: 0.00 | Yaw: 4.8° | Alerts: 1
2025-11-24 18:13:40,102 - INFO - Frame 170 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:40,250 - INFO - Frame 172 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:40,280 - INFO - Frame 876 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 18:13:40,348 - INFO - Frame 174 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:40,458 - INFO - Frame 878 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 1
2025-11-24 18:13:40,517 - INFO - Frame 176 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:40,574 - INFO - Frame 880 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 1
2025-11-24 18:13:40,668 - INFO - Frame 178 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:40,773 - INFO - Frame 180 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:40,797 - INFO - Frame 882 | PERCLOS: 0.20 | Yaw: 4.5° | Alerts: 1
2025-11-24 18:13:40,930 - INFO - Frame 884 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:40,932 - INFO - Frame 182 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:41,082 - INFO - Frame 184 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:41,133 - INFO - Frame 886 | PERCLOS: 0.00 | Yaw: 5.1° | Alerts: 0
2025-11-24 18:13:41,188 - INFO - Frame 186 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:41,346 - INFO - Frame 188 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:41,347 - INFO - Frame 888 | PERCLOS: 0.00 | Yaw: 6.1° | Alerts: 1
2025-11-24 18:13:41,504 - INFO - Frame 190 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:41,510 - INFO - Frame 890 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 1
2025-11-24 18:13:41,613 - INFO - Frame 192 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:41,635 - INFO - Frame 892 | PERCLOS: 0.00 | Yaw: 6.2° | Alerts: 1
2025-11-24 18:13:41,767 - INFO - Frame 894 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:41,769 - INFO - Frame 194 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:41,918 - INFO - Frame 196 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:41,966 - INFO - Frame 896 | PERCLOS: 0.00 | Yaw: 5.8° | Alerts: 0
2025-11-24 18:13:42,026 - INFO - Frame 198 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:42,131 - INFO - Frame 898 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 0
2025-11-24 18:13:42,196 - INFO - Frame 200 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:42,352 - INFO - Frame 900 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 1
2025-11-24 18:13:42,356 - INFO - Frame 202 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:42,459 - INFO - Frame 204 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:42,481 - INFO - Frame 902 | PERCLOS: 0.00 | Yaw: 5.8° | Alerts: 1
2025-11-24 18:13:42,628 - INFO - Frame 206 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:42,651 - INFO - Frame 904 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-24 18:13:42,780 - INFO - Frame 208 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:42,886 - INFO - Frame 906 | PERCLOS: 0.00 | Yaw: 5.8° | Alerts: 1
2025-11-24 18:13:42,894 - INFO - Frame 210 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:43,053 - INFO - Frame 908 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-24 18:13:43,060 - INFO - Frame 212 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:43,210 - INFO - Frame 910 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 1
2025-11-24 18:13:43,210 - INFO - Frame 214 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:43,320 - INFO - Frame 216 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:43,433 - INFO - Frame 912 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 1
2025-11-24 18:13:43,489 - INFO - Frame 218 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:43,543 - INFO - Frame 914 | PERCLOS: 0.00 | Yaw: 5.8° | Alerts: 1
2025-11-24 18:13:43,654 - INFO - Frame 220 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:43,725 - INFO - Frame 916 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 1
2025-11-24 18:13:43,773 - INFO - Frame 222 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:43,950 - INFO - Frame 224 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:43,968 - INFO - Frame 918 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 1
2025-11-24 18:13:44,135 - INFO - Frame 920 | PERCLOS: 0.00 | Yaw: 5.9° | Alerts: 1
2025-11-24 18:13:44,143 - INFO - Frame 226 | PERCLOS: 0.00 | Yaw: 5.9° | Alerts: 0
2025-11-24 18:13:44,302 - INFO - Frame 228 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:44,302 - INFO - Frame 922 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-24 18:13:44,406 - INFO - Frame 230 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:44,567 - INFO - Frame 924 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 1
2025-11-24 18:13:44,569 - INFO - Frame 232 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:44,737 - INFO - Frame 234 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:44,737 - INFO - Frame 926 | PERCLOS: 0.00 | Yaw: 6.1° | Alerts: 1
2025-11-24 18:13:44,844 - INFO - Frame 236 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:44,863 - INFO - Frame 928 | PERCLOS: 0.00 | Yaw: 6.1° | Alerts: 1
2025-11-24 18:13:45,014 - INFO - Frame 238 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:45,090 - INFO - Frame 930 | PERCLOS: 0.00 | Yaw: 6.5° | Alerts: 1
2025-11-24 18:13:45,168 - INFO - Frame 240 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:45,251 - INFO - Frame 932 | PERCLOS: 0.00 | Yaw: 6.2° | Alerts: 1
2025-11-24 18:13:45,278 - INFO - Frame 242 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:45,436 - INFO - Frame 934 | PERCLOS: 0.19 | Yaw: 6.2° | Alerts: 1
2025-11-24 18:13:45,440 - INFO - Frame 244 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:45,607 - INFO - Frame 246 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:45,676 - INFO - Frame 936 | PERCLOS: 0.00 | Yaw: 6.2° | Alerts: 1
2025-11-24 18:13:45,713 - INFO - Frame 248 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:45,872 - INFO - Frame 938 | PERCLOS: 0.00 | Yaw: 6.3° | Alerts: 1
2025-11-24 18:13:45,894 - INFO - Frame 250 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:46,058 - INFO - Frame 252 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:46,058 - INFO - Frame 940 | PERCLOS: 0.00 | Yaw: 6.2° | Alerts: 1
2025-11-24 18:13:46,165 - INFO - Frame 254 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:46,334 - INFO - Frame 942 | PERCLOS: 0.00 | Yaw: 6.4° | Alerts: 1
2025-11-24 18:13:46,344 - INFO - Frame 256 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:46,495 - INFO - Frame 944 | PERCLOS: 0.00 | Yaw: 6.7° | Alerts: 1
2025-11-24 18:13:46,500 - INFO - Frame 258 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:46,601 - INFO - Frame 260 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:46,627 - INFO - Frame 946 | PERCLOS: 0.00 | Yaw: 7.2° | Alerts: 1
2025-11-24 18:13:46,772 - INFO - Frame 262 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:46,901 - INFO - Frame 948 | PERCLOS: 0.00 | Yaw: 6.6° | Alerts: 1
2025-11-24 18:13:46,915 - INFO - Frame 264 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:47,022 - INFO - Frame 266 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:47,026 - INFO - Frame 950 | PERCLOS: 0.00 | Yaw: 6.6° | Alerts: 1
2025-11-24 18:13:47,192 - INFO - Frame 268 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:47,213 - INFO - Frame 952 | PERCLOS: 0.00 | Yaw: 6.7° | Alerts: 1
2025-11-24 18:13:47,340 - INFO - Frame 270 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:47,441 - INFO - Frame 954 | PERCLOS: 0.00 | Yaw: 6.6° | Alerts: 1
2025-11-24 18:13:47,448 - INFO - Frame 272 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:47,604 - INFO - Frame 956 | PERCLOS: 0.00 | Yaw: 6.5° | Alerts: 1
2025-11-24 18:13:47,616 - INFO - Frame 274 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:47,780 - INFO - Frame 276 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:47,781 - INFO - Frame 958 | PERCLOS: 0.00 | Yaw: 6.6° | Alerts: 1
2025-11-24 18:13:47,897 - INFO - Frame 278 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:48,006 - INFO - Frame 960 | PERCLOS: 0.00 | Yaw: 6.8° | Alerts: 1
2025-11-24 18:13:48,058 - INFO - Frame 280 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:48,115 - INFO - Frame 962 | PERCLOS: 0.00 | Yaw: 6.9° | Alerts: 1
2025-11-24 18:13:48,209 - INFO - Frame 282 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:48,292 - INFO - Frame 964 | PERCLOS: 0.00 | Yaw: 7.1° | Alerts: 1
2025-11-24 18:13:48,317 - INFO - Frame 284 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:48,495 - INFO - Frame 286 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:48,514 - INFO - Frame 966 | PERCLOS: 0.00 | Yaw: 7.0° | Alerts: 1
2025-11-24 18:13:48,638 - INFO - Frame 288 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:48,692 - INFO - Frame 968 | PERCLOS: 0.00 | Yaw: 6.8° | Alerts: 1
2025-11-24 18:13:48,748 - INFO - Frame 290 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:48,863 - INFO - Frame 970 | PERCLOS: 0.00 | Yaw: 7.1° | Alerts: 1
2025-11-24 18:13:48,934 - INFO - Frame 292 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:49,087 - INFO - Frame 972 | PERCLOS: 0.00 | Yaw: 7.1° | Alerts: 1
2025-11-24 18:13:49,093 - INFO - Frame 294 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:49,197 - INFO - Frame 296 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:49,222 - INFO - Frame 974 | PERCLOS: 0.00 | Yaw: 7.0° | Alerts: 1
2025-11-24 18:13:49,353 - INFO - Frame 976 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:49,355 - INFO - Frame 298 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:49,506 - INFO - Frame 978 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:49,511 - INFO - Frame 300 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:49,617 - INFO - Frame 302 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:49,643 - INFO - Frame 980 | PERCLOS: 0.00 | Yaw: 7.6° | Alerts: 0
2025-11-24 18:13:49,778 - INFO - Frame 982 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:49,781 - INFO - Frame 304 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:49,947 - INFO - Frame 306 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:50,013 - INFO - Frame 984 | PERCLOS: 0.28 | Yaw: 7.6° | Alerts: 1
2025-11-24 18:13:50,050 - INFO - Frame 308 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:50,207 - INFO - Frame 986 | PERCLOS: 0.00 | Yaw: 7.0° | Alerts: 1
2025-11-24 18:13:50,229 - INFO - Frame 310 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:50,379 - INFO - Frame 988 | PERCLOS: 0.00 | Yaw: 6.5° | Alerts: 1
2025-11-24 18:13:50,379 - INFO - Frame 312 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:50,481 - INFO - Frame 314 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:50,626 - INFO - Frame 990 | PERCLOS: 0.00 | Yaw: 5.8° | Alerts: 1
2025-11-24 18:13:50,649 - INFO - Frame 316 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:50,791 - INFO - Frame 992 | PERCLOS: 0.00 | Yaw: 6.1° | Alerts: 1
2025-11-24 18:13:50,794 - INFO - Frame 318 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:50,902 - INFO - Frame 320 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:50,911 - INFO - Frame 994 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 1
2025-11-24 18:13:51,046 - INFO - Frame 322 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:51,143 - INFO - Frame 996 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 1
2025-11-24 18:13:51,150 - INFO - Frame 324 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:51,308 - INFO - Frame 998 | PERCLOS: 0.00 | Yaw: 5.2° | Alerts: 1
2025-11-24 18:13:51,315 - INFO - Frame 326 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:51,451 - INFO - Frame 328 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:51,480 - INFO - Frame 1000 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-24 18:13:51,550 - INFO - Frame 330 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:51,720 - INFO - Frame 332 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:51,722 - INFO - Frame 1002 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-24 18:13:51,860 - INFO - Frame 334 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:51,907 - INFO - Frame 1004 | PERCLOS: 0.00 | Yaw: 5.2° | Alerts: 1
2025-11-24 18:13:51,964 - INFO - Frame 336 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:52,071 - INFO - Frame 1006 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-24 18:13:52,140 - INFO - Frame 338 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:52,302 - INFO - Frame 340 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:52,322 - INFO - Frame 1008 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-24 18:13:52,416 - INFO - Frame 342 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:52,442 - INFO - Frame 1010 | PERCLOS: 0.00 | Yaw: 6.3° | Alerts: 1
2025-11-24 18:13:52,576 - INFO - Frame 344 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:52,601 - INFO - Frame 1012 | PERCLOS: 0.00 | Yaw: 6.5° | Alerts: 1
2025-11-24 18:13:52,721 - INFO - Frame 1014 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:52,726 - INFO - Frame 346 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:52,839 - INFO - Frame 1016 | PERCLOS: 0.00 | Yaw: 7.0° | Alerts: 0
2025-11-24 18:13:52,840 - INFO - Frame 348 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:53,001 - INFO - Frame 350 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:53,006 - INFO - Frame 1018 | PERCLOS: 0.00 | Yaw: 7.5° | Alerts: 0
2025-11-24 18:13:53,179 - INFO - Frame 352 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:53,231 - INFO - Frame 1020 | PERCLOS: 0.00 | Yaw: 7.2° | Alerts: 1
2025-11-24 18:13:53,282 - INFO - Frame 354 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:53,393 - INFO - Frame 1022 | PERCLOS: 0.00 | Yaw: 7.1° | Alerts: 1
2025-11-24 18:13:53,450 - INFO - Frame 356 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:53,555 - INFO - Frame 1024 | PERCLOS: 0.00 | Yaw: 7.2° | Alerts: 1
2025-11-24 18:13:53,616 - INFO - Frame 358 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:53,765 - INFO - Frame 360 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:53,814 - INFO - Frame 1026 | PERCLOS: 0.00 | Yaw: 7.2° | Alerts: 1
2025-11-24 18:13:53,872 - INFO - Frame 362 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:53,978 - INFO - Frame 1028 | PERCLOS: 0.00 | Yaw: 7.0° | Alerts: 1
2025-11-24 18:13:54,023 - INFO - Frame 364 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:54,100 - INFO - Frame 1030 | PERCLOS: 0.00 | Yaw: 7.3° | Alerts: 1
2025-11-24 18:13:54,119 - INFO - Frame 366 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:54,286 - INFO - Frame 368 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:54,320 - INFO - Frame 1032 | PERCLOS: 0.00 | Yaw: 6.8° | Alerts: 1
2025-11-24 18:13:54,444 - INFO - Frame 1034 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:54,446 - INFO - Frame 370 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:54,591 - INFO - Frame 372 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:54,640 - INFO - Frame 1036 | PERCLOS: 0.00 | Yaw: 6.5° | Alerts: 0
2025-11-24 18:13:54,692 - INFO - Frame 374 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:54,850 - INFO - Frame 376 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:54,862 - INFO - Frame 1038 | PERCLOS: 0.00 | Yaw: 6.4° | Alerts: 1
2025-11-24 18:13:55,056 - INFO - Frame 1040 | PERCLOS: 0.00 | Yaw: 6.1° | Alerts: 1
2025-11-24 18:13:55,142 - INFO - Frame 378 | PERCLOS: 0.00 | Yaw: 6.1° | Alerts: 1
2025-11-24 18:13:55,225 - INFO - Frame 1042 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 1
2025-11-24 18:13:55,299 - INFO - Frame 380 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:55,444 - INFO - Frame 382 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:55,480 - INFO - Frame 1044 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 1
2025-11-24 18:13:55,541 - INFO - Frame 384 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:55,649 - INFO - Frame 1046 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 1
2025-11-24 18:13:55,694 - INFO - Frame 386 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:55,771 - INFO - Frame 1048 | PERCLOS: 0.00 | Yaw: 5.2° | Alerts: 1
2025-11-24 18:13:55,794 - INFO - Frame 388 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:55,953 - INFO - Frame 390 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:55,986 - INFO - Frame 1050 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 18:13:56,129 - INFO - Frame 392 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:56,160 - INFO - Frame 1052 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 18:13:56,324 - INFO - Frame 1054 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:56,328 - INFO - Frame 394 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:56,440 - INFO - Frame 396 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:56,576 - INFO - Frame 1056 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:13:56,596 - INFO - Frame 398 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:56,740 - INFO - Frame 1058 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 18:13:56,742 - INFO - Frame 400 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:56,846 - INFO - Frame 402 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:56,869 - INFO - Frame 1060 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 1
2025-11-24 18:13:57,015 - INFO - Frame 404 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:57,087 - INFO - Frame 1062 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 1
2025-11-24 18:13:57,171 - INFO - Frame 406 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:57,252 - INFO - Frame 1064 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 1
2025-11-24 18:13:57,272 - INFO - Frame 408 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:57,420 - INFO - Frame 410 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:57,422 - INFO - Frame 1066 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 1
2025-11-24 18:13:57,634 - INFO - Frame 412 | PERCLOS: 0.47 | Yaw: 2.2° | Alerts: 1
2025-11-24 18:13:57,682 - INFO - Frame 1068 | PERCLOS: 0.47 | Yaw: 2.2° | Alerts: 2
2025-11-24 18:13:57,725 - INFO - Frame 414 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:57,862 - INFO - Video thread started with source: Camera
2025-11-24 18:13:57,863 - ERROR - ❌ No camera found!
2025-11-24 18:13:57,934 - INFO - Frame 1070 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 18:13:57,937 - INFO - Frame 416 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:58,033 - INFO - Frame 418 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:58,114 - INFO - Video thread started with source: Camera
2025-11-24 18:13:58,115 - ERROR - ❌ No camera found!
2025-11-24 18:13:58,116 - INFO - Frame 1072 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 1
2025-11-24 18:13:58,191 - INFO - Frame 420 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:13:58,216 - INFO - End of video file reached
2025-11-24 18:13:58,216 - INFO - Video capture loop ended
2025-11-24 18:13:58,354 - INFO - Frame 1074 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 1
2025-11-24 18:13:58,357 - INFO - Video thread started with source: Camera
2025-11-24 18:13:58,358 - ERROR - ❌ No camera found!
2025-11-24 18:13:58,485 - INFO - Frame 1076 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-24 18:13:58,577 - INFO - Video thread started with source: Camera
2025-11-24 18:13:58,578 - ERROR - ❌ No camera found!
2025-11-24 18:13:58,665 - INFO - Frame 1078 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:13:58,801 - INFO - Video thread started with source: Camera
2025-11-24 18:13:58,802 - ERROR - ❌ No camera found!
2025-11-24 18:13:58,907 - INFO - Video thread started with source: Camera
2025-11-24 18:13:58,908 - ERROR - ❌ No camera found!
2025-11-24 18:13:58,928 - INFO - Frame 1080 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 18:13:59,008 - INFO - Video thread started with source: Camera
2025-11-24 18:13:59,009 - ERROR - ❌ No camera found!
2025-11-24 18:13:59,102 - INFO - Video thread started with source: Camera
2025-11-24 18:13:59,104 - ERROR - ❌ No camera found!
2025-11-24 18:13:59,138 - INFO - Frame 1082 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 18:13:59,197 - INFO - Video thread started with source: Camera
2025-11-24 18:13:59,198 - ERROR - ❌ No camera found!
2025-11-24 18:13:59,291 - INFO - Video thread started with source: Camera
2025-11-24 18:13:59,292 - ERROR - ❌ No camera found!
2025-11-24 18:13:59,322 - INFO - Frame 1084 | PERCLOS: 0.00 | Yaw: 4.9° | Alerts: 1
2025-11-24 18:13:59,384 - INFO - Video thread started with source: Camera
2025-11-24 18:13:59,385 - ERROR - ❌ No camera found!
2025-11-24 18:13:59,473 - INFO - Video thread started with source: Camera
2025-11-24 18:13:59,474 - ERROR - ❌ No camera found!
2025-11-24 18:13:59,569 - INFO - Video thread started with source: Camera
2025-11-24 18:13:59,570 - ERROR - ❌ No camera found!
2025-11-24 18:13:59,590 - INFO - Frame 1086 | PERCLOS: 0.00 | Yaw: 5.4° | Alerts: 1
2025-11-24 18:13:59,665 - INFO - Video thread started with source: Camera
2025-11-24 18:13:59,665 - ERROR - ❌ No camera found!
2025-11-24 18:13:59,754 - INFO - Video thread started with source: Camera
2025-11-24 18:13:59,756 - ERROR - ❌ No camera found!
2025-11-24 18:13:59,788 - INFO - Frame 1088 | PERCLOS: 0.00 | Yaw: 6.4° | Alerts: 1
2025-11-24 18:13:59,854 - INFO - Video thread started with source: Camera
2025-11-24 18:13:59,855 - ERROR - ❌ No camera found!
2025-11-24 18:13:59,944 - INFO - Video thread started with source: Camera
2025-11-24 18:13:59,945 - ERROR - ❌ No camera found!
2025-11-24 18:13:59,973 - INFO - Frame 1090 | PERCLOS: 0.00 | Yaw: 6.2° | Alerts: 1
2025-11-24 18:14:00,041 - INFO - Video thread started with source: Camera
2025-11-24 18:14:00,042 - ERROR - ❌ No camera found!
2025-11-24 18:14:00,142 - INFO - Video thread started with source: Camera
2025-11-24 18:14:00,142 - ERROR - ❌ No camera found!
2025-11-24 18:14:00,242 - INFO - Video thread started with source: Camera
2025-11-24 18:14:00,243 - ERROR - ❌ No camera found!
2025-11-24 18:14:00,264 - INFO - Frame 1092 | PERCLOS: 0.00 | Yaw: 6.2° | Alerts: 1
2025-11-24 18:14:00,347 - INFO - Video thread started with source: Camera
2025-11-24 18:14:00,348 - ERROR - ❌ No camera found!
2025-11-24 18:14:00,450 - INFO - Video thread started with source: Camera
2025-11-24 18:14:00,452 - ERROR - ❌ No camera found!
2025-11-24 18:14:00,482 - INFO - Frame 1094 | PERCLOS: 0.00 | Yaw: 6.3° | Alerts: 1
2025-11-24 18:14:00,546 - INFO - Video thread started with source: Camera
2025-11-24 18:14:00,547 - ERROR - ❌ No camera found!
2025-11-24 18:14:00,643 - INFO - Video thread started with source: Camera
2025-11-24 18:14:00,644 - ERROR - ❌ No camera found!
2025-11-24 18:14:00,673 - INFO - Frame 1096 | PERCLOS: 0.00 | Yaw: 6.1° | Alerts: 1
2025-11-24 18:14:00,741 - INFO - Video thread started with source: Camera
2025-11-24 18:14:00,742 - ERROR - ❌ No camera found!
2025-11-24 18:14:00,837 - INFO - Video thread started with source: Camera
2025-11-24 18:14:00,838 - ERROR - ❌ No camera found!
2025-11-24 18:14:00,942 - INFO - Video thread started with source: Camera
2025-11-24 18:14:00,943 - ERROR - ❌ No camera found!
2025-11-24 18:14:00,964 - INFO - Frame 1098 | PERCLOS: 0.00 | Yaw: 6.6° | Alerts: 1
2025-11-24 18:14:01,043 - INFO - Video thread started with source: Camera
2025-11-24 18:14:01,044 - ERROR - ❌ No camera found!
2025-11-24 18:14:01,134 - INFO - Video thread started with source: Camera
2025-11-24 18:14:01,136 - ERROR - ❌ No camera found!
2025-11-24 18:14:01,166 - INFO - Frame 1100 | PERCLOS: 0.00 | Yaw: 6.7° | Alerts: 1
2025-11-24 18:14:01,229 - INFO - Video thread started with source: Camera
2025-11-24 18:14:01,230 - ERROR - ❌ No camera found!
2025-11-24 18:14:01,332 - INFO - Video thread started with source: Camera
2025-11-24 18:14:01,334 - ERROR - ❌ No camera found!
2025-11-24 18:14:01,365 - INFO - Frame 1102 | PERCLOS: 0.00 | Yaw: 6.4° | Alerts: 1
2025-11-24 18:14:01,439 - INFO - Video thread started with source: Camera
2025-11-24 18:14:01,440 - ERROR - ❌ No camera found!
2025-11-24 18:14:01,541 - INFO - Video thread started with source: Camera
2025-11-24 18:14:01,541 - ERROR - ❌ No camera found!
2025-11-24 18:14:01,645 - INFO - Video thread started with source: Camera
2025-11-24 18:14:01,646 - ERROR - ❌ No camera found!
2025-11-24 18:14:01,666 - INFO - Frame 1104 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 1
2025-11-24 18:14:01,748 - INFO - Video thread started with source: Camera
2025-11-24 18:14:01,749 - ERROR - ❌ No camera found!
2025-11-24 18:14:01,845 - INFO - Video thread started with source: Camera
2025-11-24 18:14:01,846 - ERROR - ❌ No camera found!
2025-11-24 18:14:01,876 - INFO - Frame 1106 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 1
2025-11-24 18:14:01,945 - INFO - Video thread started with source: Camera
2025-11-24 18:14:01,946 - ERROR - ❌ No camera found!
2025-11-24 18:14:02,041 - INFO - Video thread started with source: Camera
2025-11-24 18:14:02,042 - ERROR - ❌ No camera found!
2025-11-24 18:14:02,072 - INFO - Frame 1108 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 1
2025-11-24 18:14:02,136 - INFO - Video thread started with source: Camera
2025-11-24 18:14:02,137 - ERROR - ❌ No camera found!
2025-11-24 18:14:02,231 - INFO - Video thread started with source: Camera
2025-11-24 18:14:02,232 - ERROR - ❌ No camera found!
2025-11-24 18:14:02,328 - INFO - Video thread started with source: Camera
2025-11-24 18:14:02,329 - ERROR - ❌ No camera found!
2025-11-24 18:14:02,349 - INFO - Frame 1110 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 1
2025-11-24 18:14:02,433 - INFO - Video thread started with source: Camera
2025-11-24 18:14:02,434 - ERROR - ❌ No camera found!
2025-11-24 18:14:02,530 - INFO - Video thread started with source: Camera
2025-11-24 18:14:02,532 - ERROR - ❌ No camera found!
2025-11-24 18:14:02,564 - INFO - Frame 1112 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 1
2025-11-24 18:14:02,631 - INFO - Video thread started with source: Camera
2025-11-24 18:14:02,631 - ERROR - ❌ No camera found!
2025-11-24 18:14:02,726 - INFO - Video thread started with source: Camera
2025-11-24 18:14:02,727 - ERROR - ❌ No camera found!
2025-11-24 18:14:02,755 - INFO - Frame 1114 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 1
2025-11-24 18:14:02,830 - INFO - Video thread started with source: Camera
2025-11-24 18:14:02,831 - ERROR - ❌ No camera found!
2025-11-24 18:14:02,938 - INFO - Video thread started with source: Camera
2025-11-24 18:14:02,939 - ERROR - ❌ No camera found!
2025-11-24 18:14:03,046 - INFO - Video thread started with source: Camera
2025-11-24 18:14:03,047 - ERROR - ❌ No camera found!
2025-11-24 18:14:03,068 - INFO - Frame 1116 | PERCLOS: 0.00 | Yaw: -0.2° | Alerts: 1
2025-11-24 18:14:03,150 - INFO - Video thread started with source: Camera
2025-11-24 18:14:03,151 - ERROR - ❌ No camera found!
2025-11-24 18:14:03,251 - INFO - Video thread started with source: Camera
2025-11-24 18:14:03,253 - ERROR - ❌ No camera found!
2025-11-24 18:14:03,284 - INFO - Frame 1118 | PERCLOS: 0.00 | Yaw: -0.3° | Alerts: 1
2025-11-24 18:14:03,357 - INFO - Video thread started with source: Camera
2025-11-24 18:14:03,358 - ERROR - ❌ No camera found!
2025-11-24 18:14:03,456 - INFO - Video thread started with source: Camera
2025-11-24 18:14:03,457 - ERROR - ❌ No camera found!
2025-11-24 18:14:03,482 - INFO - Frame 1120 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 1
2025-11-24 18:14:03,557 - INFO - Video thread started with source: Camera
2025-11-24 18:14:03,558 - ERROR - ❌ No camera found!
2025-11-24 18:14:03,653 - INFO - Video thread started with source: Camera
2025-11-24 18:14:03,654 - ERROR - ❌ No camera found!
2025-11-24 18:14:03,758 - INFO - Video thread started with source: Camera
2025-11-24 18:14:03,759 - ERROR - ❌ No camera found!
2025-11-24 18:14:03,778 - INFO - Frame 1122 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 1
2025-11-24 18:14:03,858 - INFO - Video thread started with source: Camera
2025-11-24 18:14:03,858 - ERROR - ❌ No camera found!
2025-11-24 18:14:03,955 - INFO - Video thread started with source: Camera
2025-11-24 18:14:03,956 - ERROR - ❌ No camera found!
2025-11-24 18:14:03,958 - INFO - Frame 1124 | PERCLOS: 0.00 | Yaw: -0.3° | Alerts: 1
2025-11-24 18:14:04,049 - INFO - Video thread started with source: Camera
2025-11-24 18:14:04,050 - ERROR - ❌ No camera found!
2025-11-24 18:14:04,145 - INFO - Video thread started with source: Camera
2025-11-24 18:14:04,146 - ERROR - ❌ No camera found!
2025-11-24 18:14:04,177 - INFO - Frame 1126 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 1
2025-11-24 18:14:04,242 - INFO - Video thread started with source: Camera
2025-11-24 18:14:04,243 - ERROR - ❌ No camera found!
2025-11-24 18:14:04,339 - INFO - Video thread started with source: Camera
2025-11-24 18:14:04,340 - ERROR - ❌ No camera found!
2025-11-24 18:14:04,429 - INFO - Video thread started with source: Camera
2025-11-24 18:14:04,430 - ERROR - ❌ No camera found!
2025-11-24 18:14:04,449 - INFO - Frame 1128 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 1
2025-11-24 18:14:04,528 - INFO - Video thread started with source: Camera
2025-11-24 18:14:04,529 - ERROR - ❌ No camera found!
2025-11-24 18:14:04,625 - INFO - Video thread started with source: Camera
2025-11-24 18:14:04,626 - ERROR - ❌ No camera found!
2025-11-24 18:14:04,655 - INFO - Frame 1130 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 1
2025-11-24 18:14:04,716 - INFO - Video thread started with source: Camera
2025-11-24 18:14:04,717 - ERROR - ❌ No camera found!
2025-11-24 18:14:04,811 - INFO - Video thread started with source: Camera
2025-11-24 18:14:04,812 - ERROR - ❌ No camera found!
2025-11-24 18:14:04,842 - INFO - Frame 1132 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 1
2025-11-24 18:14:04,908 - INFO - Video thread started with source: Camera
2025-11-24 18:14:04,909 - ERROR - ❌ No camera found!
2025-11-24 18:14:05,003 - INFO - Video thread started with source: Camera
2025-11-24 18:14:05,004 - ERROR - ❌ No camera found!
2025-11-24 18:14:05,102 - INFO - Video thread started with source: Camera
2025-11-24 18:14:05,103 - ERROR - ❌ No camera found!
2025-11-24 18:14:05,123 - INFO - Frame 1134 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 1
2025-11-24 18:14:05,200 - INFO - Video thread started with source: Camera
2025-11-24 18:14:05,201 - ERROR - ❌ No camera found!
2025-11-24 18:14:05,302 - INFO - Video thread started with source: Camera
2025-11-24 18:14:05,303 - ERROR - ❌ No camera found!
2025-11-24 18:14:05,334 - INFO - Frame 1136 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 1
2025-11-24 18:14:05,402 - INFO - Video thread started with source: Camera
2025-11-24 18:14:05,403 - ERROR - ❌ No camera found!
2025-11-24 18:14:05,496 - INFO - Video thread started with source: Camera
2025-11-24 18:14:05,497 - ERROR - ❌ No camera found!
2025-11-24 18:14:05,528 - INFO - Frame 1138 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 1
2025-11-24 18:14:05,594 - INFO - Video thread started with source: Camera
2025-11-24 18:14:05,595 - ERROR - ❌ No camera found!
2025-11-24 18:14:05,691 - INFO - Video thread started with source: Camera
2025-11-24 18:14:05,691 - ERROR - ❌ No camera found!
2025-11-24 18:14:05,789 - INFO - Video thread started with source: Camera
2025-11-24 18:14:05,790 - ERROR - ❌ No camera found!
2025-11-24 18:14:05,810 - INFO - Frame 1140 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 1
2025-11-24 18:14:05,884 - INFO - Video thread started with source: Camera
2025-11-24 18:14:05,886 - ERROR - ❌ No camera found!
2025-11-24 18:14:05,975 - INFO - Video thread started with source: Camera
2025-11-24 18:14:05,976 - ERROR - ❌ No camera found!
2025-11-24 18:14:06,005 - INFO - Frame 1142 | PERCLOS: 0.00 | Yaw: 0.2° | Alerts: 1
2025-11-24 18:14:06,064 - INFO - Video thread started with source: Camera
2025-11-24 18:14:06,065 - ERROR - ❌ No camera found!
2025-11-24 18:14:06,162 - INFO - Video thread started with source: Camera
2025-11-24 18:14:06,163 - ERROR - ❌ No camera found!
2025-11-24 18:14:06,194 - INFO - Frame 1144 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 1
2025-11-24 18:14:06,266 - INFO - Video thread started with source: Camera
2025-11-24 18:14:06,267 - ERROR - ❌ No camera found!
2025-11-24 18:14:06,356 - INFO - Video thread started with source: Camera
2025-11-24 18:14:06,357 - ERROR - ❌ No camera found!
2025-11-24 18:14:06,454 - INFO - Video thread started with source: Camera
2025-11-24 18:14:06,455 - ERROR - ❌ No camera found!
2025-11-24 18:14:06,475 - INFO - Frame 1146 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 1
2025-11-24 18:14:06,548 - INFO - Video thread started with source: Camera
2025-11-24 18:14:06,549 - ERROR - ❌ No camera found!
2025-11-24 18:14:06,638 - INFO - Video thread started with source: Camera
2025-11-24 18:14:06,639 - ERROR - ❌ No camera found!
2025-11-24 18:14:06,669 - INFO - Frame 1148 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 1
2025-11-24 18:14:06,733 - INFO - Video thread started with source: Camera
2025-11-24 18:14:06,734 - ERROR - ❌ No camera found!
2025-11-24 18:14:06,822 - INFO - Video thread started with source: Camera
2025-11-24 18:14:06,823 - ERROR - ❌ No camera found!
2025-11-24 18:14:06,857 - INFO - Frame 1150 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 1
2025-11-24 18:14:06,916 - INFO - Video thread started with source: Camera
2025-11-24 18:14:06,917 - ERROR - ❌ No camera found!
2025-11-24 18:14:07,011 - INFO - Video thread started with source: Camera
2025-11-24 18:14:07,012 - ERROR - ❌ No camera found!
2025-11-24 18:14:07,109 - INFO - Video thread started with source: Camera
2025-11-24 18:14:07,110 - ERROR - ❌ No camera found!
2025-11-24 18:14:07,127 - INFO - Frame 1152 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 1
2025-11-24 18:14:07,205 - INFO - Video thread started with source: Camera
2025-11-24 18:14:07,206 - ERROR - ❌ No camera found!
2025-11-24 18:14:07,306 - INFO - Video thread started with source: Camera
2025-11-24 18:14:07,307 - ERROR - ❌ No camera found!
2025-11-24 18:14:07,337 - INFO - Frame 1154 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 1
2025-11-24 18:14:07,406 - INFO - Video thread started with source: Camera
2025-11-24 18:14:07,407 - ERROR - ❌ No camera found!
2025-11-24 18:14:07,503 - INFO - Video thread started with source: Camera
2025-11-24 18:14:07,504 - ERROR - ❌ No camera found!
2025-11-24 18:14:07,536 - INFO - Frame 1156 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 1
2025-11-24 18:14:07,609 - INFO - Video thread started with source: Camera
2025-11-24 18:14:07,611 - ERROR - ❌ No camera found!
2025-11-24 18:14:07,712 - INFO - Video thread started with source: Camera
2025-11-24 18:14:07,713 - ERROR - ❌ No camera found!
2025-11-24 18:14:07,819 - INFO - Video thread started with source: Camera
2025-11-24 18:14:07,820 - ERROR - ❌ No camera found!
2025-11-24 18:14:07,838 - INFO - Frame 1158 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 1
2025-11-24 18:14:07,918 - INFO - Video thread started with source: Camera
2025-11-24 18:14:07,918 - ERROR - ❌ No camera found!
2025-11-24 18:14:08,018 - INFO - Video thread started with source: Camera
2025-11-24 18:14:08,020 - ERROR - ❌ No camera found!
2025-11-24 18:14:08,047 - INFO - Frame 1160 | PERCLOS: 0.14 | Yaw: 1.2° | Alerts: 1
2025-11-24 18:14:08,118 - INFO - Video thread started with source: Camera
2025-11-24 18:14:08,118 - ERROR - ❌ No camera found!
2025-11-24 18:14:08,216 - INFO - Video thread started with source: Camera
2025-11-24 18:14:08,217 - ERROR - ❌ No camera found!
2025-11-24 18:14:08,245 - INFO - Frame 1162 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-24 18:14:08,316 - INFO - Video thread started with source: Camera
2025-11-24 18:14:08,317 - ERROR - ❌ No camera found!
2025-11-24 18:14:08,414 - INFO - Video thread started with source: Camera
2025-11-24 18:14:08,415 - ERROR - ❌ No camera found!
2025-11-24 18:14:08,510 - INFO - Video thread started with source: Camera
2025-11-24 18:14:08,511 - ERROR - ❌ No camera found!
2025-11-24 18:14:08,532 - INFO - Frame 1164 | PERCLOS: 0.00 | Yaw: 5.2° | Alerts: 1
2025-11-24 18:14:08,609 - INFO - Video thread started with source: Camera
2025-11-24 18:14:08,610 - ERROR - ❌ No camera found!
2025-11-24 18:14:08,703 - INFO - Video thread started with source: Camera
2025-11-24 18:14:08,705 - ERROR - ❌ No camera found!
2025-11-24 18:14:08,734 - INFO - Frame 1166 | PERCLOS: 0.00 | Yaw: 5.9° | Alerts: 1
2025-11-24 18:14:08,801 - INFO - Video thread started with source: Camera
2025-11-24 18:14:08,801 - ERROR - ❌ No camera found!
2025-11-24 18:14:08,904 - INFO - Video thread started with source: Camera
2025-11-24 18:14:08,906 - ERROR - ❌ No camera found!
2025-11-24 18:14:08,937 - INFO - Frame 1168 | PERCLOS: 0.00 | Yaw: 5.9° | Alerts: 1
2025-11-24 18:14:09,014 - INFO - Video thread started with source: Camera
2025-11-24 18:14:09,016 - ERROR - ❌ No camera found!
2025-11-24 18:14:09,113 - INFO - Video thread started with source: Camera
2025-11-24 18:14:09,114 - ERROR - ❌ No camera found!
2025-11-24 18:14:09,302 - INFO - Video file uploaded: assets/temp_videos/Screen Recording 2025-11-24 at 6.07.31 PM.mov
2025-11-24 18:14:09,302 - INFO - Video thread started with source: assets/temp_videos/Screen Recording 2025-11-24 at 6.07.31 PM.mov
2025-11-24 18:14:09,303 - INFO - Frame 1170 | PERCLOS: 0.00 | Yaw: 5.9° | Alerts: 1
2025-11-24 18:14:09,328 - INFO - ✓ Video file opened: assets/temp_videos/Screen Recording 2025-11-24 at 6.07.31 PM.mov
2025-11-24 18:14:09,500 - INFO - Frame 0 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:09,516 - INFO - Frame 1172 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 1
2025-11-24 18:14:09,677 - INFO - Frame 2 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:09,678 - INFO - Frame 1174 | PERCLOS: 0.00 | Yaw: 6.5° | Alerts: 1
2025-11-24 18:14:09,844 - INFO - Frame 4 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:09,895 - INFO - Frame 1176 | PERCLOS: 0.00 | Yaw: 6.4° | Alerts: 1
2025-11-24 18:14:09,953 - INFO - Frame 6 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:10,063 - INFO - Frame 1178 | PERCLOS: 0.00 | Yaw: 6.5° | Alerts: 1
2025-11-24 18:14:10,118 - INFO - Frame 8 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:10,181 - INFO - Frame 1180 | PERCLOS: 0.38 | Yaw: 6.9° | Alerts: 2
2025-11-24 18:14:10,273 - INFO - Frame 10 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:10,380 - INFO - Frame 12 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:10,421 - INFO - Frame 1182 | PERCLOS: 0.00 | Yaw: 6.6° | Alerts: 1
2025-11-24 18:14:10,513 - INFO - Frame 14 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:10,583 - INFO - Frame 1184 | PERCLOS: 0.00 | Yaw: 6.4° | Alerts: 1
2025-11-24 18:14:10,619 - INFO - Frame 16 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:10,759 - INFO - Frame 1186 | PERCLOS: 0.00 | Yaw: 6.2° | Alerts: 1
2025-11-24 18:14:10,784 - INFO - Frame 18 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:10,935 - INFO - Frame 20 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:10,985 - INFO - Frame 1188 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 1
2025-11-24 18:14:11,041 - INFO - Frame 22 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:11,143 - INFO - Frame 1190 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 1
2025-11-24 18:14:11,200 - INFO - Frame 24 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:11,262 - INFO - Frame 1192 | PERCLOS: 0.00 | Yaw: 5.8° | Alerts: 1
2025-11-24 18:14:11,346 - INFO - Frame 26 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:11,456 - INFO - Frame 28 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:11,483 - INFO - Frame 1194 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-24 18:14:11,627 - INFO - Frame 30 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:11,653 - INFO - Frame 1196 | PERCLOS: 0.00 | Yaw: 6.1° | Alerts: 1
2025-11-24 18:14:11,717 - INFO - Frame 32 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:11,839 - INFO - Frame 1198 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 1
2025-11-24 18:14:11,893 - INFO - Frame 34 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:12,069 - INFO - Frame 36 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:12,084 - INFO - Frame 1200 | PERCLOS: 0.00 | Yaw: 6.2° | Alerts: 1
2025-11-24 18:14:12,289 - INFO - Frame 38 | PERCLOS: 0.00 | Yaw: 6.4° | Alerts: 0
2025-11-24 18:14:12,290 - INFO - Frame 1202 | PERCLOS: 0.00 | Yaw: 6.4° | Alerts: 1
2025-11-24 18:14:12,395 - INFO - Frame 1204 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:12,398 - INFO - Frame 40 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:12,567 - INFO - Video thread started with source: Camera
2025-11-24 18:14:12,569 - ERROR - ❌ No camera found!
2025-11-24 18:14:12,582 - INFO - Frame 42 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:12,711 - INFO - Frame 1206 | PERCLOS: 0.00 | Yaw: 6.2° | Alerts: 1
2025-11-24 18:14:12,761 - INFO - Frame 44 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:12,879 - INFO - Video thread started with source: Camera
2025-11-24 18:14:12,880 - INFO - Frame 1208 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 1
2025-11-24 18:14:12,881 - ERROR - ❌ No camera found!
2025-11-24 18:14:12,933 - INFO - Frame 46 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:13,012 - INFO - Frame 1210 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:14:13,097 - INFO - Video thread started with source: Camera
2025-11-24 18:14:13,097 - INFO - Frame 48 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:13,098 - ERROR - ❌ No camera found!
2025-11-24 18:14:13,212 - INFO - Frame 50 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:13,235 - INFO - Frame 1212 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-24 18:14:13,320 - INFO - Video thread started with source: Camera
2025-11-24 18:14:13,321 - ERROR - ❌ No camera found!
2025-11-24 18:14:13,373 - INFO - Frame 1214 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:13,375 - INFO - Frame 52 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:13,529 - INFO - Video thread started with source: Camera
2025-11-24 18:14:13,530 - ERROR - ❌ No camera found!
2025-11-24 18:14:13,534 - INFO - Frame 54 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:13,583 - INFO - Frame 1216 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 0
2025-11-24 18:14:13,642 - INFO - Frame 56 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:13,754 - INFO - Video thread started with source: Camera
2025-11-24 18:14:13,755 - ERROR - ❌ No camera found!
2025-11-24 18:14:13,824 - INFO - Frame 58 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:13,826 - INFO - Frame 1218 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 1
2025-11-24 18:14:13,968 - INFO - Video thread started with source: Camera
2025-11-24 18:14:13,971 - ERROR - ❌ No camera found!
2025-11-24 18:14:13,992 - INFO - Frame 60 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:14,026 - INFO - Frame 1220 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 1
2025-11-24 18:14:14,102 - INFO - Frame 62 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:14,194 - INFO - Video thread started with source: Camera
2025-11-24 18:14:14,195 - ERROR - ❌ No camera found!
2025-11-24 18:14:14,195 - INFO - Frame 1222 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 1
2025-11-24 18:14:14,267 - INFO - Frame 64 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:14,412 - INFO - Frame 1224 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 1
2025-11-24 18:14:14,415 - INFO - Video thread started with source: Camera
2025-11-24 18:14:14,415 - INFO - Frame 66 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:14,416 - ERROR - ❌ No camera found!
2025-11-24 18:14:14,527 - INFO - Frame 68 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:14,544 - INFO - Frame 1226 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 1
2025-11-24 18:14:14,622 - INFO - Video thread started with source: Camera
2025-11-24 18:14:14,624 - ERROR - ❌ No camera found!
2025-11-24 18:14:14,708 - INFO - Frame 70 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:14,710 - INFO - Frame 1228 | PERCLOS: 0.04 | Yaw: 2.2° | Alerts: 1
2025-11-24 18:14:14,845 - INFO - Video thread started with source: Camera
2025-11-24 18:14:14,846 - ERROR - ❌ No camera found!
2025-11-24 18:14:14,854 - INFO - Frame 1230 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:14,860 - INFO - Frame 72 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:14,968 - INFO - Frame 1232 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 0
2025-11-24 18:14:14,971 - INFO - Frame 74 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:15,068 - INFO - Video thread started with source: Camera
2025-11-24 18:14:15,070 - ERROR - ❌ No camera found!
2025-11-24 18:14:15,131 - INFO - Frame 76 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:15,156 - INFO - Frame 1234 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 0
2025-11-24 18:14:15,288 - INFO - Video thread started with source: Camera
2025-11-24 18:14:15,289 - INFO - Frame 78 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:15,289 - ERROR - ❌ No camera found!
2025-11-24 18:14:15,395 - INFO - Frame 1236 | PERCLOS: 0.00 | Yaw: 6.2° | Alerts: 1
2025-11-24 18:14:15,401 - INFO - Frame 80 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:15,504 - INFO - Video thread started with source: Camera
2025-11-24 18:14:15,505 - ERROR - ❌ No camera found!
2025-11-24 18:14:15,558 - INFO - Frame 1238 | PERCLOS: 0.00 | Yaw: 6.6° | Alerts: 1
2025-11-24 18:14:15,571 - INFO - Frame 82 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:15,733 - INFO - Frame 84 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:15,735 - INFO - Video thread started with source: Camera
2025-11-24 18:14:15,735 - INFO - Frame 1240 | PERCLOS: 0.00 | Yaw: 7.3° | Alerts: 1
2025-11-24 18:14:15,736 - ERROR - ❌ No camera found!
2025-11-24 18:14:15,851 - INFO - Frame 86 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:15,955 - INFO - Video thread started with source: Camera
2025-11-24 18:14:15,957 - ERROR - ❌ No camera found!
2025-11-24 18:14:16,002 - INFO - Frame 1242 | PERCLOS: 0.00 | Yaw: 8.6° | Alerts: 1
2025-11-24 18:14:16,016 - INFO - Frame 88 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:16,161 - INFO - Video thread started with source: Camera
2025-11-24 18:14:16,163 - INFO - Frame 1244 | PERCLOS: 0.00 | Yaw: 8.7° | Alerts: 1
2025-11-24 18:14:16,164 - ERROR - ❌ No camera found!
2025-11-24 18:14:16,174 - INFO - Frame 90 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:16,285 - INFO - Frame 1246 | PERCLOS: 0.00 | Yaw: 9.1° | Alerts: 1
2025-11-24 18:14:16,294 - INFO - Frame 92 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:16,359 - INFO - Video thread started with source: Camera
2025-11-24 18:14:16,360 - ERROR - ❌ No camera found!
2025-11-24 18:14:16,457 - INFO - Frame 94 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:16,503 - INFO - Frame 1248 | PERCLOS: 0.00 | Yaw: 8.5° | Alerts: 1
2025-11-24 18:14:16,576 - INFO - Video thread started with source: Camera
2025-11-24 18:14:16,578 - ERROR - ❌ No camera found!
2025-11-24 18:14:16,600 - INFO - Frame 96 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:16,672 - INFO - Frame 1250 | PERCLOS: 0.00 | Yaw: 8.1° | Alerts: 1
2025-11-24 18:14:16,708 - INFO - Frame 98 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:16,800 - INFO - Video thread started with source: Camera
2025-11-24 18:14:16,802 - ERROR - ❌ No camera found!
2025-11-24 18:14:16,853 - INFO - Frame 1252 | PERCLOS: 0.00 | Yaw: 8.4° | Alerts: 1
2025-11-24 18:14:16,873 - INFO - Frame 100 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:17,033 - INFO - Video thread started with source: Camera
2025-11-24 18:14:17,034 - INFO - Frame 102 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:17,035 - ERROR - ❌ No camera found!
2025-11-24 18:14:17,106 - INFO - Frame 1254 | PERCLOS: 0.00 | Yaw: 8.5° | Alerts: 1
2025-11-24 18:14:17,148 - INFO - Frame 104 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:17,249 - INFO - Video thread started with source: Camera
2025-11-24 18:14:17,250 - ERROR - ❌ No camera found!
2025-11-24 18:14:17,304 - INFO - Frame 1256 | PERCLOS: 0.00 | Yaw: 8.4° | Alerts: 1
2025-11-24 18:14:17,318 - INFO - Frame 106 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:17,471 - INFO - Frame 1258 | PERCLOS: 0.00 | Yaw: 8.3° | Alerts: 1
2025-11-24 18:14:17,483 - INFO - Frame 108 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:17,578 - INFO - Frame 110 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:17,632 - INFO - Frame 1260 | PERCLOS: 0.00 | Yaw: 8.2° | Alerts: 1
2025-11-24 18:14:17,667 - INFO - Frame 112 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:17,743 - INFO - Frame 1262 | PERCLOS: 0.00 | Yaw: 7.8° | Alerts: 1
2025-11-24 18:14:17,758 - INFO - Frame 114 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:17,850 - INFO - Frame 116 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:17,857 - INFO - Frame 1264 | PERCLOS: 0.00 | Yaw: 6.5° | Alerts: 1
2025-11-24 18:14:17,871 - INFO - Video thread started with source: Camera
2025-11-24 18:14:17,874 - ERROR - ❌ No camera found!
2025-11-24 18:14:17,977 - INFO - Video thread started with source: Camera
2025-11-24 18:14:17,979 - ERROR - ❌ No camera found!
2025-11-24 18:14:18,000 - INFO - Frame 118 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:18,093 - INFO - Video thread started with source: Camera
2025-11-24 18:14:18,095 - ERROR - ❌ No camera found!
2025-11-24 18:14:18,199 - INFO - Frame 1266 | PERCLOS: 0.31 | Yaw: 5.3° | Alerts: 2
2025-11-24 18:14:18,202 - INFO - Video thread started with source: Camera
2025-11-24 18:14:18,203 - ERROR - ❌ No camera found!
2025-11-24 18:14:18,223 - INFO - Frame 120 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:18,291 - INFO - Video thread started with source: Camera
2025-11-24 18:14:18,293 - ERROR - ❌ No camera found!
2025-11-24 18:14:18,395 - INFO - Video thread started with source: Camera
2025-11-24 18:14:18,396 - ERROR - ❌ No camera found!
2025-11-24 18:14:18,397 - INFO - Frame 1268 | PERCLOS: 0.00 | Yaw: 4.8° | Alerts: 1
2025-11-24 18:14:18,416 - INFO - Frame 122 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:18,510 - INFO - Video thread started with source: Camera
2025-11-24 18:14:18,512 - ERROR - ❌ No camera found!
2025-11-24 18:14:18,627 - INFO - Video thread started with source: Camera
2025-11-24 18:14:18,643 - ERROR - ❌ No camera found!
2025-11-24 18:14:18,643 - INFO - Frame 1270 | PERCLOS: 0.00 | Yaw: 4.1° | Alerts: 1
2025-11-24 18:14:18,647 - INFO - Frame 124 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:18,745 - INFO - Video thread started with source: Camera
2025-11-24 18:14:18,747 - ERROR - ❌ No camera found!
2025-11-24 18:14:18,860 - INFO - Video thread started with source: Camera
2025-11-24 18:14:18,862 - ERROR - ❌ No camera found!
2025-11-24 18:14:18,889 - INFO - Frame 126 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:18,984 - INFO - Frame 1272 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 18:14:18,987 - INFO - Video thread started with source: Camera
2025-11-24 18:14:18,989 - ERROR - ❌ No camera found!
2025-11-24 18:14:19,087 - INFO - Video thread started with source: Camera
2025-11-24 18:14:19,102 - ERROR - ❌ No camera found!
2025-11-24 18:14:19,118 - INFO - Frame 128 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:19,145 - INFO - Frame 1274 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-24 18:14:19,230 - INFO - Video thread started with source: Camera
2025-11-24 18:14:19,231 - ERROR - ❌ No camera found!
2025-11-24 18:14:19,331 - INFO - Video thread started with source: Camera
2025-11-24 18:14:19,342 - ERROR - ❌ No camera found!
2025-11-24 18:14:19,351 - INFO - Frame 130 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:19,373 - INFO - Frame 1276 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 1
2025-11-24 18:14:19,458 - INFO - Video thread started with source: Camera
2025-11-24 18:14:19,460 - ERROR - ❌ No camera found!
2025-11-24 18:14:19,559 - INFO - Video thread started with source: Camera
2025-11-24 18:14:19,571 - ERROR - ❌ No camera found!
2025-11-24 18:14:19,584 - INFO - Frame 132 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:19,683 - INFO - Video thread started with source: Camera
2025-11-24 18:14:19,685 - ERROR - ❌ No camera found!
2025-11-24 18:14:19,707 - INFO - Frame 1278 | PERCLOS: 0.00 | Yaw: 5.9° | Alerts: 1
2025-11-24 18:14:19,788 - INFO - Video thread started with source: Camera
2025-11-24 18:14:19,789 - ERROR - ❌ No camera found!
2025-11-24 18:14:19,811 - INFO - Frame 134 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:19,886 - INFO - Video thread started with source: Camera
2025-11-24 18:14:19,888 - ERROR - ❌ No camera found!
2025-11-24 18:14:19,922 - INFO - Frame 1280 | PERCLOS: 0.00 | Yaw: 6.3° | Alerts: 1
2025-11-24 18:14:19,991 - INFO - Video thread started with source: Camera
2025-11-24 18:14:19,992 - ERROR - ❌ No camera found!
2025-11-24 18:14:20,015 - INFO - Frame 136 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:20,103 - ERROR - ❌ No camera found!
2025-11-24 18:14:20,105 - INFO - Video thread started with source: Camera
2025-11-24 18:14:20,260 - INFO - Video thread started with source: Camera
2025-11-24 18:14:20,261 - INFO - Frame 1282 | PERCLOS: 0.00 | Yaw: 6.6° | Alerts: 1
2025-11-24 18:14:20,263 - ERROR - ❌ No camera found!
2025-11-24 18:14:20,289 - INFO - Frame 138 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:20,365 - INFO - Video thread started with source: Camera
2025-11-24 18:14:20,366 - ERROR - ❌ No camera found!
2025-11-24 18:14:20,466 - INFO - Video thread started with source: Camera
2025-11-24 18:14:20,467 - ERROR - ❌ No camera found!
2025-11-24 18:14:20,488 - INFO - Video thread started with source: Camera
2025-11-24 18:14:20,491 - ERROR - ❌ No camera found!
2025-11-24 18:14:20,496 - INFO - Frame 140 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:20,627 - INFO - Frame 1284 | PERCLOS: 0.00 | Yaw: 6.5° | Alerts: 1
2025-11-24 18:14:20,630 - INFO - Video thread started with source: Camera
2025-11-24 18:14:20,631 - ERROR - ❌ No camera found!
2025-11-24 18:14:20,729 - INFO - Video thread started with source: Camera
2025-11-24 18:14:20,730 - ERROR - ❌ No camera found!
2025-11-24 18:14:20,757 - INFO - Frame 142 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:20,840 - INFO - Video thread started with source: Camera
2025-11-24 18:14:20,841 - INFO - Frame 1286 | PERCLOS: 0.00 | Yaw: 6.5° | Alerts: 1
2025-11-24 18:14:20,841 - ERROR - ❌ No camera found!
2025-11-24 18:14:20,939 - INFO - Video thread started with source: Camera
2025-11-24 18:14:20,950 - ERROR - ❌ No camera found!
2025-11-24 18:14:20,957 - INFO - Frame 144 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:21,063 - INFO - Video thread started with source: Camera
2025-11-24 18:14:21,064 - INFO - Frame 1288 | PERCLOS: 0.00 | Yaw: 7.0° | Alerts: 1
2025-11-24 18:14:21,064 - ERROR - ❌ No camera found!
2025-11-24 18:14:21,171 - INFO - Video thread started with source: Camera
2025-11-24 18:14:21,172 - ERROR - ❌ No camera found!
2025-11-24 18:14:21,276 - INFO - Video thread started with source: Camera
2025-11-24 18:14:21,277 - ERROR - ❌ No camera found!
2025-11-24 18:14:21,281 - INFO - Frame 146 | PERCLOS: 0.00 | Yaw: 7.4° | Alerts: 0
2025-11-24 18:14:21,382 - INFO - Frame 1290 | PERCLOS: 0.00 | Yaw: 7.4° | Alerts: 1
2025-11-24 18:14:21,384 - INFO - Video thread started with source: Camera
2025-11-24 18:14:21,385 - ERROR - ❌ No camera found!
2025-11-24 18:14:21,497 - INFO - Video thread started with source: Camera
2025-11-24 18:14:21,498 - ERROR - ❌ No camera found!
2025-11-24 18:14:21,600 - INFO - Video thread started with source: Camera
2025-11-24 18:14:21,602 - INFO - Frame 1292 | PERCLOS: 0.00 | Yaw: 7.6° | Alerts: 1
2025-11-24 18:14:21,602 - ERROR - ❌ No camera found!
2025-11-24 18:14:21,605 - INFO - Frame 148 | PERCLOS: 0.00 | Yaw: 7.6° | Alerts: 0
2025-11-24 18:14:21,705 - INFO - Video thread started with source: Camera
2025-11-24 18:14:21,706 - ERROR - ❌ No camera found!
2025-11-24 18:14:21,744 - INFO - Frame 1294 | PERCLOS: 0.00 | Yaw: 7.6° | Alerts: 1
2025-11-24 18:14:21,815 - INFO - Video thread started with source: Camera
2025-11-24 18:14:21,816 - ERROR - ❌ No camera found!
2025-11-24 18:14:21,822 - INFO - Frame 150 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:21,922 - INFO - Video thread started with source: Camera
2025-11-24 18:14:21,924 - ERROR - ❌ No camera found!
2025-11-24 18:14:22,038 - INFO - Video thread started with source: Camera
2025-11-24 18:14:22,040 - ERROR - ❌ No camera found!
2025-11-24 18:14:22,045 - INFO - Frame 152 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:22,061 - INFO - Frame 1296 | PERCLOS: 0.00 | Yaw: 7.5° | Alerts: 1
2025-11-24 18:14:22,143 - INFO - Video thread started with source: Camera
2025-11-24 18:14:22,143 - ERROR - ❌ No camera found!
2025-11-24 18:14:22,257 - INFO - Video thread started with source: Camera
2025-11-24 18:14:22,258 - ERROR - ❌ No camera found!
2025-11-24 18:14:22,263 - INFO - Frame 154 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:22,293 - INFO - Frame 1298 | PERCLOS: 0.36 | Yaw: 6.3° | Alerts: 2
2025-11-24 18:14:22,370 - INFO - Video thread started with source: Camera
2025-11-24 18:14:22,371 - ERROR - ❌ No camera found!
2025-11-24 18:14:22,485 - INFO - Video thread started with source: Camera
2025-11-24 18:14:22,486 - ERROR - ❌ No camera found!
2025-11-24 18:14:22,493 - INFO - Frame 156 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:22,520 - INFO - Frame 1300 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 18:14:22,597 - INFO - Video thread started with source: Camera
2025-11-24 18:14:22,598 - ERROR - ❌ No camera found!
2025-11-24 18:14:22,713 - INFO - Video thread started with source: Camera
2025-11-24 18:14:22,714 - ERROR - ❌ No camera found!
2025-11-24 18:14:22,718 - INFO - Frame 158 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:22,821 - INFO - Video thread started with source: Camera
2025-11-24 18:14:22,822 - ERROR - ❌ No camera found!
2025-11-24 18:14:22,841 - INFO - Frame 1302 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-24 18:14:22,936 - INFO - Video thread started with source: Camera
2025-11-24 18:14:22,937 - ERROR - ❌ No camera found!
2025-11-24 18:14:22,940 - INFO - Frame 160 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:23,042 - INFO - Video thread started with source: Camera
2025-11-24 18:14:23,044 - ERROR - ❌ No camera found!
2025-11-24 18:14:23,074 - INFO - Frame 1304 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 1
2025-11-24 18:14:23,156 - INFO - Video thread started with source: Camera
2025-11-24 18:14:23,157 - ERROR - ❌ No camera found!
2025-11-24 18:14:23,161 - INFO - Frame 162 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:23,259 - INFO - Video thread started with source: Camera
2025-11-24 18:14:23,260 - ERROR - ❌ No camera found!
2025-11-24 18:14:23,291 - INFO - Frame 1306 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 1
2025-11-24 18:14:23,372 - INFO - Video thread started with source: Camera
2025-11-24 18:14:23,373 - ERROR - ❌ No camera found!
2025-11-24 18:14:23,377 - INFO - Frame 164 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:23,479 - INFO - Video thread started with source: Camera
2025-11-24 18:14:23,480 - ERROR - ❌ No camera found!
2025-11-24 18:14:23,598 - INFO - Video thread started with source: Camera
2025-11-24 18:14:23,599 - ERROR - ❌ No camera found!
2025-11-24 18:14:23,604 - INFO - Frame 166 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:23,617 - INFO - Frame 1308 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 1
2025-11-24 18:14:23,708 - INFO - Video thread started with source: Camera
2025-11-24 18:14:23,709 - ERROR - ❌ No camera found!
2025-11-24 18:14:23,823 - INFO - Video thread started with source: Camera
2025-11-24 18:14:23,825 - ERROR - ❌ No camera found!
2025-11-24 18:14:23,829 - INFO - Frame 168 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:23,856 - INFO - Frame 1310 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 1
2025-11-24 18:14:23,931 - INFO - Video thread started with source: Camera
2025-11-24 18:14:23,933 - ERROR - ❌ No camera found!
2025-11-24 18:14:24,040 - INFO - Frame 1312 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:24,043 - INFO - Video thread started with source: Camera
2025-11-24 18:14:24,044 - ERROR - ❌ No camera found!
2025-11-24 18:14:24,048 - INFO - Frame 170 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:24,142 - INFO - Video thread started with source: Camera
2025-11-24 18:14:24,143 - ERROR - ❌ No camera found!
2025-11-24 18:14:24,250 - INFO - Video thread started with source: Camera
2025-11-24 18:14:24,251 - ERROR - ❌ No camera found!
2025-11-24 18:14:24,256 - INFO - Frame 172 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:24,348 - INFO - Frame 1314 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 1
2025-11-24 18:14:24,350 - INFO - Video thread started with source: Camera
2025-11-24 18:14:24,351 - ERROR - ❌ No camera found!
2025-11-24 18:14:24,448 - INFO - Video thread started with source: Camera
2025-11-24 18:14:24,449 - ERROR - ❌ No camera found!
2025-11-24 18:14:24,555 - INFO - Video thread started with source: Camera
2025-11-24 18:14:24,556 - ERROR - ❌ No camera found!
2025-11-24 18:14:24,558 - INFO - Frame 1316 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 1
2025-11-24 18:14:24,657 - INFO - Video thread started with source: Camera
2025-11-24 18:14:24,658 - ERROR - ❌ No camera found!
2025-11-24 18:14:24,779 - INFO - Frame 174 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 1
2025-11-24 18:14:24,779 - INFO - Video thread started with source: Camera
2025-11-24 18:14:24,779 - INFO - Frame 1318 | PERCLOS: 0.00 | Yaw: 0.2° | Alerts: 1
2025-11-24 18:14:24,780 - ERROR - ❌ No camera found!
2025-11-24 18:14:24,875 - INFO - Video thread started with source: Camera
2025-11-24 18:14:24,876 - ERROR - ❌ No camera found!
2025-11-24 18:14:24,976 - INFO - Video thread started with source: Camera
2025-11-24 18:14:24,976 - INFO - Frame 176 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:24,977 - ERROR - ❌ No camera found!
2025-11-24 18:14:25,074 - INFO - Frame 1320 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 1
2025-11-24 18:14:25,077 - INFO - Video thread started with source: Camera
2025-11-24 18:14:25,078 - ERROR - ❌ No camera found!
2025-11-24 18:14:25,182 - INFO - Video thread started with source: Camera
2025-11-24 18:14:25,182 - INFO - Frame 178 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:25,183 - ERROR - ❌ No camera found!
2025-11-24 18:14:25,284 - INFO - Video thread started with source: Camera
2025-11-24 18:14:25,285 - ERROR - ❌ No camera found!
2025-11-24 18:14:25,285 - INFO - Frame 1322 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 1
2025-11-24 18:14:25,388 - INFO - Video thread started with source: Camera
2025-11-24 18:14:25,389 - ERROR - ❌ No camera found!
2025-11-24 18:14:25,393 - INFO - Frame 180 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:25,485 - INFO - Video thread started with source: Camera
2025-11-24 18:14:25,486 - ERROR - ❌ No camera found!
2025-11-24 18:14:25,515 - INFO - Frame 1324 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 1
2025-11-24 18:14:25,595 - INFO - Video thread started with source: Camera
2025-11-24 18:14:25,596 - ERROR - ❌ No camera found!
2025-11-24 18:14:25,600 - INFO - Frame 182 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:25,700 - INFO - Video thread started with source: Camera
2025-11-24 18:14:25,701 - ERROR - ❌ No camera found!
2025-11-24 18:14:25,808 - INFO - Video thread started with source: Camera
2025-11-24 18:14:25,822 - ERROR - ❌ No camera found!
2025-11-24 18:14:25,829 - INFO - Frame 1326 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 1
2025-11-24 18:14:25,833 - INFO - Frame 184 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:25,925 - INFO - Video thread started with source: Camera
2025-11-24 18:14:25,926 - ERROR - ❌ No camera found!
2025-11-24 18:14:26,030 - INFO - Frame 1328 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:26,034 - INFO - Video thread started with source: Camera
2025-11-24 18:14:26,035 - ERROR - ❌ No camera found!
2025-11-24 18:14:26,040 - INFO - Frame 186 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:26,144 - INFO - Video thread started with source: Camera
2025-11-24 18:14:26,145 - ERROR - ❌ No camera found!
2025-11-24 18:14:26,258 - INFO - Frame 1330 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 0
2025-11-24 18:14:26,258 - INFO - Video thread started with source: Camera
2025-11-24 18:14:26,259 - ERROR - ❌ No camera found!
2025-11-24 18:14:26,263 - INFO - Frame 188 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:26,357 - INFO - Video thread started with source: Camera
2025-11-24 18:14:26,358 - ERROR - ❌ No camera found!
2025-11-24 18:14:26,463 - INFO - Video thread started with source: Camera
2025-11-24 18:14:26,464 - ERROR - ❌ No camera found!
2025-11-24 18:14:26,469 - INFO - Frame 190 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:26,559 - INFO - Frame 1332 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 1
2025-11-24 18:14:26,561 - INFO - Video thread started with source: Camera
2025-11-24 18:14:26,563 - ERROR - ❌ No camera found!
2025-11-24 18:14:26,670 - INFO - Frame 192 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:26,670 - INFO - Video thread started with source: Camera
2025-11-24 18:14:26,672 - ERROR - ❌ No camera found!
2025-11-24 18:14:26,767 - INFO - Video thread started with source: Camera
2025-11-24 18:14:26,768 - INFO - Frame 1334 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 1
2025-11-24 18:14:26,769 - ERROR - ❌ No camera found!
2025-11-24 18:14:26,875 - INFO - Video thread started with source: Camera
2025-11-24 18:14:26,876 - ERROR - ❌ No camera found!
2025-11-24 18:14:26,978 - INFO - Video thread started with source: Camera
2025-11-24 18:14:26,980 - ERROR - ❌ No camera found!
2025-11-24 18:14:26,980 - INFO - Frame 1336 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 1
2025-11-24 18:14:26,983 - INFO - Frame 194 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 0
2025-11-24 18:14:27,078 - INFO - Video thread started with source: Camera
2025-11-24 18:14:27,079 - ERROR - ❌ No camera found!
2025-11-24 18:14:27,181 - INFO - Video thread started with source: Camera
2025-11-24 18:14:27,182 - ERROR - ❌ No camera found!
2025-11-24 18:14:27,285 - INFO - Video thread started with source: Camera
2025-11-24 18:14:27,286 - ERROR - ❌ No camera found!
2025-11-24 18:14:27,290 - INFO - Frame 196 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 0
2025-11-24 18:14:27,390 - INFO - Frame 1338 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 1
2025-11-24 18:14:27,392 - INFO - Video thread started with source: Camera
2025-11-24 18:14:27,394 - ERROR - ❌ No camera found!
2025-11-24 18:14:27,498 - INFO - Video thread started with source: Camera
2025-11-24 18:14:27,499 - ERROR - ❌ No camera found!
2025-11-24 18:14:27,601 - INFO - Video thread started with source: Camera
2025-11-24 18:14:27,602 - INFO - Frame 1340 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 1
2025-11-24 18:14:27,603 - ERROR - ❌ No camera found!
2025-11-24 18:14:27,717 - INFO - Video thread started with source: Camera
2025-11-24 18:14:27,719 - ERROR - ❌ No camera found!
2025-11-24 18:14:27,755 - INFO - Frame 1342 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 1
2025-11-24 18:14:27,823 - INFO - Video thread started with source: Camera
2025-11-24 18:14:27,824 - INFO - Frame 198 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 1
2025-11-24 18:14:27,824 - ERROR - ❌ No camera found!
2025-11-24 18:14:27,920 - INFO - Video thread started with source: Camera
2025-11-24 18:14:27,922 - ERROR - ❌ No camera found!
2025-11-24 18:14:28,029 - INFO - Video thread started with source: Camera
2025-11-24 18:14:28,030 - ERROR - ❌ No camera found!
2025-11-24 18:14:28,034 - INFO - Frame 200 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:28,125 - INFO - Frame 1344 | PERCLOS: 0.00 | Yaw: 4.8° | Alerts: 1
2025-11-24 18:14:28,127 - INFO - Video thread started with source: Camera
2025-11-24 18:14:28,128 - ERROR - ❌ No camera found!
2025-11-24 18:14:28,234 - INFO - Video thread started with source: Camera
2025-11-24 18:14:28,235 - ERROR - ❌ No camera found!
2025-11-24 18:14:28,342 - INFO - Video thread started with source: Camera
2025-11-24 18:14:28,343 - INFO - Frame 1346 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 1
2025-11-24 18:14:28,344 - ERROR - ❌ No camera found!
2025-11-24 18:14:28,347 - INFO - Frame 202 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 0
2025-11-24 18:14:28,445 - INFO - Video thread started with source: Camera
2025-11-24 18:14:28,446 - ERROR - ❌ No camera found!
2025-11-24 18:14:28,483 - INFO - Frame 1348 | PERCLOS: 0.00 | Yaw: 5.8° | Alerts: 1
2025-11-24 18:14:28,561 - INFO - Video thread started with source: Camera
2025-11-24 18:14:28,562 - ERROR - ❌ No camera found!
2025-11-24 18:14:28,566 - INFO - Frame 204 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:28,869 - INFO - Video thread started with source: Camera
2025-11-24 18:14:28,870 - ERROR - ❌ No camera found!
2025-11-24 18:14:29,037 - INFO - Frame 206 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:29,046 - INFO - Video file uploaded: assets/temp_videos/Screen Recording 2025-11-24 at 5.55.42 PM.mov
2025-11-24 18:14:29,047 - INFO - Video thread started with source: assets/temp_videos/Screen Recording 2025-11-24 at 5.55.42 PM.mov
2025-11-24 18:14:29,061 - INFO - Frame 1350 | PERCLOS: 0.00 | Yaw: 6.2° | Alerts: 1
2025-11-24 18:14:29,063 - INFO - ✓ Video file opened: assets/temp_videos/Screen Recording 2025-11-24 at 5.55.42 PM.mov
2025-11-24 18:14:29,195 - INFO - Frame 0 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:29,225 - INFO - Frame 208 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:29,343 - INFO - Frame 1352 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:29,344 - INFO - Frame 2 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:29,400 - INFO - Frame 4 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:29,466 - INFO - Frame 210 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:29,539 - INFO - Frame 6 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:29,546 - INFO - Frame 1354 | PERCLOS: 0.00 | Yaw: 6.3° | Alerts: 0
2025-11-24 18:14:29,681 - INFO - Frame 8 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:29,737 - INFO - Frame 10 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:29,743 - INFO - Frame 212 | PERCLOS: 0.00 | Yaw: 5.9° | Alerts: 0
2025-11-24 18:14:29,858 - INFO - Frame 1356 | PERCLOS: 0.00 | Yaw: 5.9° | Alerts: 1
2025-11-24 18:14:29,871 - INFO - Frame 12 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:29,997 - INFO - Frame 14 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:29,997 - INFO - Frame 214 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:30,083 - INFO - Frame 16 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:30,086 - INFO - Frame 1358 | PERCLOS: 0.38 | Yaw: 6.1° | Alerts: 2
2025-11-24 18:14:30,230 - INFO - Frame 18 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:30,232 - INFO - Frame 216 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:30,285 - INFO - Frame 20 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:30,388 - INFO - Frame 1360 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 1
2025-11-24 18:14:30,417 - INFO - Frame 22 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:30,420 - INFO - Frame 218 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:30,524 - INFO - Frame 1362 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:30,526 - INFO - Frame 24 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:30,587 - INFO - Frame 220 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:30,618 - INFO - Frame 26 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:30,744 - INFO - Frame 1364 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 0
2025-11-24 18:14:30,773 - INFO - Frame 28 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:30,775 - INFO - Frame 222 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:30,888 - INFO - Frame 1366 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:30,890 - INFO - Frame 30 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:30,951 - INFO - Frame 224 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:30,972 - INFO - Frame 32 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:31,129 - INFO - Frame 34 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:31,135 - INFO - Frame 226 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:31,157 - INFO - Frame 1368 | PERCLOS: 0.00 | Yaw: 5.2° | Alerts: 1
2025-11-24 18:14:31,178 - INFO - Frame 36 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:31,311 - INFO - Frame 38 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:31,313 - INFO - Frame 228 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:31,357 - INFO - Frame 1370 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-24 18:14:31,422 - INFO - Frame 40 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:31,516 - INFO - Frame 42 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:31,642 - INFO - Frame 1372 | PERCLOS: 0.00 | Yaw: 5.4° | Alerts: 1
2025-11-24 18:14:31,643 - INFO - Frame 230 | PERCLOS: 0.00 | Yaw: 5.4° | Alerts: 0
2025-11-24 18:14:31,665 - INFO - Frame 44 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:31,710 - INFO - Frame 46 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:31,844 - INFO - Frame 48 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:31,847 - INFO - Frame 232 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:31,949 - INFO - Frame 50 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:31,951 - INFO - Frame 1374 | PERCLOS: 0.00 | Yaw: 5.4° | Alerts: 1
2025-11-24 18:14:32,022 - INFO - Frame 52 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:32,025 - INFO - Frame 234 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:32,136 - INFO - Frame 54 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:32,138 - INFO - Frame 1376 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 1
2025-11-24 18:14:32,224 - INFO - Frame 56 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:32,226 - INFO - Frame 236 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:32,370 - INFO - Frame 58 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:32,378 - INFO - Frame 1378 | PERCLOS: 0.00 | Yaw: 5.8° | Alerts: 1
2025-11-24 18:14:32,473 - INFO - Frame 60 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:32,504 - INFO - Frame 238 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:32,558 - INFO - Frame 62 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:32,648 - INFO - Frame 1380 | PERCLOS: 0.00 | Yaw: 5.9° | Alerts: 1
2025-11-24 18:14:32,687 - INFO - Frame 64 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:32,711 - INFO - Frame 240 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:32,759 - INFO - Frame 66 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:32,858 - INFO - Frame 1382 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-24 18:14:32,890 - INFO - Frame 68 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:32,893 - INFO - Frame 242 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:33,004 - INFO - Frame 1384 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:33,004 - INFO - Frame 70 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:33,066 - INFO - Frame 244 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:33,098 - INFO - Frame 72 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:33,260 - INFO - Frame 74 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:33,262 - INFO - Frame 246 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:33,278 - INFO - Frame 1386 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 18:14:33,370 - INFO - Frame 76 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:33,441 - INFO - Frame 248 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:33,463 - INFO - Frame 78 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:33,578 - INFO - Frame 1388 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 18:14:33,602 - INFO - Frame 80 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:33,643 - INFO - Frame 250 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:33,798 - INFO - Frame 1390 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 18:14:33,802 - INFO - Frame 82 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 0
2025-11-24 18:14:33,925 - INFO - Frame 252 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:33,947 - INFO - Frame 84 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:33,997 - INFO - Frame 86 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:34,130 - INFO - Frame 88 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:34,132 - INFO - Frame 254 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:34,149 - INFO - Frame 1392 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 1
2025-11-24 18:14:34,183 - INFO - Frame 90 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:34,324 - INFO - Frame 92 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:34,327 - INFO - Frame 256 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:34,343 - INFO - Frame 1394 | PERCLOS: 0.00 | Yaw: 4.1° | Alerts: 1
2025-11-24 18:14:34,440 - INFO - Frame 94 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:34,508 - INFO - Frame 258 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:34,533 - INFO - Frame 96 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:14:34,659 - INFO - Frame 1396 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 1
2025-11-24 18:14:34,691 - ERROR - Error processing frame: CalculatorGraph::Run() failed: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:34,691 - ERROR - Error processing frame: CalculatorGraph::Run() failed: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:34,730 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:34,733 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:34,865 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:34,872 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:34,888 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:34,915 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:35,032 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:35,036 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:35,044 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:35,081 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:35,152 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:35,206 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:35,211 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:35,252 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:35,252 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:35,365 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:35,368 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:35,379 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:35,414 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:35,505 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:35,521 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:35,529 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:35,568 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:35,635 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:35,687 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:35,691 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:35,734 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:35,734 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:35,841 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:35,849 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:35,863 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:35,894 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:36,001 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:36,005 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:36,015 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:36,048 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:36,115 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:36,158 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:36,165 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:36,207 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:36,277 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:36,329 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:36,332 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:36,374 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:36,377 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:36,479 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:36,488 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:36,502 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:36,532 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:36,640 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:36,643 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:36,655 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:36,684 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:36,752 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:36,796 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:36,804 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:36,832 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:36,847 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:36,962 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:36,965 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:36,976 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:37,010 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:37,104 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:37,117 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:37,127 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:37,168 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:37,262 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:37,284 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:37,289 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:37,332 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:37,333 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:37,452 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:37,462 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:37,470 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:37,506 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:37,571 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:37,624 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:37,628 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:37,671 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:37,671 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:37,786 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:37,792 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:37,808 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:37,836 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:37,953 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:37,956 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:37,964 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:37,998 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:38,092 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:38,108 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:38,116 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:38,159 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:38,253 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:38,276 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:38,279 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:38,322 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:38,325 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:38,437 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:38,443 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:38,456 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:38,485 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:38,595 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:38,598 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:38,610 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:38,641 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:38,738 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:38,750 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:38,758 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:38,800 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:38,894 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:38,919 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:38,923 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:38,965 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:38,965 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:39,071 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:39,078 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:39,093 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:39,121 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:39,218 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:39,236 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:39,240 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:39,282 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:39,355 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:39,399 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:39,409 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:39,452 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:39,544 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:39,567 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:39,571 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:39,615 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:39,617 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:39,721 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:39,731 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:39,745 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:39,776 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:39,888 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:39,892 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:39,897 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:39,935 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:40,022 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:40,042 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:40,047 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:40,088 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:40,180 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:40,200 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:40,206 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:40,248 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:40,250 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:40,354 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:40,362 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:40,377 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:40,404 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:40,517 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:40,521 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:40,531 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:40,565 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:40,659 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:40,673 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:40,682 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:40,722 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:40,813 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:40,836 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:40,841 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:40,882 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:40,884 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:40,990 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:40,999 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:41,013 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:41,041 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:41,153 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:41,156 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:41,165 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:41,198 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:41,293 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:41,307 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:41,314 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:41,354 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:41,447 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:41,469 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:41,472 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:41,514 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:41,516 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:41,617 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:41,628 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:41,636 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:41,679 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:41,751 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:41,802 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:41,807 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:41,839 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:41,849 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:41,965 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:41,974 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:41,987 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:42,017 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:42,149 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:42,154 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:42,157 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:42,198 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:42,288 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:42,305 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:42,312 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:42,352 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:42,419 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:42,473 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:42,478 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:42,520 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:42,521 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:42,630 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:42,638 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:42,652 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:42,682 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:42,793 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:42,796 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:42,804 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:42,839 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:42,931 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:42,949 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:42,956 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:42,998 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:43,062 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:43,116 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:43,119 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:43,164 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:43,169 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:43,314 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:43,318 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:43,333 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:43,362 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:43,479 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:43,482 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:43,492 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:43,524 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:43,618 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:43,631 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:43,640 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:43,682 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:43,741 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:43,793 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:43,796 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:43,837 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:43,839 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:43,946 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:43,955 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:43,969 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:43,997 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:44,117 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:44,120 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:44,130 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:44,164 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:44,266 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:44,280 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:44,288 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:44,331 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:44,432 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:44,459 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:44,463 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:44,503 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:44,506 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:44,611 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:44,617 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:44,623 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:44,664 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:44,755 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:44,776 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:44,781 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:44,823 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:44,826 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:44,934 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:44,942 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:44,956 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:44,984 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:45,095 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:45,099 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:45,111 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:45,140 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:45,234 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:45,250 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:45,258 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:45,299 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:45,359 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:45,416 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:45,420 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:45,432 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:45,465 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:45,530 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:45,574 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:45,582 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:45,623 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:45,714 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:45,734 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:45,739 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:45,783 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:45,784 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:45,895 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:45,905 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:45,918 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:46,005 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:46,061 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:46,072 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:46,085 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:46,166 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:46,198 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:46,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:46,243 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:46,349 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:46,354 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:46,373 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:46,398 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:46,420 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:46,514 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:46,527 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:46,549 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:46,559 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:46,669 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:46,690 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:46,703 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:46,715 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:46,827 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:46,829 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:46,841 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:46,873 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:46,978 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:46,978 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:47,005 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:47,027 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:47,048 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:47,144 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:47,150 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:47,161 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:47,189 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:47,299 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:47,303 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:47,322 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:47,348 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:47,370 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:47,474 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:47,490 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:47,512 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:47,516 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:47,634 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:47,638 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:47,658 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:47,682 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:47,686 - INFO - End of video file reached
2025-11-24 18:14:47,687 - INFO - Video capture loop ended
2025-11-24 18:14:47,707 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:47,799 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:47,833 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:47,841 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:47,944 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:47,979 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:47,984 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:48,094 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:48,127 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:48,135 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:48,258 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:48,273 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:48,298 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:48,398 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:48,407 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:48,447 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:48,535 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:48,558 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:48,598 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:48,682 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:48,702 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:48,744 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:48,827 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:48,850 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:48,892 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:48,981 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:49,005 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:49,045 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:49,131 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:49,153 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:49,194 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:49,286 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:49,309 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:49,348 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:49,442 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:49,463 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:49,503 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:49,598 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:49,622 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:49,663 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:49,753 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:49,776 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:49,816 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:49,905 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:49,927 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:49,966 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:50,023 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:50,073 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:50,114 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:50,171 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:50,222 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:50,263 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:50,350 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:50,372 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:50,465 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:50,467 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:50,520 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:50,560 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:50,616 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:50,664 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:50,705 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:50,792 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:50,813 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:50,854 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:50,937 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:50,961 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:51,001 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:51,093 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:51,124 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:51,239 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:51,239 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:51,280 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:51,390 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:51,390 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:51,431 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:51,508 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:51,535 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:51,579 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:51,654 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:51,686 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:51,727 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:51,835 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:51,836 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:51,878 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:51,990 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:51,991 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:52,031 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:52,115 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:52,116 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:52,188 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:52,191 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:52,293 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:52,328 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:52,335 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:52,444 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:52,478 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:52,484 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:52,594 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:52,627 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:52,633 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:52,745 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:52,781 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:52,787 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:52,893 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:52,926 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:52,933 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:53,041 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:53,078 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:53,082 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:53,189 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:53,223 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:53,232 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:53,345 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:53,379 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:53,385 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:53,462 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:53,503 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:53,516 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:53,558 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:53,615 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:53,665 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:53,706 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:53,795 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:53,817 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:53,857 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:53,946 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:53,966 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:54,007 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:54,072 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:54,124 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:54,163 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:54,249 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:54,272 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:54,313 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:54,372 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:54,407 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:54,443 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:54,447 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:54,556 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:54,559 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:54,597 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:54,700 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:54,703 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:54,745 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:54,853 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:54,857 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:54,897 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:55,008 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:55,008 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:55,050 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:55,130 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:55,159 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:55,200 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:55,306 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:55,307 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:55,349 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:55,478 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:55,497 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:55,539 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:55,624 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:55,645 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:55,684 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:55,770 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:55,774 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:55,813 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:55,920 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:55,921 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:55,962 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:56,066 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:56,068 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:56,110 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:56,219 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:56,222 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:56,262 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:56,337 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:56,338 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:56,408 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:56,485 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:56,518 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:56,561 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:56,667 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:56,667 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:56,708 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:56,783 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:56,785 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:56,853 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:56,859 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:56,965 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:56,998 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:57,007 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:57,086 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:57,148 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:57,153 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:57,264 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:57,297 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:57,306 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:57,419 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:57,426 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:57,467 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:57,542 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:57,593 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:57,632 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:57,726 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:57,748 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:57,789 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:57,874 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:57,895 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:57,935 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:58,020 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:58,043 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:58,083 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:58,166 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:58,191 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:58,230 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:58,318 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:58,341 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:58,380 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:58,437 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:58,488 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:58,529 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:58,618 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:58,643 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:58,682 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:58,747 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:58,800 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:58,841 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:58,933 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:58,956 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:59,053 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:59,083 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:59,125 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:59,234 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:59,235 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:59,278 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:59,358 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:59,390 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:59,428 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:59,431 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:59,515 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:59,553 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:59,584 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:59,662 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:59,664 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:59,734 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:59,738 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:59,847 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:59,879 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:59,888 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:14:59,996 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:00,029 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:00,036 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:00,144 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:00,177 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:00,185 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:00,308 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:00,324 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:00,347 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:00,457 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:00,472 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:00,497 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:00,605 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:00,617 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:00,647 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:00,763 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:00,768 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:00,877 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:00,912 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:00,918 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:01,029 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:01,061 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:01,069 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:01,180 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:01,213 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:01,220 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:01,331 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:01,365 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:01,373 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:01,457 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:01,497 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:01,528 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:01,630 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:01,631 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:01,674 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:01,779 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:01,781 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:01,823 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:01,928 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:01,930 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:01,970 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:02,051 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:02,085 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:02,122 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:02,129 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:02,244 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:02,279 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:02,285 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:02,396 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:02,430 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:02,438 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:02,548 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:02,582 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:02,589 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:02,695 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:02,728 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:02,739 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:02,842 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:02,877 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:02,883 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:02,990 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:03,023 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:03,031 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:03,139 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:03,174 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:03,180 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:03,289 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:03,323 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:03,330 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:03,409 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:03,472 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:03,479 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:03,583 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:03,617 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:03,625 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:03,732 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:03,768 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:03,775 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:03,887 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:03,923 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:03,930 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:04,037 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:04,072 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:04,079 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:04,156 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:04,191 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:04,211 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:04,250 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:04,336 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:04,358 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:04,398 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:04,454 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:04,508 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:04,549 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:04,642 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:04,663 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:04,703 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:04,798 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:04,819 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:04,861 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:04,952 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:04,975 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:05,015 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:05,108 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:05,129 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:05,168 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:05,262 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:05,284 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:05,324 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:05,387 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:05,439 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:05,480 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:05,537 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:05,586 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:05,628 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:05,685 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:05,734 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:05,759 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:05,775 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:05,888 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:05,901 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:05,929 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:06,033 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:06,047 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:06,074 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:06,172 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:06,195 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:06,278 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:06,310 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:06,351 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:06,355 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:06,461 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:06,497 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:06,502 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:06,608 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:06,641 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:06,649 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:06,730 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:06,770 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:06,798 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:06,884 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:06,887 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:06,954 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:06,959 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:07,046 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:07,114 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:07,116 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:07,227 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:07,260 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:07,267 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:07,349 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:07,388 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:07,418 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:07,526 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:07,526 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:07,566 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:07,648 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:07,678 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:07,719 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:07,829 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:07,831 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:07,871 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:07,955 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:07,987 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:08,029 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:08,031 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:08,144 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:08,177 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:08,186 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:08,324 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:08,357 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:08,367 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:08,491 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:08,504 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:08,531 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:08,638 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:08,652 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:08,680 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:08,773 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:08,786 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:08,827 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:08,912 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:08,951 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:09,059 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:09,059 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:09,103 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:09,204 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:09,208 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:09,248 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:09,356 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:09,357 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:09,398 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:09,504 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:09,506 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:09,546 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:09,626 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:09,653 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:09,694 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:09,770 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:09,797 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:09,839 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:09,947 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:09,947 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:09,988 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:10,065 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:10,096 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:10,138 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:10,216 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:10,218 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:10,290 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:10,401 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:10,401 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:10,444 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:10,550 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:10,551 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:10,592 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:10,696 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:10,696 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:10,736 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:10,842 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:10,843 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:10,883 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:10,961 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:10,992 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:11,032 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:11,145 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:11,147 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:11,187 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:11,290 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:11,292 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:11,332 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:11,440 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:11,441 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:11,481 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:11,587 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:11,587 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:11,630 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:11,737 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:11,739 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:11,779 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:11,854 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:11,856 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:11,926 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:11,931 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:12,041 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:12,076 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:12,082 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:12,188 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:12,222 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:12,230 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:12,338 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:12,374 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:12,379 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:12,486 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:12,522 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:12,529 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:12,636 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:12,669 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:12,678 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:12,786 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:12,822 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:12,828 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:12,937 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:12,972 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:12,979 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:13,082 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:13,116 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:13,123 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:13,228 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:13,262 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:13,269 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:13,375 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:13,408 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:13,416 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:13,525 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:13,558 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:13,565 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:13,669 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:13,704 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:13,711 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:13,821 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:13,857 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:13,863 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:13,970 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:14,005 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:14,013 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:14,091 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:14,129 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:14,162 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:14,273 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:14,273 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:14,314 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:14,427 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:14,428 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:14,469 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:14,578 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:14,581 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:14,622 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:14,702 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:14,705 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:14,774 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:14,860 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:14,861 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:14,932 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:15,045 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:15,046 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:15,087 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:15,190 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:15,191 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:15,232 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:15,337 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:15,338 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:15,380 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:15,487 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:15,489 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:15,530 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:15,637 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:15,637 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:15,679 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:15,783 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:15,784 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:15,825 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:15,903 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:15,935 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:15,980 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:15,980 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:16,095 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:16,128 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:16,136 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:16,246 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:16,281 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:16,288 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:16,391 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:16,423 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:16,431 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:16,542 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:16,577 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:16,583 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:16,687 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:16,722 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:16,729 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:16,835 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:16,868 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:16,878 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:16,984 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:17,016 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:17,027 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:17,130 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:17,165 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:17,171 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:17,278 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:17,312 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:17,320 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:17,431 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:17,465 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:17,473 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:17,583 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:17,619 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:17,626 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:17,735 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:17,770 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:17,778 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:17,889 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:17,924 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:17,931 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:18,047 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:18,079 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:18,087 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:18,201 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:18,235 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:18,243 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:18,347 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:18,383 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:18,388 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:18,493 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:18,530 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:18,535 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:18,642 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:18,676 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:18,683 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:18,795 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:18,831 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:18,837 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:18,941 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:18,974 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:18,981 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:19,090 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:19,126 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:19,131 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:19,240 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:19,275 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:19,281 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:19,363 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:19,430 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:19,433 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:19,548 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:19,581 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:19,590 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:19,697 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:19,731 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:19,738 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:19,840 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:19,875 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:19,881 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:19,988 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:20,023 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:20,030 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:20,180 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:20,182 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:20,225 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:20,304 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:20,339 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:20,379 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:20,380 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:20,485 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:20,519 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:20,527 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:20,605 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:20,642 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:20,662 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:20,701 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:20,789 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:20,813 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:20,852 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:20,938 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:20,961 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:20,999 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:21,056 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:21,108 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:21,148 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:21,232 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:21,255 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:21,297 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:21,391 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:21,411 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:21,452 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:21,547 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:21,570 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:21,612 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:21,673 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:21,724 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:21,749 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:21,763 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:21,877 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:21,891 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:21,919 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:22,012 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:22,026 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:22,120 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:22,149 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:22,191 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:22,266 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:22,295 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:22,337 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:22,445 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:22,446 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:22,487 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:22,567 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:22,569 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:22,639 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:22,717 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:22,747 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:22,790 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:22,896 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:22,896 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:22,938 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:23,038 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:23,059 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:23,098 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:23,193 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:23,211 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:23,251 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:23,338 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:23,360 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:23,401 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:23,491 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:23,516 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:23,608 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:23,608 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:23,678 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:23,789 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:23,790 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:23,831 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:23,942 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:23,943 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:23,982 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:24,087 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:24,090 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:24,129 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:24,235 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:24,235 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:24,277 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:24,381 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:24,383 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:24,426 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:24,536 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:24,536 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:24,577 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:24,678 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:24,678 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:24,720 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:24,824 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:24,824 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:24,865 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:24,944 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:24,973 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:25,015 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:25,118 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:25,120 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:25,161 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:25,265 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:25,266 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:25,308 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:25,410 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:25,411 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:25,451 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:25,562 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:25,565 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:25,608 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:25,684 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:25,714 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:25,756 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:25,834 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:25,836 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:25,905 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:25,910 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:26,022 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:26,057 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:26,064 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:26,180 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:26,214 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:26,223 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:26,338 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:26,370 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:26,379 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:26,491 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:26,524 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:26,532 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:26,646 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:26,680 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:26,689 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:26,793 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:26,825 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:26,833 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:26,942 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:26,977 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:26,983 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:27,086 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:27,120 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:27,128 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:27,238 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:27,270 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:27,280 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:27,395 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:27,405 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:27,437 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:27,547 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:27,549 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:27,591 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:27,704 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:27,708 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:27,757 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:27,830 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:27,880 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:27,906 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:27,920 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:28,040 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:28,052 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:28,080 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:28,197 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:28,210 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:28,239 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:28,344 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:28,360 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:28,383 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:28,482 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:28,494 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:28,533 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:28,590 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:28,642 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:28,681 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:28,771 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:28,793 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:28,832 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:28,921 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:28,942 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:28,982 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:29,073 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:29,094 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:29,133 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:29,227 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:29,248 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:29,289 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:29,352 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:29,404 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:29,445 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:29,536 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:29,559 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:29,600 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:29,691 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:29,714 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:29,754 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:29,838 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:29,860 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:29,901 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:29,987 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:30,009 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:30,048 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:30,137 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:30,159 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:30,198 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:30,284 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:30,307 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:30,346 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:30,434 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:30,454 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:30,496 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:30,584 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:30,609 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:30,649 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:30,715 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:30,765 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:30,806 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:30,898 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:30,923 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:30,965 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:31,057 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:31,079 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:31,118 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:31,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:31,232 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:31,273 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:31,337 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:31,389 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:31,430 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:31,525 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:31,546 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:31,586 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:31,676 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:31,697 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:31,809 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:31,811 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:31,890 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:31,971 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:32,000 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:32,040 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:32,149 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:32,149 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:32,192 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:32,298 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:32,298 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:32,339 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:32,415 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:32,415 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:32,483 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:32,598 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:32,599 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:32,640 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:32,744 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:32,745 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:32,785 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:32,895 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:32,896 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:32,937 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:33,038 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:33,060 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:33,100 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:33,190 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:33,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:33,250 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:33,345 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:33,366 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:33,406 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:33,464 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:33,516 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:33,540 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:33,556 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:33,660 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:33,673 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:33,713 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:33,803 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:33,825 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:33,866 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:33,924 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:33,978 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:34,000 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:34,017 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:34,133 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:34,147 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:34,175 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:34,288 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:34,301 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:34,330 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:34,445 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:34,458 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:34,485 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:34,602 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:34,615 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:34,643 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:34,750 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:34,762 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:34,791 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:34,900 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:34,913 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:34,940 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:35,051 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:35,064 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:35,178 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:35,210 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:35,218 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:35,326 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:35,359 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:35,366 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:35,472 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:35,482 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:35,514 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:35,620 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:35,620 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:35,662 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:35,777 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:35,778 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:35,819 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:35,927 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:35,928 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:35,969 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:36,077 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:36,077 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:36,117 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:36,221 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:36,222 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:36,263 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:36,371 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:36,373 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:36,415 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:36,520 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:36,522 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:36,563 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:36,670 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:36,671 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:36,712 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:36,815 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:36,835 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:36,876 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:36,965 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:36,985 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:37,028 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:37,118 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:37,139 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:37,179 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:37,260 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:37,283 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:37,323 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:37,408 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:37,429 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:37,469 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:37,554 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:37,577 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:37,616 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:37,702 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:37,727 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:37,765 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:37,825 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:37,877 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:37,916 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:37,973 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:38,024 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:38,065 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:38,155 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:38,177 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:38,217 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:38,303 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:38,328 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:38,366 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:38,456 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:38,478 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:38,518 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:38,583 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:38,637 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:38,676 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:38,744 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:38,797 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:38,838 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:38,931 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:38,954 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:38,996 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:39,085 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:39,111 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:39,228 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:39,230 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:39,271 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:39,379 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:39,379 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:39,421 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:39,527 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:39,528 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:39,570 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:39,672 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:39,692 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:39,731 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:39,789 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:39,827 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:39,863 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:39,866 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:39,974 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:40,006 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:40,014 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:40,096 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:40,160 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:40,164 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:40,277 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:40,312 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:40,317 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:40,422 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:40,455 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:40,464 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:40,592 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:40,608 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:40,631 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:40,745 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:40,758 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:40,785 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:40,904 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:40,907 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:41,015 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:41,048 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:41,056 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:41,161 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:41,194 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:41,201 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:41,309 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:41,341 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:41,358 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:41,482 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:41,496 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:41,523 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:41,642 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:41,657 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:41,681 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:41,793 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:41,807 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:41,888 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:41,952 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:41,960 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:42,068 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:42,103 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:42,110 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:42,214 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:42,249 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:42,256 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:42,331 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:42,392 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:42,398 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:42,476 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:42,537 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:42,543 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:42,649 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:42,682 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:42,689 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:42,797 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:42,829 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:42,842 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:42,951 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:42,954 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:42,994 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:43,096 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:43,096 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:43,138 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:43,243 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:43,245 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:43,287 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:43,391 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:43,393 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:43,434 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:43,539 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:43,542 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:43,582 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:43,663 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:43,663 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:43,731 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:43,837 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:43,838 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:43,879 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:43,986 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:43,988 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:44,029 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:44,139 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:44,139 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:44,181 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:44,261 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:44,292 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:44,332 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:44,437 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:44,439 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:44,480 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:44,586 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:44,588 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:44,629 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:44,742 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:44,744 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:44,785 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:44,869 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:44,902 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:44,944 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:45,018 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:45,053 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:45,095 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:45,197 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:45,199 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:45,240 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:45,346 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:45,346 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:45,391 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:45,521 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:45,542 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:45,581 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:45,638 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:45,691 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:45,730 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:45,788 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:45,840 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:45,940 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:45,971 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:46,011 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:46,122 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:46,122 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:46,163 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:46,266 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:46,268 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:46,310 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:46,415 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:46,418 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:46,460 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:46,564 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:46,564 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:46,606 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:46,715 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:46,717 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:46,758 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:46,835 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:46,837 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:46,906 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:46,908 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:47,015 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:47,050 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:47,058 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:47,169 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:47,203 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:47,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:47,322 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:47,357 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:47,363 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:47,447 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:47,513 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:47,516 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:47,621 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:47,656 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:47,662 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:47,769 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:47,803 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:47,811 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:47,921 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:47,930 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:47,961 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:48,039 - INFO - End of video file reached
2025-11-24 18:15:48,068 - INFO - Video capture loop ended
2025-11-24 18:15:48,069 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:48,214 - INFO - Video thread started with source: assets/temp_videos/Screen Recording 2025-11-24 at 5.55.42 PM.mov
2025-11-24 18:15:48,214 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:48,226 - INFO - ✓ Video file opened: assets/temp_videos/Screen Recording 2025-11-24 at 5.55.42 PM.mov
2025-11-24 18:15:48,250 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:48,273 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:48,339 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:48,340 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:48,394 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:48,417 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:48,513 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:48,514 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:48,535 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:48,560 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:48,657 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:48,660 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:48,680 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:48,700 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:48,778 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:48,807 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:48,828 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:48,848 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:48,922 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:48,923 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:48,958 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:48,979 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:48,995 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:48,999 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:49,076 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:49,127 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:49,142 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:49,148 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:49,168 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:49,255 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:49,277 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:49,288 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:49,299 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:49,376 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:49,428 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:49,442 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:49,448 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:49,468 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:49,555 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:49,577 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:49,591 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:49,598 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:49,672 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:49,706 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:49,728 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:49,739 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:49,749 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:49,833 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:49,866 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:49,889 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:49,898 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:49,911 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:49,984 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,033 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,048 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,053 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,074 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,168 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,192 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,202 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,215 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,323 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,344 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,356 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,365 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,386 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,474 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,494 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,506 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,514 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,533 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,622 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,644 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,659 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,664 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,684 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,774 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,794 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,809 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,815 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,836 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,929 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,931 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,949 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,969 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:50,991 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:51,079 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:51,081 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:51,103 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:51,127 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:51,226 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:51,226 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:51,248 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:51,267 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:51,346 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:51,348 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:51,397 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:51,419 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:51,440 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:51,495 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:51,527 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:51,548 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:51,568 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:51,649 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:51,681 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:51,683 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:51,705 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:51,727 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:51,806 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:51,806 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:51,858 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:51,878 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:51,898 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:51,954 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:51,987 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,010 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,031 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,052 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,107 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,140 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,161 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,182 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,183 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,254 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,304 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,320 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,327 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,347 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,435 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,459 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,470 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,480 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,582 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,603 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,618 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,625 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,645 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,733 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,756 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,769 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,778 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,798 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,886 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,909 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,921 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:52,929 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,005 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,054 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,069 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,075 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,096 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,199 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,216 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,220 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,242 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,330 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,350 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,363 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,372 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,392 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,476 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,497 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,511 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,518 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,540 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,647 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,662 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,667 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,689 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,772 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,793 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,807 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,814 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,891 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,924 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,933 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,946 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,965 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:53,986 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,106 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,110 - INFO - Video thread started with source: Camera
2025-11-24 18:15:54,112 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,112 - ERROR - ❌ No camera found!
2025-11-24 18:15:54,133 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,156 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,177 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,241 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,241 - INFO - Video thread started with source: Camera
2025-11-24 18:15:54,242 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,243 - ERROR - ❌ No camera found!
2025-11-24 18:15:54,264 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,284 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,306 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,365 - INFO - Video thread started with source: Camera
2025-11-24 18:15:54,366 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,367 - ERROR - ❌ No camera found!
2025-11-24 18:15:54,382 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,403 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,426 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,486 - INFO - Video thread started with source: Camera
2025-11-24 18:15:54,488 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,488 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,488 - ERROR - ❌ No camera found!
2025-11-24 18:15:54,509 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,530 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,550 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,615 - INFO - Video thread started with source: Camera
2025-11-24 18:15:54,616 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,617 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,617 - ERROR - ❌ No camera found!
2025-11-24 18:15:54,640 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,662 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,682 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,743 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,745 - INFO - Video thread started with source: Camera
2025-11-24 18:15:54,745 - ERROR - ❌ No camera found!
2025-11-24 18:15:54,763 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,783 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,806 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,870 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,870 - INFO - Video thread started with source: Camera
2025-11-24 18:15:54,871 - ERROR - ❌ No camera found!
2025-11-24 18:15:54,872 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,895 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,916 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:54,936 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,000 - INFO - Video thread started with source: Camera
2025-11-24 18:15:55,002 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,003 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,003 - ERROR - ❌ No camera found!
2025-11-24 18:15:55,025 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,047 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,066 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,129 - INFO - Video thread started with source: Camera
2025-11-24 18:15:55,130 - ERROR - ❌ No camera found!
2025-11-24 18:15:55,130 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,146 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,167 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,188 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,253 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,254 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,255 - INFO - Video thread started with source: Camera
2025-11-24 18:15:55,256 - ERROR - ❌ No camera found!
2025-11-24 18:15:55,276 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,297 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,317 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,379 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,381 - INFO - Video thread started with source: Camera
2025-11-24 18:15:55,382 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,383 - ERROR - ❌ No camera found!
2025-11-24 18:15:55,404 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,426 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,447 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,511 - INFO - Video thread started with source: Camera
2025-11-24 18:15:55,512 - ERROR - ❌ No camera found!
2025-11-24 18:15:55,512 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,528 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,548 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,569 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,637 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,639 - INFO - Video thread started with source: Camera
2025-11-24 18:15:55,641 - ERROR - ❌ No camera found!
2025-11-24 18:15:55,641 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,663 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,686 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,796 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,797 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,797 - INFO - Video thread started with source: Camera
2025-11-24 18:15:55,798 - ERROR - ❌ No camera found!
2025-11-24 18:15:55,818 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,841 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,919 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,922 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,923 - INFO - Video thread started with source: Camera
2025-11-24 18:15:55,924 - ERROR - ❌ No camera found!
2025-11-24 18:15:55,943 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,964 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:55,984 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,049 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,050 - INFO - Video thread started with source: Camera
2025-11-24 18:15:56,051 - ERROR - ❌ No camera found!
2025-11-24 18:15:56,052 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,074 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,096 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,116 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,180 - INFO - Video thread started with source: Camera
2025-11-24 18:15:56,182 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,182 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,182 - ERROR - ❌ No camera found!
2025-11-24 18:15:56,203 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,226 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,301 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,305 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,306 - INFO - Video thread started with source: Camera
2025-11-24 18:15:56,306 - ERROR - ❌ No camera found!
2025-11-24 18:15:56,327 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,348 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,369 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,433 - INFO - Video thread started with source: Camera
2025-11-24 18:15:56,433 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,434 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,435 - ERROR - ❌ No camera found!
2025-11-24 18:15:56,457 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,478 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,498 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,558 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,560 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,560 - INFO - Video thread started with source: Camera
2025-11-24 18:15:56,561 - ERROR - ❌ No camera found!
2025-11-24 18:15:56,581 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,601 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,623 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,680 - INFO - Video thread started with source: Camera
2025-11-24 18:15:56,682 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,682 - ERROR - ❌ No camera found!
2025-11-24 18:15:56,682 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,703 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,725 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,798 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,801 - INFO - Video thread started with source: Camera
2025-11-24 18:15:56,802 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,803 - ERROR - ❌ No camera found!
2025-11-24 18:15:56,823 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,845 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,866 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,931 - INFO - Video thread started with source: Camera
2025-11-24 18:15:56,932 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,933 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:56,934 - ERROR - ❌ No camera found!
2025-11-24 18:15:56,956 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,021 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,042 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,054 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,062 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,083 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,104 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,124 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,126 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,145 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,166 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,188 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,193 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,209 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,229 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,249 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,263 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,270 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,292 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,313 - INFO - Video thread started with source: Camera
2025-11-24 18:15:57,315 - ERROR - ❌ No camera found!
2025-11-24 18:15:57,317 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,333 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,340 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,416 - INFO - Video thread started with source: Camera
2025-11-24 18:15:57,418 - ERROR - ❌ No camera found!
2025-11-24 18:15:57,422 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,445 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,453 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,518 - INFO - Video thread started with source: Camera
2025-11-24 18:15:57,519 - ERROR - ❌ No camera found!
2025-11-24 18:15:57,521 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,543 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,554 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,620 - INFO - Video thread started with source: Camera
2025-11-24 18:15:57,622 - ERROR - ❌ No camera found!
2025-11-24 18:15:57,624 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,645 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,657 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,718 - INFO - Video thread started with source: Camera
2025-11-24 18:15:57,719 - ERROR - ❌ No camera found!
2025-11-24 18:15:57,722 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,745 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,755 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,827 - INFO - Video thread started with source: Camera
2025-11-24 18:15:57,828 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,828 - ERROR - ❌ No camera found!
2025-11-24 18:15:57,853 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,862 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,927 - INFO - Video thread started with source: Camera
2025-11-24 18:15:57,929 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,929 - ERROR - ❌ No camera found!
2025-11-24 18:15:57,950 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:57,962 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:58,028 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:58,028 - INFO - Video thread started with source: Camera
2025-11-24 18:15:58,029 - ERROR - ❌ No camera found!
2025-11-24 18:15:58,050 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:58,063 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:58,131 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:58,131 - INFO - Video thread started with source: Camera
2025-11-24 18:15:58,132 - ERROR - ❌ No camera found!
2025-11-24 18:15:58,152 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:58,165 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:58,231 - INFO - Video thread started with source: Camera
2025-11-24 18:15:58,232 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:58,232 - ERROR - ❌ No camera found!
2025-11-24 18:15:58,256 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:58,267 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:58,331 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:58,331 - INFO - Video thread started with source: Camera
2025-11-24 18:15:58,332 - ERROR - ❌ No camera found!
2025-11-24 18:15:58,353 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:58,367 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:58,431 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:58,432 - INFO - Video thread started with source: Camera
2025-11-24 18:15:58,435 - ERROR - ❌ No camera found!
2025-11-24 18:15:58,453 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:58,467 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:58,530 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:58,530 - INFO - Video thread started with source: Camera
2025-11-24 18:15:58,531 - ERROR - ❌ No camera found!
2025-11-24 18:15:58,550 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:58,564 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:58,624 - INFO - Video thread started with source: Camera
2025-11-24 18:15:58,625 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:58,626 - ERROR - ❌ No camera found!
2025-11-24 18:15:58,646 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:58,658 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:58,724 - INFO - Video thread started with source: Camera
2025-11-24 18:15:58,726 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:58,726 - ERROR - ❌ No camera found!
2025-11-24 18:15:58,746 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:58,760 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:58,822 - INFO - Video thread started with source: Camera
2025-11-24 18:15:58,823 - ERROR - ❌ No camera found!
2025-11-24 18:15:58,825 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:58,845 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:58,859 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:58,923 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:58,923 - INFO - Video thread started with source: Camera
2025-11-24 18:15:58,924 - ERROR - ❌ No camera found!
2025-11-24 18:15:58,945 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:58,955 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,020 - INFO - Video thread started with source: Camera
2025-11-24 18:15:59,022 - ERROR - ❌ No camera found!
2025-11-24 18:15:59,023 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,044 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,056 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,119 - INFO - Video thread started with source: Camera
2025-11-24 18:15:59,121 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,121 - ERROR - ❌ No camera found!
2025-11-24 18:15:59,144 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,154 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,222 - INFO - Video thread started with source: Camera
2025-11-24 18:15:59,222 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,223 - ERROR - ❌ No camera found!
2025-11-24 18:15:59,245 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,254 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,322 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,322 - INFO - Video thread started with source: Camera
2025-11-24 18:15:59,324 - ERROR - ❌ No camera found!
2025-11-24 18:15:59,344 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,358 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,414 - INFO - Video thread started with source: Camera
2025-11-24 18:15:59,415 - ERROR - ❌ No camera found!
2025-11-24 18:15:59,416 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,438 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,448 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,508 - INFO - Video thread started with source: Camera
2025-11-24 18:15:59,509 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,510 - ERROR - ❌ No camera found!
2025-11-24 18:15:59,531 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,542 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,601 - INFO - Video thread started with source: Camera
2025-11-24 18:15:59,602 - ERROR - ❌ No camera found!
2025-11-24 18:15:59,603 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,625 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,638 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,693 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,695 - INFO - Video thread started with source: Camera
2025-11-24 18:15:59,696 - ERROR - ❌ No camera found!
2025-11-24 18:15:59,715 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,731 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,790 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,790 - INFO - Video thread started with source: Camera
2025-11-24 18:15:59,791 - ERROR - ❌ No camera found!
2025-11-24 18:15:59,811 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,880 - INFO - Video thread started with source: Camera
2025-11-24 18:15:59,880 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,882 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,882 - ERROR - ❌ No camera found!
2025-11-24 18:15:59,904 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,973 - INFO - Video thread started with source: Camera
2025-11-24 18:15:59,974 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,975 - ERROR - ❌ No camera found!
2025-11-24 18:15:59,975 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:15:59,996 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:00,064 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:00,066 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:00,066 - INFO - Video thread started with source: Camera
2025-11-24 18:16:00,068 - ERROR - ❌ No camera found!
2025-11-24 18:16:00,087 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:00,157 - INFO - Video thread started with source: Camera
2025-11-24 18:16:00,157 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:00,159 - ERROR - ❌ No camera found!
2025-11-24 18:16:00,159 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:00,180 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:00,249 - INFO - Video thread started with source: Camera
2025-11-24 18:16:00,249 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:00,249 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:00,250 - ERROR - ❌ No camera found!
2025-11-24 18:16:00,272 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:00,341 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:00,342 - INFO - Video thread started with source: Camera
2025-11-24 18:16:00,343 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:00,344 - ERROR - ❌ No camera found!
2025-11-24 18:16:00,364 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:00,439 - INFO - Video thread started with source: Camera
2025-11-24 18:16:00,440 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:00,440 - ERROR - ❌ No camera found!
2025-11-24 18:16:00,441 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:00,462 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:00,535 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:00,536 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:00,538 - INFO - Video thread started with source: Camera
2025-11-24 18:16:00,540 - ERROR - ❌ No camera found!
2025-11-24 18:16:00,560 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:00,633 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:00,633 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:00,634 - INFO - Video thread started with source: Camera
2025-11-24 18:16:00,635 - ERROR - ❌ No camera found!
2025-11-24 18:16:00,655 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:00,731 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:00,733 - INFO - Video thread started with source: Camera
2025-11-24 18:16:00,733 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:00,734 - ERROR - ❌ No camera found!
2025-11-24 18:16:00,752 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:00,825 - INFO - Video thread started with source: Camera
2025-11-24 18:16:00,826 - ERROR - ❌ No camera found!
2025-11-24 18:16:00,827 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:00,828 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:00,850 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:00,917 - INFO - Video thread started with source: Camera
2025-11-24 18:16:00,919 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:00,919 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:00,919 - ERROR - ❌ No camera found!
2025-11-24 18:16:00,941 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,009 - INFO - Video thread started with source: Camera
2025-11-24 18:16:01,010 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,010 - ERROR - ❌ No camera found!
2025-11-24 18:16:01,012 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,032 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,100 - INFO - Video thread started with source: Camera
2025-11-24 18:16:01,102 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,102 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,102 - ERROR - ❌ No camera found!
2025-11-24 18:16:01,123 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,190 - INFO - Video thread started with source: Camera
2025-11-24 18:16:01,190 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,191 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,192 - ERROR - ❌ No camera found!
2025-11-24 18:16:01,214 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,286 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,286 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,286 - INFO - Video thread started with source: Camera
2025-11-24 18:16:01,288 - ERROR - ❌ No camera found!
2025-11-24 18:16:01,307 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,377 - INFO - Video thread started with source: Camera
2025-11-24 18:16:01,377 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,378 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,378 - ERROR - ❌ No camera found!
2025-11-24 18:16:01,399 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,469 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,471 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,471 - INFO - Video thread started with source: Camera
2025-11-24 18:16:01,472 - ERROR - ❌ No camera found!
2025-11-24 18:16:01,492 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,559 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,561 - INFO - Video thread started with source: Camera
2025-11-24 18:16:01,562 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,562 - ERROR - ❌ No camera found!
2025-11-24 18:16:01,582 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,653 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,653 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,653 - INFO - Video thread started with source: Camera
2025-11-24 18:16:01,654 - ERROR - ❌ No camera found!
2025-11-24 18:16:01,675 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,742 - INFO - Video thread started with source: Camera
2025-11-24 18:16:01,743 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,744 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,744 - ERROR - ❌ No camera found!
2025-11-24 18:16:01,766 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,833 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,834 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,834 - INFO - Video thread started with source: Camera
2025-11-24 18:16:01,835 - ERROR - ❌ No camera found!
2025-11-24 18:16:01,856 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,926 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,927 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:01,929 - INFO - Video thread started with source: Camera
2025-11-24 18:16:01,930 - ERROR - ❌ No camera found!
2025-11-24 18:16:01,949 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,019 - INFO - Video thread started with source: Camera
2025-11-24 18:16:02,019 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,020 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,020 - ERROR - ❌ No camera found!
2025-11-24 18:16:02,043 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,109 - INFO - Video thread started with source: Camera
2025-11-24 18:16:02,110 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,110 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,111 - ERROR - ❌ No camera found!
2025-11-24 18:16:02,132 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,201 - INFO - Video thread started with source: Camera
2025-11-24 18:16:02,201 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,202 - ERROR - ❌ No camera found!
2025-11-24 18:16:02,224 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,232 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,299 - INFO - Video thread started with source: Camera
2025-11-24 18:16:02,300 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,301 - ERROR - ❌ No camera found!
2025-11-24 18:16:02,323 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,336 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,399 - INFO - Video thread started with source: Camera
2025-11-24 18:16:02,401 - ERROR - ❌ No camera found!
2025-11-24 18:16:02,401 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,423 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,435 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,498 - INFO - Video thread started with source: Camera
2025-11-24 18:16:02,499 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,500 - ERROR - ❌ No camera found!
2025-11-24 18:16:02,521 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,534 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,592 - INFO - Video thread started with source: Camera
2025-11-24 18:16:02,592 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,593 - ERROR - ❌ No camera found!
2025-11-24 18:16:02,613 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,627 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,689 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,689 - INFO - Video thread started with source: Camera
2025-11-24 18:16:02,691 - ERROR - ❌ No camera found!
2025-11-24 18:16:02,710 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,722 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,783 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,783 - INFO - Video thread started with source: Camera
2025-11-24 18:16:02,784 - ERROR - ❌ No camera found!
2025-11-24 18:16:02,803 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,817 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,873 - INFO - Video thread started with source: Camera
2025-11-24 18:16:02,875 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,875 - ERROR - ❌ No camera found!
2025-11-24 18:16:02,897 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,910 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,968 - INFO - Video thread started with source: Camera
2025-11-24 18:16:02,969 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:02,970 - ERROR - ❌ No camera found!
2025-11-24 18:16:02,992 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,005 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,060 - INFO - Video thread started with source: Camera
2025-11-24 18:16:03,061 - ERROR - ❌ No camera found!
2025-11-24 18:16:03,062 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,083 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,095 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,152 - INFO - Video thread started with source: Camera
2025-11-24 18:16:03,153 - ERROR - ❌ No camera found!
2025-11-24 18:16:03,155 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,177 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,188 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,244 - INFO - Video thread started with source: Camera
2025-11-24 18:16:03,245 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,246 - ERROR - ❌ No camera found!
2025-11-24 18:16:03,265 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,279 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,335 - INFO - Video thread started with source: Camera
2025-11-24 18:16:03,337 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,337 - ERROR - ❌ No camera found!
2025-11-24 18:16:03,359 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,370 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,427 - INFO - Video thread started with source: Camera
2025-11-24 18:16:03,428 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,428 - ERROR - ❌ No camera found!
2025-11-24 18:16:03,449 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,462 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,520 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,520 - INFO - Video thread started with source: Camera
2025-11-24 18:16:03,521 - ERROR - ❌ No camera found!
2025-11-24 18:16:03,541 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,555 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,610 - INFO - Video thread started with source: Camera
2025-11-24 18:16:03,612 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,612 - ERROR - ❌ No camera found!
2025-11-24 18:16:03,633 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,645 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,701 - INFO - Video thread started with source: Camera
2025-11-24 18:16:03,702 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,703 - ERROR - ❌ No camera found!
2025-11-24 18:16:03,725 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,738 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,793 - INFO - Video thread started with source: Camera
2025-11-24 18:16:03,794 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,794 - ERROR - ❌ No camera found!
2025-11-24 18:16:03,816 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,829 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,888 - INFO - Video thread started with source: Camera
2025-11-24 18:16:03,890 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,890 - ERROR - ❌ No camera found!
2025-11-24 18:16:03,912 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,926 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,980 - INFO - Video thread started with source: Camera
2025-11-24 18:16:03,982 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:03,982 - ERROR - ❌ No camera found!
2025-11-24 18:16:04,004 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:04,101 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:04,105 - INFO - Video thread started with source: Camera
2025-11-24 18:16:04,106 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:04,107 - ERROR - ❌ No camera found!
2025-11-24 18:16:04,128 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:04,195 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:04,195 - INFO - Video thread started with source: Camera
2025-11-24 18:16:04,196 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:04,197 - ERROR - ❌ No camera found!
2025-11-24 18:16:04,216 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:04,289 - INFO - Video thread started with source: Camera
2025-11-24 18:16:04,289 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:04,290 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:04,291 - ERROR - ❌ No camera found!
2025-11-24 18:16:04,312 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:04,378 - INFO - Video thread started with source: Camera
2025-11-24 18:16:04,378 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:04,380 - ERROR - ❌ No camera found!
2025-11-24 18:16:04,380 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:04,402 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:04,471 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:04,471 - INFO - Video thread started with source: Camera
2025-11-24 18:16:04,473 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:04,473 - ERROR - ❌ No camera found!
2025-11-24 18:16:04,495 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:04,569 - INFO - Video thread started with source: Camera
2025-11-24 18:16:04,569 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:04,570 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:04,571 - ERROR - ❌ No camera found!
2025-11-24 18:16:04,593 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:04,658 - INFO - Video thread started with source: Camera
2025-11-24 18:16:04,659 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:04,660 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:04,660 - ERROR - ❌ No camera found!
2025-11-24 18:16:04,682 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:04,755 - INFO - Video thread started with source: Camera
2025-11-24 18:16:04,756 - ERROR - ❌ No camera found!
2025-11-24 18:16:04,758 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:04,758 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:04,780 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:04,856 - INFO - Video thread started with source: Camera
2025-11-24 18:16:04,858 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:04,858 - ERROR - ❌ No camera found!
2025-11-24 18:16:04,879 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:04,890 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:04,957 - INFO - Video thread started with source: Camera
2025-11-24 18:16:04,959 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:04,959 - ERROR - ❌ No camera found!
2025-11-24 18:16:04,981 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:04,992 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:05,053 - INFO - Video thread started with source: Camera
2025-11-24 18:16:05,053 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:05,054 - ERROR - ❌ No camera found!
2025-11-24 18:16:05,077 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:05,088 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:05,148 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:05,149 - INFO - Video thread started with source: Camera
2025-11-24 18:16:05,150 - ERROR - ❌ No camera found!
2025-11-24 18:16:05,169 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:05,183 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:05,243 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:05,243 - INFO - Video thread started with source: Camera
2025-11-24 18:16:05,244 - ERROR - ❌ No camera found!
2025-11-24 18:16:05,265 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:05,277 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:05,336 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:05,336 - INFO - Video thread started with source: Camera
2025-11-24 18:16:05,338 - ERROR - ❌ No camera found!
2025-11-24 18:16:05,358 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:05,372 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:05,433 - INFO - Video thread started with source: Camera
2025-11-24 18:16:05,435 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:05,435 - ERROR - ❌ No camera found!
2025-11-24 18:16:05,457 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:05,468 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:05,530 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:05,530 - INFO - Video thread started with source: Camera
2025-11-24 18:16:05,532 - ERROR - ❌ No camera found!
2025-11-24 18:16:05,550 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:05,563 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:05,627 - INFO - Video thread started with source: Camera
2025-11-24 18:16:05,628 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:05,629 - ERROR - ❌ No camera found!
2025-11-24 18:16:05,652 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:05,662 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:05,727 - INFO - Video thread started with source: Camera
2025-11-24 18:16:05,728 - ERROR - ❌ No camera found!
2025-11-24 18:16:05,730 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:05,752 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:05,763 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:05,823 - INFO - Video thread started with source: Camera
2025-11-24 18:16:05,825 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:05,825 - ERROR - ❌ No camera found!
2025-11-24 18:16:05,847 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:05,858 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:05,918 - INFO - Video thread started with source: Camera
2025-11-24 18:16:05,920 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:05,920 - ERROR - ❌ No camera found!
2025-11-24 18:16:05,942 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:05,953 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,012 - INFO - Video thread started with source: Camera
2025-11-24 18:16:06,014 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,014 - ERROR - ❌ No camera found!
2025-11-24 18:16:06,036 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,048 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,106 - INFO - Video thread started with source: Camera
2025-11-24 18:16:06,107 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,107 - ERROR - ❌ No camera found!
2025-11-24 18:16:06,129 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,142 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,203 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,203 - INFO - Video thread started with source: Camera
2025-11-24 18:16:06,205 - ERROR - ❌ No camera found!
2025-11-24 18:16:06,225 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,236 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,297 - INFO - Video thread started with source: Camera
2025-11-24 18:16:06,298 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,299 - ERROR - ❌ No camera found!
2025-11-24 18:16:06,319 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,332 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,388 - INFO - Video thread started with source: Camera
2025-11-24 18:16:06,389 - ERROR - ❌ No camera found!
2025-11-24 18:16:06,391 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,413 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,424 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,480 - INFO - Video thread started with source: Camera
2025-11-24 18:16:06,481 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,481 - ERROR - ❌ No camera found!
2025-11-24 18:16:06,502 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,515 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,576 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,577 - INFO - Video thread started with source: Camera
2025-11-24 18:16:06,578 - ERROR - ❌ No camera found!
2025-11-24 18:16:06,598 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,612 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,669 - INFO - Video thread started with source: Camera
2025-11-24 18:16:06,672 - ERROR - ❌ No camera found!
2025-11-24 18:16:06,672 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,694 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,705 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,764 - INFO - Video thread started with source: Camera
2025-11-24 18:16:06,765 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,766 - ERROR - ❌ No camera found!
2025-11-24 18:16:06,786 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,798 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,858 - INFO - Video thread started with source: Camera
2025-11-24 18:16:06,859 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,860 - ERROR - ❌ No camera found!
2025-11-24 18:16:06,881 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,894 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,950 - INFO - Video thread started with source: Camera
2025-11-24 18:16:06,952 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,953 - ERROR - ❌ No camera found!
2025-11-24 18:16:06,974 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:06,987 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:07,045 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:07,045 - INFO - Video thread started with source: Camera
2025-11-24 18:16:07,047 - ERROR - ❌ No camera found!
2025-11-24 18:16:07,066 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:07,080 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:07,139 - INFO - Video thread started with source: Camera
2025-11-24 18:16:07,140 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:07,141 - ERROR - ❌ No camera found!
2025-11-24 18:16:07,161 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:07,176 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:07,234 - INFO - Video thread started with source: Camera
2025-11-24 18:16:07,234 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:07,235 - ERROR - ❌ No camera found!
2025-11-24 18:16:07,257 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:07,269 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:07,329 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:07,329 - INFO - Video thread started with source: Camera
2025-11-24 18:16:07,330 - ERROR - ❌ No camera found!
2025-11-24 18:16:07,349 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:07,362 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:07,423 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:07,423 - INFO - Video thread started with source: Camera
2025-11-24 18:16:07,425 - ERROR - ❌ No camera found!
2025-11-24 18:16:07,444 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:07,454 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:07,532 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:07,535 - INFO - Video thread started with source: Camera
2025-11-24 18:16:07,537 - ERROR - ❌ No camera found!
2025-11-24 18:16:07,555 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:07,569 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:07,638 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:07,638 - INFO - Video thread started with source: Camera
2025-11-24 18:16:07,639 - ERROR - ❌ No camera found!
2025-11-24 18:16:07,660 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:07,670 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:07,742 - INFO - Video thread started with source: Camera
2025-11-24 18:16:07,743 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:07,744 - ERROR - ❌ No camera found!
2025-11-24 18:16:07,766 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:07,779 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:07,849 - INFO - Video thread started with source: Camera
2025-11-24 18:16:07,849 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:07,850 - ERROR - ❌ No camera found!
2025-11-24 18:16:07,872 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:07,880 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:07,953 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:07,953 - INFO - Video thread started with source: Camera
2025-11-24 18:16:07,954 - ERROR - ❌ No camera found!
2025-11-24 18:16:07,975 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:07,986 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:08,050 - INFO - Video thread started with source: Camera
2025-11-24 18:16:08,052 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:08,053 - ERROR - ❌ No camera found!
2025-11-24 18:16:08,075 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:08,087 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:08,151 - INFO - Video thread started with source: Camera
2025-11-24 18:16:08,153 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:08,154 - ERROR - ❌ No camera found!
2025-11-24 18:16:08,175 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:08,187 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:08,252 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:08,252 - INFO - Video thread started with source: Camera
2025-11-24 18:16:08,253 - ERROR - ❌ No camera found!
2025-11-24 18:16:08,275 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:08,289 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:08,352 - INFO - Video thread started with source: Camera
2025-11-24 18:16:08,352 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:08,353 - ERROR - ❌ No camera found!
2025-11-24 18:16:08,376 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:08,387 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:08,443 - INFO - Video thread started with source: Camera
2025-11-24 18:16:08,444 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:08,445 - ERROR - ❌ No camera found!
2025-11-24 18:16:08,465 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:08,477 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:08,540 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:08,540 - INFO - Video thread started with source: Camera
2025-11-24 18:16:08,541 - ERROR - ❌ No camera found!
2025-11-24 18:16:08,561 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:08,575 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:08,630 - INFO - Video thread started with source: Camera
2025-11-24 18:16:08,631 - ERROR - ❌ No camera found!
2025-11-24 18:16:08,633 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:08,655 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:08,669 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:08,731 - INFO - Video thread started with source: Camera
2025-11-24 18:16:08,733 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:08,733 - ERROR - ❌ No camera found!
2025-11-24 18:16:08,755 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:08,766 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:08,895 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:08,897 - INFO - Video thread started with source: Camera
2025-11-24 18:16:08,898 - ERROR - ❌ No camera found!
2025-11-24 18:16:08,917 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:08,929 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:08,995 - INFO - Video thread started with source: Camera
2025-11-24 18:16:08,997 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:08,997 - ERROR - ❌ No camera found!
2025-11-24 18:16:09,017 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:09,030 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:09,094 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:09,095 - INFO - Video thread started with source: Camera
2025-11-24 18:16:09,097 - ERROR - ❌ No camera found!
2025-11-24 18:16:09,116 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:09,128 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:09,192 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:09,192 - INFO - Video thread started with source: Camera
2025-11-24 18:16:09,194 - ERROR - ❌ No camera found!
2025-11-24 18:16:09,213 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:09,226 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:09,291 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:09,291 - INFO - Video thread started with source: Camera
2025-11-24 18:16:09,292 - ERROR - ❌ No camera found!
2025-11-24 18:16:09,312 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:09,326 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:09,385 - INFO - Video thread started with source: Camera
2025-11-24 18:16:09,386 - ERROR - ❌ No camera found!
2025-11-24 18:16:09,389 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:09,410 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:09,422 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:09,482 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:09,484 - INFO - Video thread started with source: Camera
2025-11-24 18:16:09,485 - ERROR - ❌ No camera found!
2025-11-24 18:16:09,505 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:09,518 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:09,583 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:09,583 - INFO - Video thread started with source: Camera
2025-11-24 18:16:09,584 - ERROR - ❌ No camera found!
2025-11-24 18:16:09,606 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:09,617 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:09,677 - INFO - Video thread started with source: Camera
2025-11-24 18:16:09,677 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:09,678 - ERROR - ❌ No camera found!
2025-11-24 18:16:09,699 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:09,713 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:09,778 - INFO - Video thread started with source: Camera
2025-11-24 18:16:09,779 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:09,779 - ERROR - ❌ No camera found!
2025-11-24 18:16:09,800 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:09,812 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:09,878 - INFO - Video thread started with source: Camera
2025-11-24 18:16:09,880 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:09,880 - ERROR - ❌ No camera found!
2025-11-24 18:16:09,901 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:09,912 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:09,978 - INFO - Video thread started with source: Camera
2025-11-24 18:16:09,980 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:09,980 - ERROR - ❌ No camera found!
2025-11-24 18:16:10,000 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,013 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,070 - INFO - Video thread started with source: Camera
2025-11-24 18:16:10,070 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,071 - ERROR - ❌ No camera found!
2025-11-24 18:16:10,093 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,106 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,163 - INFO - Video thread started with source: Camera
2025-11-24 18:16:10,163 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,164 - ERROR - ❌ No camera found!
2025-11-24 18:16:10,186 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,197 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,254 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,254 - INFO - Video thread started with source: Camera
2025-11-24 18:16:10,258 - ERROR - ❌ No camera found!
2025-11-24 18:16:10,277 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,289 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,346 - INFO - Video thread started with source: Camera
2025-11-24 18:16:10,347 - ERROR - ❌ No camera found!
2025-11-24 18:16:10,348 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,370 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,381 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,449 - INFO - Video thread started with source: Camera
2025-11-24 18:16:10,451 - ERROR - ❌ No camera found!
2025-11-24 18:16:10,451 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,474 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,485 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,549 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,551 - INFO - Video thread started with source: Camera
2025-11-24 18:16:10,552 - ERROR - ❌ No camera found!
2025-11-24 18:16:10,571 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,584 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,649 - INFO - Video thread started with source: Camera
2025-11-24 18:16:10,650 - ERROR - ❌ No camera found!
2025-11-24 18:16:10,654 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,676 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,685 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,740 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,743 - INFO - Video thread started with source: Camera
2025-11-24 18:16:10,745 - ERROR - ❌ No camera found!
2025-11-24 18:16:10,762 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,777 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,782 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,838 - INFO - Video thread started with source: Camera
2025-11-24 18:16:10,839 - ERROR - ❌ No camera found!
2025-11-24 18:16:10,854 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,872 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,931 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,933 - INFO - Video thread started with source: Camera
2025-11-24 18:16:10,934 - ERROR - ❌ No camera found!
2025-11-24 18:16:10,954 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:10,969 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,024 - INFO - Video thread started with source: Camera
2025-11-24 18:16:11,026 - ERROR - ❌ No camera found!
2025-11-24 18:16:11,027 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,049 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,062 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,119 - INFO - Video thread started with source: Camera
2025-11-24 18:16:11,121 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,121 - ERROR - ❌ No camera found!
2025-11-24 18:16:11,143 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,157 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,217 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,219 - INFO - Video thread started with source: Camera
2025-11-24 18:16:11,220 - ERROR - ❌ No camera found!
2025-11-24 18:16:11,240 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,315 - INFO - Video thread started with source: Camera
2025-11-24 18:16:11,316 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,317 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,317 - ERROR - ❌ No camera found!
2025-11-24 18:16:11,341 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,411 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,411 - INFO - Video thread started with source: Camera
2025-11-24 18:16:11,412 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,413 - ERROR - ❌ No camera found!
2025-11-24 18:16:11,433 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,505 - INFO - Video thread started with source: Camera
2025-11-24 18:16:11,506 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,507 - ERROR - ❌ No camera found!
2025-11-24 18:16:11,509 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,530 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,597 - INFO - Video thread started with source: Camera
2025-11-24 18:16:11,598 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,598 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,600 - ERROR - ❌ No camera found!
2025-11-24 18:16:11,620 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,687 - INFO - Video thread started with source: Camera
2025-11-24 18:16:11,689 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,689 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,689 - ERROR - ❌ No camera found!
2025-11-24 18:16:11,710 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,779 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,780 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,781 - INFO - Video thread started with source: Camera
2025-11-24 18:16:11,782 - ERROR - ❌ No camera found!
2025-11-24 18:16:11,800 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,880 - INFO - Video thread started with source: Camera
2025-11-24 18:16:11,881 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,882 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,882 - ERROR - ❌ No camera found!
2025-11-24 18:16:11,903 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,978 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,982 - INFO - Video thread started with source: Camera
2025-11-24 18:16:11,982 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:11,983 - ERROR - ❌ No camera found!
2025-11-24 18:16:12,004 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:12,081 - INFO - Video thread started with source: Camera
2025-11-24 18:16:12,083 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:12,083 - ERROR - ❌ No camera found!
2025-11-24 18:16:12,086 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:12,106 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:12,174 - INFO - Video thread started with source: Camera
2025-11-24 18:16:12,175 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:12,176 - ERROR - ❌ No camera found!
2025-11-24 18:16:12,197 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:12,211 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:12,268 - INFO - Video thread started with source: Camera
2025-11-24 18:16:12,269 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:12,270 - ERROR - ❌ No camera found!
2025-11-24 18:16:12,290 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:12,303 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:12,388 - INFO - Video thread started with source: Camera
2025-11-24 18:16:12,389 - ERROR - ❌ No camera found!
2025-11-24 18:16:12,392 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:12,414 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:12,424 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:12,495 - INFO - Video thread started with source: Camera
2025-11-24 18:16:12,497 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:12,497 - ERROR - ❌ No camera found!
2025-11-24 18:16:12,517 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:12,531 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:12,594 - INFO - Video thread started with source: Camera
2025-11-24 18:16:12,596 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:12,596 - ERROR - ❌ No camera found!
2025-11-24 18:16:12,616 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:12,629 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:12,687 - INFO - Video thread started with source: Camera
2025-11-24 18:16:12,689 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:12,689 - ERROR - ❌ No camera found!
2025-11-24 18:16:12,711 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:12,723 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:12,783 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:12,783 - INFO - Video thread started with source: Camera
2025-11-24 18:16:12,785 - ERROR - ❌ No camera found!
2025-11-24 18:16:12,804 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:12,818 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:12,878 - INFO - Video thread started with source: Camera
2025-11-24 18:16:12,880 - ERROR - ❌ No camera found!
2025-11-24 18:16:12,880 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:12,900 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:12,913 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:12,972 - INFO - Video thread started with source: Camera
2025-11-24 18:16:12,974 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:12,974 - ERROR - ❌ No camera found!
2025-11-24 18:16:12,994 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,007 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,080 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,080 - INFO - Video thread started with source: Camera
2025-11-24 18:16:13,082 - ERROR - ❌ No camera found!
2025-11-24 18:16:13,101 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,117 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,175 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,178 - INFO - Video thread started with source: Camera
2025-11-24 18:16:13,182 - ERROR - ❌ No camera found!
2025-11-24 18:16:13,196 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,276 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,279 - INFO - Video thread started with source: Camera
2025-11-24 18:16:13,280 - ERROR - ❌ No camera found!
2025-11-24 18:16:13,299 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,313 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,424 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,429 - INFO - Video file uploaded: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:16:13,429 - INFO - Video thread started with source: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:16:13,439 - INFO - ✓ Video file opened: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:16:13,445 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,449 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,459 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,466 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,533 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,549 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,552 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,569 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,633 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,633 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,651 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,657 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,670 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,671 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,729 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,731 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,749 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,751 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,768 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,768 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,828 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,834 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,853 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,856 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,865 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,872 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,933 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,942 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,954 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,960 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:13,963 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,025 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,025 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,046 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,048 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,058 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,118 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,120 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,137 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,145 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,153 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,155 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,215 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,216 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,233 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,239 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,249 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,251 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,311 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,315 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,332 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,339 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,349 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,349 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,412 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,413 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,431 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,433 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,448 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,449 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,506 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,511 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,528 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,533 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,544 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,546 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,603 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,606 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,622 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,628 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,638 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,641 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,648 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,709 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,729 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,730 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,743 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,800 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,801 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,823 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,826 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,835 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,841 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,895 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,899 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,919 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,923 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,935 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,937 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,993 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:14,997 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,015 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,017 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,027 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,033 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,089 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,092 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,108 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,114 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,124 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,126 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,185 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,189 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,208 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,210 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,223 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,280 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,285 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,304 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,309 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,321 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,322 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,377 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,380 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,396 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,401 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,413 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,415 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,423 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,486 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,490 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,505 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,513 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,522 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,524 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,586 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,591 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,606 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,612 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,622 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,624 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,681 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,684 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,704 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,706 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,720 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,722 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,783 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,791 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,805 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,813 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,821 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,824 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,884 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,886 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,903 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,911 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,919 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,922 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,979 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:15,982 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,000 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,005 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,016 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,019 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,079 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,080 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,097 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,104 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,113 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,115 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,173 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,176 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,194 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,197 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,208 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,271 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,275 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,290 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,295 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,308 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,309 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,369 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,371 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,388 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,394 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,403 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,407 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,465 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,466 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,487 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,488 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,501 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,562 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,566 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,580 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,589 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,596 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,598 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,656 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,660 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,675 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,681 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,694 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,696 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,756 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,756 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,777 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,779 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,793 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,795 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,855 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,859 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,878 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,881 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,894 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,946 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,951 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,970 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,973 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:16,989 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,046 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,046 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,050 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,064 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,072 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,082 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,144 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,144 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,145 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,164 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,168 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,182 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,239 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,239 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,242 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,260 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,266 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,278 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,337 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,337 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,340 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,357 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,364 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,377 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,433 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,433 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,434 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,455 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,460 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,527 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,527 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,529 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,546 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,551 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,564 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,632 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,635 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,636 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,655 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,657 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,674 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,730 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,735 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,744 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,758 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,762 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,824 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,825 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,825 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,844 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,847 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,863 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,867 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,926 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,926 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,943 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,945 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,964 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:17,964 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,021 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,040 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,042 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,113 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,113 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,117 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,132 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,140 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,150 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,216 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,217 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,218 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,240 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,243 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,311 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,311 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,312 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,334 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,338 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,353 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,411 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,411 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,416 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,430 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,438 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,448 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,512 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,512 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,512 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,531 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,533 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,549 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,612 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,613 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,614 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,632 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,638 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,650 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,716 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,719 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,721 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,742 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,745 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,817 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,817 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,822 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,836 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,844 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,855 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,913 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,913 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,915 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,932 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,938 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:18,951 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,025 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,028 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,028 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,047 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,049 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,065 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,138 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,139 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,143 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,158 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,168 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,177 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,255 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,255 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,259 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,276 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,282 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,294 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,358 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,358 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,359 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,380 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,382 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,398 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,463 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,464 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,464 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,484 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,488 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,503 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,569 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,570 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,574 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,589 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,598 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,608 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,701 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,702 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,715 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,727 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,733 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,800 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,801 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,823 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,825 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,829 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,892 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,899 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,913 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,921 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,929 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,932 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,988 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:19,992 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,007 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,017 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,022 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,026 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,093 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,096 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,115 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,121 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,132 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,133 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,202 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,207 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,222 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,239 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,240 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,242 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,333 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,338 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,355 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,363 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,373 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,374 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,434 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,438 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,457 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,462 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,474 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,476 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,530 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,534 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,553 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,555 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,569 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,572 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,631 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,632 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,649 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,654 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,668 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,668 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,735 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,736 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,755 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,760 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,771 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,773 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,836 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,837 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,858 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,863 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,871 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,932 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,936 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,951 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,959 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,967 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:20,969 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,031 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,035 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,050 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,059 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,067 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,069 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,127 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,132 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,146 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,153 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,165 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,165 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,230 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,231 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,252 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,255 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,267 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,270 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,334 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,337 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,356 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,359 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,373 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,375 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,382 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,445 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,461 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,464 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,481 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,483 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,483 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,546 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,565 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,567 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,581 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,586 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,644 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,663 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,667 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,684 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,685 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,745 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,751 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,764 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,774 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,782 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,782 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,851 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,855 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,869 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,878 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,885 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,888 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,954 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,957 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,974 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,980 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,990 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:21,992 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,049 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,051 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,072 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,077 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,086 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,091 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,151 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,155 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,172 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,178 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,189 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,191 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,251 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,251 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,270 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,274 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,286 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,289 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,349 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,350 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,369 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,373 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,383 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,442 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,446 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,464 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,468 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,481 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,483 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,544 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,548 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,566 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,570 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,582 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,584 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,646 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,648 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,665 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,672 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,682 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,683 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,745 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,747 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,763 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,771 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,780 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,781 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,843 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,847 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,865 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,874 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,882 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,884 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,951 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,953 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,970 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,978 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,987 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:22,988 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,046 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,047 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,068 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,072 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,084 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,087 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,144 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,148 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,162 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,172 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,181 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,182 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,247 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,251 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,268 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,273 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,282 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,343 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,347 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,362 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,371 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,379 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,381 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,439 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,440 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,459 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,464 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,476 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,477 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,533 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,537 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,556 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,560 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,573 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,574 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,634 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,635 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,656 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,660 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,669 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,730 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,732 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,749 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,755 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,766 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,767 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,827 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,828 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,846 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,849 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,863 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,864 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,925 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,927 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,944 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,950 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,960 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:23,962 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,018 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,023 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,037 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,046 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,054 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,055 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,115 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,120 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,134 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,142 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,151 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,153 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,213 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,214 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,233 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,238 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,248 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,251 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,314 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,317 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,333 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,342 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,349 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,351 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,416 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,422 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,440 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,444 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,455 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,458 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,520 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,524 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,539 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,545 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,553 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,557 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,620 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,626 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,639 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,647 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,655 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,658 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,725 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,725 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,744 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,747 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,760 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,762 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,819 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,821 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,838 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,843 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,855 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,857 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,863 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,921 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,928 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,942 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,949 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,959 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:24,960 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,021 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,022 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,043 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,045 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,057 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,061 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,126 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,127 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,148 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,149 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,160 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,226 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,227 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,246 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,248 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,262 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,265 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,320 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,323 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,340 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,346 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,356 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,358 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,420 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,425 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,440 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,446 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,456 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,458 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,518 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,522 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,536 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,544 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,553 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,554 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,614 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,616 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,633 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,639 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,649 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,650 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,711 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,719 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,733 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,742 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,749 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,751 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,809 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,814 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,830 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,838 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,846 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,848 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,913 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,917 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,931 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,939 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,947 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:25,950 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,010 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,010 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,031 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,037 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,047 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,049 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,109 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,110 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,128 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,133 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,145 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,146 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,201 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,203 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,221 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,228 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,237 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,240 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,298 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,303 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,321 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,325 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,338 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,340 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,397 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,399 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,416 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,422 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,432 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,435 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,505 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,506 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,525 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,527 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,541 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,543 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,605 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,609 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,627 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,630 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,643 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,645 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,706 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,709 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,727 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,731 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,745 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,746 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,815 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,815 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,833 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,840 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,850 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,852 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,910 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,912 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,931 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,933 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,947 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:26,949 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,008 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,012 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,029 - INFO - End of video file reached
2025-11-24 18:16:27,030 - INFO - Video capture loop ended
2025-11-24 18:16:27,032 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,043 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,106 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,109 - INFO - Video thread started with source: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:16:27,119 - INFO - ✓ Video file opened: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:16:27,130 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,131 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,144 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,204 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,207 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,223 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,229 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,239 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,242 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,304 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,305 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,322 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,329 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,339 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,341 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,401 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,403 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,424 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,426 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,440 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,442 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,500 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,502 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,522 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,526 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,535 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,541 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,603 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,608 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,626 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,628 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,642 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,644 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,702 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,705 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,724 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,728 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,741 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,742 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,806 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,808 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,825 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,831 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,841 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,844 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,903 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,907 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,924 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,931 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,941 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:27,943 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,000 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,003 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,021 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,025 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,038 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,040 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,096 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,097 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,117 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,121 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,130 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,136 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,190 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,195 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,209 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,217 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,227 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,229 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,287 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,291 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,308 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,317 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,325 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,326 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,385 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,385 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,407 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,409 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,423 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,425 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,484 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,485 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,506 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,509 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,522 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,525 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,586 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,590 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,605 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,612 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,621 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,624 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,681 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,681 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,701 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,703 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,717 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,719 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,778 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,778 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,799 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,806 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,816 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,817 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,878 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,882 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,900 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,905 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,916 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,918 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,976 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,979 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:28,997 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,004 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,011 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,015 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,076 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,076 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,095 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,097 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,109 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,113 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,171 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,175 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,193 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,196 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,210 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,268 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,269 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,291 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,293 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,304 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,310 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,371 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,375 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,393 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,396 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,405 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,411 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,470 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,471 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,491 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,495 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,506 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,509 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,563 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,569 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,583 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,592 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,602 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,604 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,668 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,673 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,686 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,694 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,703 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,705 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,768 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,768 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,787 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,793 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,804 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,806 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,865 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,870 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,884 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,893 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,901 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,903 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,968 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,973 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,991 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:29,999 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,007 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,009 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,072 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,074 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,093 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,100 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,110 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,111 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,170 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,175 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,193 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,196 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,204 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,211 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,268 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,270 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,289 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,293 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,304 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,308 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,365 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,368 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,384 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,392 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,403 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,403 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,467 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,467 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,487 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,490 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,503 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,507 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,567 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,572 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,592 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,593 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,607 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,610 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,668 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,668 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,687 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,694 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,704 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,706 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,778 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,778 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,796 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,801 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,811 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,815 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,874 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,875 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,897 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,899 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,910 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,969 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,973 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,991 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:30,996 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,003 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,010 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,075 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,079 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,093 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,102 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,110 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,111 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,174 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,175 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,194 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,199 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,210 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,275 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,279 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,296 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,300 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,310 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,369 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,374 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,388 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,397 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,405 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,407 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,469 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,469 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,491 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,494 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,506 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,510 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,568 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,569 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,587 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,592 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,606 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,606 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,667 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,671 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,690 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,691 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,707 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,710 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,765 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,768 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,787 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,790 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,805 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,867 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,873 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,892 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,894 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,907 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,968 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,979 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:31,992 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,000 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,009 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,010 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,067 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,070 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,089 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,093 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,102 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,108 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,166 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,168 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,186 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,192 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,201 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,204 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,262 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,262 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,281 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,283 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,297 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,299 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,361 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,362 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,383 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,387 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,399 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,401 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,459 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,464 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,478 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,487 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,496 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,497 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,562 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,565 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,583 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,588 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,596 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,658 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,662 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,677 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,683 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,693 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,695 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,754 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,756 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,774 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,777 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,789 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,792 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,850 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,854 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,869 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,878 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,885 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,888 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,947 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,950 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,965 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,973 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,977 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:32,984 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,043 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,045 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,063 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,066 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,080 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,081 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,139 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,140 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,161 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,164 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,178 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,180 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,239 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,239 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,261 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,263 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,273 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,330 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,333 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,349 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,357 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,365 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,367 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,430 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,432 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,449 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,455 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,465 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,467 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,528 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,531 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,550 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,554 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,566 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,569 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,630 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,631 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,653 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,655 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,664 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,730 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,731 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,748 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,755 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,765 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,766 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,826 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,835 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,845 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,858 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,863 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,866 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,930 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,936 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,949 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,960 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,965 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:33,967 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,029 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,034 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,053 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,060 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,071 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,072 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,130 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,132 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,150 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,155 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,169 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,169 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,230 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,232 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,248 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,255 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,264 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,266 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,328 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,332 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,350 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,354 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,366 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,369 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,430 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,432 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,449 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,455 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,466 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,557 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,566 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,579 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,589 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,596 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,597 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,657 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,658 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,677 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,682 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,691 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,695 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,757 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,760 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,778 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,782 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,795 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,797 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,861 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,863 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,880 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,887 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,897 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,899 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,959 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,961 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,978 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,983 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,996 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:34,997 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,063 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,068 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,083 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,093 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,099 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,101 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,168 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,172 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,187 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,195 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,203 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,205 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,266 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,267 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,286 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,291 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,301 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,305 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,374 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,385 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,396 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,403 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,405 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,473 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,474 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,493 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,496 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,508 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,511 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,575 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,577 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,594 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,600 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,610 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,612 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,672 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,675 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,690 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,697 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,707 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,709 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,767 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,771 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,786 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,794 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,802 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,804 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,865 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,870 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,884 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,892 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,901 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,902 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,966 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,967 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,986 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:35,990 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,000 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,059 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,064 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,082 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,085 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,098 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,100 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,160 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,162 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,179 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,187 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,195 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,197 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,256 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,256 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,275 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,279 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,290 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,293 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,357 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,369 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,378 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,387 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,393 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,460 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,460 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,480 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,482 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,495 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,555 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,564 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,574 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,586 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,593 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,595 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,656 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,661 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,678 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,685 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,696 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,696 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,756 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,760 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,775 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,783 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,793 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,796 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,852 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,857 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,875 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,880 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,892 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,894 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,954 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,958 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,975 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,979 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,994 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:36,994 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,056 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,059 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,077 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,082 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,094 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,095 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,164 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,167 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,186 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,191 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,200 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,205 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,268 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,280 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,294 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,299 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,303 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,381 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,381 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,399 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,407 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,416 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,417 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,474 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,479 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,493 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,499 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,509 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,511 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,574 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,575 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,593 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,598 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,610 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,612 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,677 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,679 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,699 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,700 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,713 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,777 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,777 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,796 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,799 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,812 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,814 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,873 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,874 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,892 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,896 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,909 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,910 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,968 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,970 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,987 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:37,994 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,004 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,005 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,065 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,066 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,085 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,089 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,099 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,158 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,163 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,179 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,187 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,193 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,196 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,261 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,262 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,280 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,287 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,296 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,299 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,359 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,360 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,378 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,383 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,393 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,396 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,457 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,463 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,476 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,484 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,492 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,495 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,554 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,559 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,572 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,580 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,588 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,591 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,650 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,654 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,669 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,677 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,681 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,688 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,749 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,751 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,770 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,774 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,783 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,849 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,855 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,868 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,878 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,885 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,887 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,950 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,954 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,972 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,976 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,989 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:38,991 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,050 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,054 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,069 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,078 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,086 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,088 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,148 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,154 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,169 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,177 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,185 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,188 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,261 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,263 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,279 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,287 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,295 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,297 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,364 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,365 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,384 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,389 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,400 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,402 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,460 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,462 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,481 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,483 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,497 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,499 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,561 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,563 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,582 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,589 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,598 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,600 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,662 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,666 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,681 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,688 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,697 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,699 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,762 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,766 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,785 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,791 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,801 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,803 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,872 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,876 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,891 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,898 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,907 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,910 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,965 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,969 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,987 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:39,994 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,005 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,006 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,063 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,066 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,084 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,090 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,101 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,103 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,160 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,165 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,183 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,187 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,197 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,201 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,261 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,262 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,281 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,283 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,296 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,299 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,360 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,361 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,379 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,384 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,396 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,397 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,457 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,460 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,475 - INFO - End of video file reached
2025-11-24 18:16:40,476 - INFO - Video capture loop ended
2025-11-24 18:16:40,485 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,491 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,557 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,557 - INFO - Video thread started with source: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:16:40,566 - INFO - ✓ Video file opened: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:16:40,576 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,579 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,592 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,594 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,654 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,658 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,672 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,680 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,689 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,691 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,751 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,753 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,770 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,774 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,786 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,789 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,851 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,860 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,870 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,881 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,889 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,891 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,960 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,961 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,979 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,982 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,996 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:40,998 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,062 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,064 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,081 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,088 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,097 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,099 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,166 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,171 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,189 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,195 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,205 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,207 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,274 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,274 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,293 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,298 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,309 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,312 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,376 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,377 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,395 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,399 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,412 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,413 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,478 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,481 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,496 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,505 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,513 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,514 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,579 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,581 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,599 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,607 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,615 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,701 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,709 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,720 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,731 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,738 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,741 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,796 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,800 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,819 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,824 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,835 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,838 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,894 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,897 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,915 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,922 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,927 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,933 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,992 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:41,996 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,010 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,020 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,029 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,031 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,088 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,093 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,109 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,116 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,126 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,127 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,183 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,188 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,206 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,211 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,219 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,224 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,281 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,283 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,299 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,306 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,315 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,317 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,387 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,388 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,407 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,410 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,423 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,425 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,431 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,495 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,511 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,513 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,527 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,532 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,532 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,603 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,612 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,626 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,630 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,633 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,695 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,698 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,716 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,721 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,729 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,735 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,794 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,799 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,813 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,823 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,829 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,831 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,897 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,899 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,915 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,924 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,932 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,933 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,998 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:42,999 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,017 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,023 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,032 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,036 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,097 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,097 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,115 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,118 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,132 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,134 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,194 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,198 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,217 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,220 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,232 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,291 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,296 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,314 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,320 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,329 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,332 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,389 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,392 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,410 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,413 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,424 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,428 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,486 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,488 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,506 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,510 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,523 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,524 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,584 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,585 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,603 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,609 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,619 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,675 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,684 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,698 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,705 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,715 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,716 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,776 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,781 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,797 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,805 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,814 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,815 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,877 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,880 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,898 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,900 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,914 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,916 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,976 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,976 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:43,999 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,001 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,011 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,077 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,079 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,098 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,100 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,111 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,116 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,182 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,184 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,203 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,209 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,220 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,222 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,288 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,288 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,308 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,312 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,323 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,326 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,391 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,391 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,409 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,414 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,425 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,427 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,491 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,492 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,511 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,515 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,527 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,529 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,592 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,593 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,611 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,616 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,626 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,629 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,692 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,696 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,711 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,720 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,727 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,729 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,795 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,797 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,814 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,821 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,831 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,832 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,892 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,897 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,914 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,921 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,930 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,932 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,991 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:44,994 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,010 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,015 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,028 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,028 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,035 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,095 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,114 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,116 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,130 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,134 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,197 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,218 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,218 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,237 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,238 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,241 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,302 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,324 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,326 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,340 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,397 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,400 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,419 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,423 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,435 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,439 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,499 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,512 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,521 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,530 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,532 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,590 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,592 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,613 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,616 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,629 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,631 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,690 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,691 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,712 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,715 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,726 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,789 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,789 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,808 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,811 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,825 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,827 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,886 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,886 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,905 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,909 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,921 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,924 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,982 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:45,996 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,005 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,013 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,017 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,077 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,079 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,096 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,103 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,114 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,117 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,185 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,188 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,208 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,220 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,283 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,290 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,302 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,315 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,321 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,323 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,391 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,391 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,411 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,414 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,427 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,429 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,488 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,489 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,509 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,514 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,525 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,527 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,584 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,589 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,606 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,612 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,622 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,624 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,685 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,685 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,707 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,709 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,718 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,783 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,788 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,803 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,811 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,819 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,821 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,882 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,883 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,902 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,908 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,913 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,921 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,979 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,984 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:46,999 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,005 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,013 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,078 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,085 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,100 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,109 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,117 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,118 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,178 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,182 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,199 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,207 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,216 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,217 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,275 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,279 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,298 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,300 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,313 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,317 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,382 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,396 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,404 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,413 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,414 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,479 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,483 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,498 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,507 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,514 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,516 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,579 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,579 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,597 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,604 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,614 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,615 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,678 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,678 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,697 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,700 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,710 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,715 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,774 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,777 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,798 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,800 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,808 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,874 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,875 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,894 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,896 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,906 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,913 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,973 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,987 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:47,995 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,004 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,005 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,065 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,069 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,084 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,092 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,100 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,102 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,161 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,161 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,181 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,183 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,194 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,199 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,258 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,258 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,279 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,282 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,297 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,298 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,358 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,362 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,380 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,382 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,397 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,398 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,457 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,458 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,479 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,482 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,495 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,497 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,561 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,565 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,580 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,589 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,597 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,598 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,665 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,667 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,685 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,690 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,700 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,703 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,764 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,771 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,788 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,797 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,800 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,888 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,893 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,907 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,913 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,925 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,928 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,990 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:48,991 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,009 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,013 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,026 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,027 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,085 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,086 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,104 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,110 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,119 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,123 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,181 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,194 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,202 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,215 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,274 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,276 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,294 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,298 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,311 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,312 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,377 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,378 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,396 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,400 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,412 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,414 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,480 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,483 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,498 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,507 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,514 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,516 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,583 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,587 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,601 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,610 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,618 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,620 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,683 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,691 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,705 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,713 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,721 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,724 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,780 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,782 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,803 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,807 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,815 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,821 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,878 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,879 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,896 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,904 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,913 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,914 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,979 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,980 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:49,998 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,004 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,014 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,016 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,076 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,076 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,097 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,099 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,110 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,171 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,173 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,191 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,194 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,207 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,210 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,267 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,271 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,288 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,294 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,302 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,307 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,368 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,368 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,389 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,392 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,403 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,463 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,465 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,485 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,488 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,501 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,503 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,568 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,574 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,593 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,594 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,609 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,671 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,676 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,694 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,697 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,711 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,712 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,772 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,773 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,791 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,796 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,808 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,809 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,868 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,869 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,887 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,893 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,903 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,905 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,964 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,966 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,983 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,989 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:50,999 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,000 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,061 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,066 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,083 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,088 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,100 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,102 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,161 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,166 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,181 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,189 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,196 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,199 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,257 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,258 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,280 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,282 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,291 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,354 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,358 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,373 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,381 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,389 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,391 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,457 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,457 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,476 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,480 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,493 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,494 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,558 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,561 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,576 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,583 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,594 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,595 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,662 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,666 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,680 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,689 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,698 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,698 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,763 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,763 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,782 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,787 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,798 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,799 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,856 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,860 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,876 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,882 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,894 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,895 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,954 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,959 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,977 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,980 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,994 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:51,995 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,053 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,058 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,072 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,079 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,088 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,090 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,156 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,157 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,174 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,180 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,187 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,193 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,247 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,250 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,265 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,273 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,283 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,287 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,348 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,349 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,370 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,374 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,444 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,444 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,447 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,466 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,470 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,485 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,550 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,550 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,563 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,575 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,581 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,651 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,652 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,656 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,670 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,679 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,690 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,750 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,752 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,765 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,775 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,783 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,846 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,849 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,850 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,867 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,872 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,886 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,946 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,946 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,950 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,969 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,974 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:52,989 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,044 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,049 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,059 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,071 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,077 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,139 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,140 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,144 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,162 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,165 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,180 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,244 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,247 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,247 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,266 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,272 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,284 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,342 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,344 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,347 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,362 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,371 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,380 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,440 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,443 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,444 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,462 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,467 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,480 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,536 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,540 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,544 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,559 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,566 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,577 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,633 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,634 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,637 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,657 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,660 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,725 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,728 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,729 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,746 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,756 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,764 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,835 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,836 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,837 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,855 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,860 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,874 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,932 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,933 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,936 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,956 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:53,959 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,023 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,024 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,025 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,043 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,047 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,061 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,120 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,120 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,120 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,142 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,144 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,160 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,214 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,215 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,215 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,237 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,242 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,255 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,311 - INFO - End of video file reached
2025-11-24 18:16:54,312 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,314 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,314 - INFO - Video capture loop ended
2025-11-24 18:16:54,338 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,416 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,417 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,420 - INFO - Video thread started with source: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:16:54,428 - INFO - ✓ Video file opened: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:16:54,440 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,442 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,514 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,515 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,518 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,533 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,541 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,552 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,618 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,618 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,619 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,638 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,643 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,657 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,723 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,724 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,724 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,743 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,747 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,761 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,826 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,826 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,828 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,846 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,851 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,864 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,922 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,924 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,925 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,944 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,946 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:54,962 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,022 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,022 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,022 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,041 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,046 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,059 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,119 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,119 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,120 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,139 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,143 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,211 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,216 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,217 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,234 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,240 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,253 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,314 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,314 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,316 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,333 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,340 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,351 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,413 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,413 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,414 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,432 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,437 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,450 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,511 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,513 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,513 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,534 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,538 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,614 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,617 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,617 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,636 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,640 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,654 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,721 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,724 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,727 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,742 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,746 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,762 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,821 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,824 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,828 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,841 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,853 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,860 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,963 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,965 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,965 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,983 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:55,991 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,001 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,070 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,071 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,073 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,094 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,096 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,167 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,173 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,173 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,192 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,196 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,210 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,272 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,277 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,277 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,296 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,300 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,314 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,380 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,380 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,381 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,399 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,405 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,417 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,483 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,486 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,492 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,506 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,513 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,525 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,581 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,581 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,583 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,601 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,608 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,620 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,682 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,682 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,683 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,702 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,708 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,721 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,779 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,779 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,783 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,801 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,806 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,820 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,875 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,875 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,877 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,894 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,899 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,912 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,973 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,975 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,978 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,994 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:56,997 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,015 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,016 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,073 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,089 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,091 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,108 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,113 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,170 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,171 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,186 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,189 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,207 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,209 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,266 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,281 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,281 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,300 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,304 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,358 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,361 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,376 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,379 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,396 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,398 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,463 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,465 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,468 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,488 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,490 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,560 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,561 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,563 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,579 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,585 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,598 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,658 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,659 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,662 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,681 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,683 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,699 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,761 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,761 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,762 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,780 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,785 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,798 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,855 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,857 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,857 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,874 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,878 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,893 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,899 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,963 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,963 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,967 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,986 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:57,991 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,004 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,060 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,060 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,065 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,083 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,089 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,101 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,163 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,163 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,169 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,182 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,194 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,200 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,266 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,268 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,270 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,285 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,294 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,304 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,370 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,372 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,374 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,390 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,395 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,409 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,469 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,470 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,471 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,492 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,494 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,510 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,571 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,572 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,573 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,593 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,597 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,665 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,665 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,666 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,687 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,690 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,761 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,762 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,762 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,780 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,785 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,798 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,864 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,865 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,866 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,883 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,888 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,903 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,963 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,963 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,963 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,983 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:58,985 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,054 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,057 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,060 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,074 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,084 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,092 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,156 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,156 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,158 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,175 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,181 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,193 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,253 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,254 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,258 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,273 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,280 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,291 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,347 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,349 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,351 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,370 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,373 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,389 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,444 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,445 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,446 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,466 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,470 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,484 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,540 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,544 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,544 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,563 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,566 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,582 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,643 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,647 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,656 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,668 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,675 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,737 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,738 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,738 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,757 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,762 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,829 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,831 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,835 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,848 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,859 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,866 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,930 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,933 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,935 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,954 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,959 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:16:59,972 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,030 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,034 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,034 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,053 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,059 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,072 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,129 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,129 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,143 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,154 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,161 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,222 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,222 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,227 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,244 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,247 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,262 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,321 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,322 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,323 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,340 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,347 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,358 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,417 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,417 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,419 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,437 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,443 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,455 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,512 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,512 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,516 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,533 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,539 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,551 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,610 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,613 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,615 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,631 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,639 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,649 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,709 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,710 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,713 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,731 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,734 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,749 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,809 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,810 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,813 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,828 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,837 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,846 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,907 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,908 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,908 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,927 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,929 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:00,945 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,002 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,004 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,007 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,025 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,031 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,044 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,105 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,105 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,110 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,127 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,135 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,145 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,213 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,214 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,232 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,237 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,250 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,310 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,312 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,313 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,332 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,337 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,350 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,409 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,410 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,411 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,428 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,436 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,446 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,506 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,507 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,510 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,528 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,533 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,546 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,605 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,606 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,609 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,624 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,632 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,643 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,704 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,705 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,708 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,728 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,729 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,798 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,801 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,819 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,823 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,836 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,838 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,895 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,897 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,914 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,921 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,930 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,932 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,991 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:01,993 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,012 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,016 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,029 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,030 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,087 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,091 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,110 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,112 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,125 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,182 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,188 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,201 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,210 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,219 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,220 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,290 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,292 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,309 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,315 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,325 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,327 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,393 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,397 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,411 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,418 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,427 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,429 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,493 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,495 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,514 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,516 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,531 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,532 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,594 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,594 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,613 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,618 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,629 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,631 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,692 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,693 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,711 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,715 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,727 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,729 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,787 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,791 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,810 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,813 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,823 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,828 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,888 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,889 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,908 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,917 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,925 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:02,927 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,026 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,039 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,048 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,057 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,059 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,115 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,120 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,134 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,144 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,152 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,154 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,216 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,232 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,240 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,248 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,250 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,310 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,315 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,329 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,338 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,346 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,347 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,406 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,410 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,427 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,430 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,443 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,446 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,505 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,506 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,524 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,530 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,536 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,543 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,603 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,613 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,625 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,631 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,635 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,696 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,701 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,715 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,725 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,732 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,733 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,792 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,799 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,814 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,822 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,830 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,832 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,894 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,895 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,913 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,918 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,929 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,932 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,991 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:03,994 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,013 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,017 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,029 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,031 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,093 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,094 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,113 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,116 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,127 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,131 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,191 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,191 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,210 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,222 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,228 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,284 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,289 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,304 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,312 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,321 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,323 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,385 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,385 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,403 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,409 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,416 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,422 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,484 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,486 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,504 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,509 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,521 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,523 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,582 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,597 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,608 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,615 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,617 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,683 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,685 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,702 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,709 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,719 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,721 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,783 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,785 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,802 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,810 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,817 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,820 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,890 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,891 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,910 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,914 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,925 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,928 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,986 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:04,990 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,005 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,013 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,021 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,024 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,083 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,096 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,104 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,113 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,114 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,176 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,177 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,196 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,198 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,214 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,218 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,283 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,283 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,303 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,305 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,319 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,381 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,385 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,404 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,411 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,422 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,424 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,501 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,502 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,520 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,527 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,535 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,539 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,600 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,610 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,622 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,629 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,631 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,691 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,693 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,711 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,716 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,726 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,729 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,789 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,790 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,809 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,811 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,823 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,827 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,887 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,890 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,909 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,913 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,922 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,928 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:05,993 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,006 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,016 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,024 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,027 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,094 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,098 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,113 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,123 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,130 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,131 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,189 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,194 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,217 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,231 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,231 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,295 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,299 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,317 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,322 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,333 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,335 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,398 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,403 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,420 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,428 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,436 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,439 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,508 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,508 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,527 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,530 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,543 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,546 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,605 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,607 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,625 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,631 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,644 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,645 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,704 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,708 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,727 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,729 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,742 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,797 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,803 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,818 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,827 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,836 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,838 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,898 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,900 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,916 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,925 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,929 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,935 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,997 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:06,998 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,016 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,020 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,031 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,035 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,093 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,094 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,115 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,116 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,129 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,133 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,200 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,203 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,223 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,227 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,238 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,241 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,305 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,310 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,325 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,332 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,341 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,343 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,407 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,408 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,426 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,431 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,444 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,445 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,504 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,505 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,524 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,529 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,541 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,542 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,605 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,607 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,624 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,630 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,640 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,642 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,704 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,709 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,728 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,733 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,741 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,746 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,808 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,809 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,829 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,832 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,846 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,847 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,910 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,911 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,929 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,934 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,947 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:07,947 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,007 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,008 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,027 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,029 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,044 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,044 - INFO - End of video file reached
2025-11-24 18:17:08,046 - INFO - Video capture loop ended
2025-11-24 18:17:08,105 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,109 - INFO - Video thread started with source: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:17:08,118 - INFO - ✓ Video file opened: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:17:08,130 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,130 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,141 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,211 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,231 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,235 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,246 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,249 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,319 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,322 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,338 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,346 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,355 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,357 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,421 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,423 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,441 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,447 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,457 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,459 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,521 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,527 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,542 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,547 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,558 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,560 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,568 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,631 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,649 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,653 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,669 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,671 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,673 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,753 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,754 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,772 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,775 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,833 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,856 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,861 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,874 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,875 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,933 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,934 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,953 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,956 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,965 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:08,972 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,029 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,033 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,047 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,055 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,064 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,065 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,124 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,127 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,144 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,149 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,160 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,162 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,223 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,227 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,245 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,247 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,262 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,263 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,320 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,324 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,342 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,345 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,355 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,360 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,418 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,418 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,437 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,441 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,453 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,455 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,508 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,512 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,529 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,533 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,546 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,547 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,608 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,609 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,627 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,632 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,643 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,645 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,700 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,707 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,721 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,729 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,738 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,740 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,797 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,798 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,816 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,822 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,831 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,834 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,891 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,895 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,910 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,918 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,926 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,928 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,988 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:09,990 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,007 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,013 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,024 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,026 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,112 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,112 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,132 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,140 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,149 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,150 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,208 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,229 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,237 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,245 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,247 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,306 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,306 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,325 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,327 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,341 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,343 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,401 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,406 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,420 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,427 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,436 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,438 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,498 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,503 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,518 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,525 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,536 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,538 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,595 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,598 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,614 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,621 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,631 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,632 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,642 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,699 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,715 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,718 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,736 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,797 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,802 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,817 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,817 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,836 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,839 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,906 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,906 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,920 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,925 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,942 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:10,945 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,008 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,008 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,022 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,029 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,041 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,101 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,102 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,104 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,122 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,126 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,141 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,198 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,200 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,200 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,219 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,225 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,237 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,295 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,296 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,298 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,317 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,322 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,336 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,396 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,397 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,397 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,418 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,422 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,437 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,496 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,496 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,498 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,515 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,521 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,533 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,590 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,595 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,611 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,617 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,624 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,629 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,691 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,694 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,712 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,717 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,729 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,730 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,789 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,793 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,808 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,814 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,823 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,826 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,884 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,888 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,903 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,913 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,920 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,921 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,984 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:11,986 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,003 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,010 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,019 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,021 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,076 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,082 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,096 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,104 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,114 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,117 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,185 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,185 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,207 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,209 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,223 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,225 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,287 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,292 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,310 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,313 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,323 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,328 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,393 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,394 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,412 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,416 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,428 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,430 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,492 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,496 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,511 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,518 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,528 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,529 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,587 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,593 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,608 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,615 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,624 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,626 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,681 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,685 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,700 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,707 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,716 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,718 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,778 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,780 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,800 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,804 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,818 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,819 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,880 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,881 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,899 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,904 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,909 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,917 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,974 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,977 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,995 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:12,998 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,012 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,014 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,079 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,083 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,097 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,106 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,114 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,115 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,177 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,182 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,196 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,204 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,213 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,214 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,273 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,277 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,292 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,300 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,308 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,310 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,367 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,370 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,386 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,392 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,402 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,405 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,465 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,470 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,487 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,490 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,505 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,565 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,567 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,586 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,587 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,604 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,605 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,662 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,663 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,682 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,684 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,698 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,703 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,704 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,779 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,788 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,797 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,802 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,864 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,868 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,886 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,889 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,903 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,904 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,959 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,961 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,979 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,983 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,997 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:13,999 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,064 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,064 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,083 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,088 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,099 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,101 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,167 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,169 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,190 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,194 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,267 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,268 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,269 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,288 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,293 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,307 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,363 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,366 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,376 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,389 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,394 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,459 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,460 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,465 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,478 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,487 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,496 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,553 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,556 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,558 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,575 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,581 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,593 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,655 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,655 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,661 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,674 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,681 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,692 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,748 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,751 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,755 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,770 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,778 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,789 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,848 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,848 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,850 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,866 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,875 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,885 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,943 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,947 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,949 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,965 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,973 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:14,983 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,045 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,045 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,045 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,064 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,066 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,082 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,143 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,145 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,146 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,165 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,168 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,183 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,248 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,249 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,250 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,273 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,275 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,350 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,353 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,353 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,373 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,379 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,392 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,447 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,447 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,452 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,469 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,477 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,488 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,546 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,547 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,552 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,566 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,577 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,584 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,645 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,645 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,646 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,665 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,670 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,682 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,746 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,747 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,747 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,765 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,771 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,783 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,839 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,839 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,844 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,862 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,868 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,880 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,941 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,941 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,942 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,960 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,966 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:15,978 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,041 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,045 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,047 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,063 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,070 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,081 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,148 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,148 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,152 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,167 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,175 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,185 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,252 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,252 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,254 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,273 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,278 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,292 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,356 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,357 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,357 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,379 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,383 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,397 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,458 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,459 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,463 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,481 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,483 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,499 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,565 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,568 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,568 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,588 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,593 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,658 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,662 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,666 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,680 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,688 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,699 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,758 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,758 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,761 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,780 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,784 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,798 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,854 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,857 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,857 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,874 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,880 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,893 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,951 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,952 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,952 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,973 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,976 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:16,992 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,092 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,093 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,106 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,113 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,125 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,190 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,191 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,195 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,210 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,218 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,228 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,297 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,297 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,301 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,315 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,325 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,333 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,396 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,397 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,401 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,415 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,425 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,433 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,495 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,495 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,499 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,514 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,522 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,532 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,590 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,590 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,591 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,609 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,613 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,627 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,687 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,689 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,690 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,712 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,713 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,732 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,735 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,788 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,792 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,808 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,810 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,827 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,886 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,887 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,889 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,907 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,910 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,985 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,986 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:17,991 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,005 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,013 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,024 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,082 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,082 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,083 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,100 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,105 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,119 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,179 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,182 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,182 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,201 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,206 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,219 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,275 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,275 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,279 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,298 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,300 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,316 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,377 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,378 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,391 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,399 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,409 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,470 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,473 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,475 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,492 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,499 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,510 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,567 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,570 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,570 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,589 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,593 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,659 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,663 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,664 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,681 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,687 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,700 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,757 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,759 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,761 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,777 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,785 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,796 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,855 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,856 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,859 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,877 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,881 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,895 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,951 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,951 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,955 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,974 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,977 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:18,993 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,048 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,050 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,062 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,074 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,080 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,143 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,144 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,146 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,165 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,172 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,183 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,242 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,242 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,245 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,264 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,266 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,282 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,341 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,344 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,344 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,362 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,365 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,381 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,443 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,443 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,447 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,462 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,468 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,481 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,542 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,542 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,543 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,563 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,565 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,581 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,648 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,648 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,648 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,671 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,673 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,746 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,747 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,748 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,767 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,777 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,786 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,850 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,851 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,856 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,871 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,878 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,890 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,954 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,954 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,958 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,976 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,981 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:19,994 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,053 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,053 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,054 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,077 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,079 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,166 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,166 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,178 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,189 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,208 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,211 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,312 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,313 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,313 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,336 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,339 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,405 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,405 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,409 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,424 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,430 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,442 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,502 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,502 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,506 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,521 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,528 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,539 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,602 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,603 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,604 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,621 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,629 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,640 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,696 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,700 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,700 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,718 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,722 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,737 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,794 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,794 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,798 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,816 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,819 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,834 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,891 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,892 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,894 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,914 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,917 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,932 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,990 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,993 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:20,997 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,012 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,023 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,031 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,090 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,091 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,095 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,111 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,116 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,129 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,191 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,192 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,193 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,210 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,216 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,229 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,285 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,286 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,290 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,308 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,311 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,326 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,384 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,384 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,387 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,403 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,411 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,421 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,431 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,497 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,498 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,502 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,518 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,525 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,537 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,596 - INFO - End of video file reached
2025-11-24 18:17:21,601 - INFO - Video capture loop ended
2025-11-24 18:17:21,601 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,603 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,626 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,702 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,702 - INFO - Video thread started with source: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:17:21,704 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,711 - INFO - ✓ Video file opened: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:17:21,721 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,725 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,739 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,801 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,801 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,806 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,820 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,828 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,838 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,898 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,898 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,900 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,917 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,924 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,935 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,995 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,999 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:21,999 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,018 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,021 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,092 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,094 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,098 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,111 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,121 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,129 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,188 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,191 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,191 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,210 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,228 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,285 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,286 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,286 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,306 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,309 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,325 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,329 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,394 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,394 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,411 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,413 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,432 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,432 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,495 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,498 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,515 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,521 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,528 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,534 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,602 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,607 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,626 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,630 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,642 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,644 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,704 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,707 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,726 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,731 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,739 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,744 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,807 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,808 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,826 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,832 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,843 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,844 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,907 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,914 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,927 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,935 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,944 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:22,945 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,006 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,006 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,026 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,028 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,041 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,044 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,103 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,114 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,126 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,132 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,137 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,197 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,199 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,217 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,221 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,235 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,236 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,296 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,300 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,315 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,322 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,331 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,333 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,392 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,397 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,413 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,422 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,429 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,431 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,491 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,494 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,510 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,515 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,526 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,528 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,585 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,589 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,603 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,610 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,620 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,622 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,685 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,688 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,704 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,711 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,721 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,723 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,785 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,785 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,804 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,810 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,819 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,823 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,881 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,886 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,903 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,910 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,919 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,921 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,980 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,981 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:23,999 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,004 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,015 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,016 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,076 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,079 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,097 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,102 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,114 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,115 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,174 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,177 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,196 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,198 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,213 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,214 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,274 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,275 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,296 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,299 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,309 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,314 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,316 - INFO - End of video file reached
2025-11-24 18:17:24,375 - INFO - Video capture loop ended
2025-11-24 18:17:24,375 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,396 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,409 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,475 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,494 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,511 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,513 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,571 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,590 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,606 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,608 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,664 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,687 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,704 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,706 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,766 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,788 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,804 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,807 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,883 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,901 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,905 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,967 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:24,989 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,005 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,007 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,062 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,083 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,100 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,101 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,158 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,179 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,194 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,197 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,252 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,274 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,290 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,292 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,349 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,368 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,385 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,387 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,448 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,467 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,483 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,485 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,548 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,569 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,583 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,588 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,653 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,672 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,688 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,742 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,761 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,779 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,781 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,848 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,866 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,883 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,884 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,946 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,965 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,981 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:25,982 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,049 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,068 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,084 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,087 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,164 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,182 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,183 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,250 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,268 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,285 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,286 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,358 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,377 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,393 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,395 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,460 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,479 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,494 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,497 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,560 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,579 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,594 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,597 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,651 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,672 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,689 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,691 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,749 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,767 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,783 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,785 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,844 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,862 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,879 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,880 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,943 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,962 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,978 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:26,980 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,041 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,063 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,079 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,081 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,145 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,163 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,180 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,181 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,244 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,266 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,279 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,284 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,349 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,367 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,383 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,385 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,449 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,471 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,484 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,489 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,543 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,564 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,582 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,583 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,641 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,662 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,679 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,680 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,738 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,757 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,773 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,775 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,848 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,866 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,869 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,929 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,947 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,963 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:27,965 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,024 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,045 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,062 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,064 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,119 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,140 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,157 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,159 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,216 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,237 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,252 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,312 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,333 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,350 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,351 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,414 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,435 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,452 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,453 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,519 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,538 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,555 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,556 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,633 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,650 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,654 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,715 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,738 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,754 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,758 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,828 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,846 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,848 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,905 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,924 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,941 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:28,943 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,002 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,021 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,037 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,039 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,097 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,118 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,131 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,194 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,228 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,230 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,289 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,307 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,324 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,326 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,383 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,402 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,419 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,422 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,498 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,516 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,518 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,587 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,606 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,622 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,625 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,696 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,713 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,715 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,777 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,796 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,812 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,813 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,869 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,891 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,907 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,969 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:29,988 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,007 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,007 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,074 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,093 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,109 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,111 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,171 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,192 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,209 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,210 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,270 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,290 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,306 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,308 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,373 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,392 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,409 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,410 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,465 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,484 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,502 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,503 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,577 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,595 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,659 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,660 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,678 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,696 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,755 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,755 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,774 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,843 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,843 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,861 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,879 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,938 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,942 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,957 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:30,976 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,034 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,035 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,053 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,071 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,126 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,127 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,147 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,165 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,222 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,226 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,241 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,259 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,317 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,319 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,336 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,355 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,412 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,413 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,430 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,448 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,512 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,515 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,536 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,602 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,602 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,621 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,640 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,702 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,703 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,721 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,740 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,800 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,812 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,830 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,891 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,895 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,912 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,930 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,988 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:31,989 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,009 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,027 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,086 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,086 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,104 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,174 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,176 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,193 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,278 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,278 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,299 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,317 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,380 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,380 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,398 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,416 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,484 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,484 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,502 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,521 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,579 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,579 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,598 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,616 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,674 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,677 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,695 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,713 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,772 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,772 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,793 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,811 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,869 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,869 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,888 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,956 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,961 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,978 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:32,996 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,053 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,056 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,074 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,093 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,149 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,149 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,170 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,245 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,245 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,264 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,282 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,341 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,342 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,361 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,379 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,437 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,438 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,457 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,475 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,535 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,546 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,564 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,628 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,629 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,647 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,665 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,720 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,721 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,740 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,759 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,816 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,816 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,834 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,853 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,913 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,914 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,932 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:33,950 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,009 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,010 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,031 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,049 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,111 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,113 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,131 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,150 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,218 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,219 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,238 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,257 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,311 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,326 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,344 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,403 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,403 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,421 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,440 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,502 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,506 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,525 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,543 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,597 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,614 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,632 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,692 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,693 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,711 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,729 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,786 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,786 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,804 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,823 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,883 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,887 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,904 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,923 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,980 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,981 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:34,999 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,016 - INFO - End of video file reached
2025-11-24 18:17:35,017 - INFO - Video capture loop ended
2025-11-24 18:17:35,074 - INFO - Video thread started with source: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:17:35,075 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,083 - INFO - ✓ Video file opened: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:17:35,094 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,111 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,170 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,171 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,189 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,208 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,261 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,264 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,283 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,301 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,358 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,358 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,379 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,397 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,461 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,464 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,482 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,500 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,562 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,565 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,582 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,600 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,657 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,661 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,679 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,697 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,754 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,754 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,775 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,794 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,847 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,847 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,866 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,884 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,942 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,945 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,963 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:35,982 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,042 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,042 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,061 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,079 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,137 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,137 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,156 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,226 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,231 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,245 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,263 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,326 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,326 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,345 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,363 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,417 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,418 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,437 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,455 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,516 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,517 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,538 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,556 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,614 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,614 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,632 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,650 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,706 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,707 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,725 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,743 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,800 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,803 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,822 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,840 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,895 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,896 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,914 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,932 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,990 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:36,993 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,011 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,029 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,089 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,090 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,111 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,181 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,182 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,200 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,218 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,279 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,279 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,298 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,315 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,375 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,375 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,393 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,411 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,465 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,469 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,486 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,505 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,560 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,561 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,581 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,599 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,657 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,661 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,679 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,697 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,758 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,758 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,776 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,795 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,851 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,854 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,872 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,891 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,948 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,961 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:37,979 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,039 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,042 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,060 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,078 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,134 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,135 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,156 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,175 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,233 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,233 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,251 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,270 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,326 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,329 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,347 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,366 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,423 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,426 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,444 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,462 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,518 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,518 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,540 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,558 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,614 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,615 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,633 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,651 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,712 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,712 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,730 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,749 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,810 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,811 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,829 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,847 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,908 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,908 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,926 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,944 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:38,998 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,002 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,016 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,035 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,120 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,124 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,142 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,160 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,217 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,221 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,238 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,257 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,312 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,315 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,333 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,351 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,411 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,411 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,430 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,448 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,509 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,509 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,527 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,545 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,600 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,600 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,621 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,640 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,699 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,699 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,717 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,736 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,794 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,794 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,814 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,833 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,894 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,894 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,912 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,930 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,987 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:39,988 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,008 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,026 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,082 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,084 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,103 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,121 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,178 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,179 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,197 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,216 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,280 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,293 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,311 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,376 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,377 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,395 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,413 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,470 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,473 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,491 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,509 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,572 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,572 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,591 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,609 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,667 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,668 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,686 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,704 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,763 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,764 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,784 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,803 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,860 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,860 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,881 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,899 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,962 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,962 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,980 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:40,998 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,059 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,059 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,077 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,096 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,153 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,153 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,171 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,190 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,245 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,260 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,278 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,338 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,338 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,359 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,377 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,437 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,437 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,456 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,474 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,532 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,532 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,550 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,569 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,626 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,626 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,647 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,665 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,728 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,728 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,746 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,764 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,820 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,825 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,842 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,861 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,917 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,917 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,937 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:41,956 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,015 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,016 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,034 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,053 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,112 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,125 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,144 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,208 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,208 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,229 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,246 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,305 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,307 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,324 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,342 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,403 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,404 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,422 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,441 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,503 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,508 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,524 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,542 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,603 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,608 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,626 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,644 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,705 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,705 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,726 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,744 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,808 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,808 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,826 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,844 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,911 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,911 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:42,931 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,004 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,025 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,039 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,043 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,113 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,131 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,133 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,190 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,211 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,224 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,230 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,284 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,305 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,322 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,324 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,378 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,397 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,415 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,416 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,479 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,497 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,514 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,515 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,571 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,591 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,610 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,610 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,667 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,689 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,703 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,707 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,778 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,796 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,798 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,858 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,877 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,894 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,895 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,952 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,974 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:43,990 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,045 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,064 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,082 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,084 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,145 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,164 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,180 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,182 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,238 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,258 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,274 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,276 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,334 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,352 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,369 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,371 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,431 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,453 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,469 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,471 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,548 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,567 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,568 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,627 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,645 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,661 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,664 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,734 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,753 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,753 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,823 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,842 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,858 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,860 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,919 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,937 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:44,954 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,009 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,028 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,046 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,047 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,108 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,126 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,143 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,144 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,200 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,220 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,236 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,238 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,309 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,327 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,330 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,393 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,411 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,427 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,429 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,489 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,510 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,527 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,528 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,594 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,612 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,628 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,630 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,687 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,706 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,723 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,725 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,778 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,800 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,817 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,819 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,875 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,894 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,912 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,913 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,973 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:45,991 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,008 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,009 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,068 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,091 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,107 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,161 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,182 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,200 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,201 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,262 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,283 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,300 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,301 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,361 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,383 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,401 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,402 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,464 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,482 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,499 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,500 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,564 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,582 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,599 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,600 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,665 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,686 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,702 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,704 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,759 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,777 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,795 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,796 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,860 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,881 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,897 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,899 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,959 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,978 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,996 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:46,999 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,097 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,116 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,132 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,134 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,198 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,217 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,233 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,235 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,294 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,312 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,329 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,330 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,390 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,411 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,425 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,485 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,507 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,524 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,525 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,586 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,608 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,624 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,627 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,690 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,709 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,725 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,727 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,784 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,806 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,821 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,824 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,895 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,913 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,914 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,974 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:47,992 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,011 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,012 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,069 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,087 - INFO - End of video file reached
2025-11-24 18:17:48,089 - INFO - Video capture loop ended
2025-11-24 18:17:48,105 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,162 - INFO - Video thread started with source: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:17:48,173 - INFO - ✓ Video file opened: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:17:48,182 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,197 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,199 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,261 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,280 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,295 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,298 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,358 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,377 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,393 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,395 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,453 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,471 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,488 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,490 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,564 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,581 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,582 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,639 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,661 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,677 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,679 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,739 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,758 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,777 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,777 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,844 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,863 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,878 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,881 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,936 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,956 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,974 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:48,975 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,034 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,053 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,066 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,071 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,124 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,148 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,163 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,166 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,225 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,243 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,260 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,261 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,318 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,337 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,354 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,356 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,417 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,436 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,455 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,507 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,524 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,543 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,607 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,608 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,627 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,646 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,712 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,713 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,731 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,749 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,811 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,814 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,832 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,850 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,916 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,917 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,935 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:49,954 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,011 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,025 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,043 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,102 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,105 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,123 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,141 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,195 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,199 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,216 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,234 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,291 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,291 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,309 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,328 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,392 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,392 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,411 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,429 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,486 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,487 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,505 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,524 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,578 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,581 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,599 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,617 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,675 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,676 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,694 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,712 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,770 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,771 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,789 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,808 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,864 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,877 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,895 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,956 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,957 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,978 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:50,996 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,052 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,055 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,074 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,092 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,150 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,163 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,181 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,241 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,241 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,259 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,277 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,337 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,337 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,356 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,374 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,433 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,435 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,453 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,471 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,533 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,533 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,553 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,571 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,628 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,629 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,650 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,668 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,728 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,728 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,746 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,765 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,827 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,828 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,848 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,924 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,928 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:51,947 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,019 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,019 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,042 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,060 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,124 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,124 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,147 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,221 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,222 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,240 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,258 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,318 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,319 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,337 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,356 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,418 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,419 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,437 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,455 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,514 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,516 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,534 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,554 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,615 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,615 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,633 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,652 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,709 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,723 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,741 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,805 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,805 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,826 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,844 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,906 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,906 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,927 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:52,945 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,008 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,008 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,027 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,045 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,102 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,103 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,122 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,140 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,199 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,200 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,217 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,236 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,298 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,298 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,317 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,336 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,399 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,399 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,418 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,436 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,497 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,498 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,519 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,538 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,598 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,598 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,616 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,635 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,694 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,694 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,712 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,730 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,788 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,791 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,809 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,828 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,887 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,888 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,906 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,925 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,981 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:53,995 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,013 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,074 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,077 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,095 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,113 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,169 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,169 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,190 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,209 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,263 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,279 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,297 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,357 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,358 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,379 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,397 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,453 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,468 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,486 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,551 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,552 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,570 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,589 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,651 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,651 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,670 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,688 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,750 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,753 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,772 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,790 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,847 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,848 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,866 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,883 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,940 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,943 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,961 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:54,979 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,060 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,061 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,080 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,099 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,157 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,161 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,179 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,196 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,256 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,259 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,277 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,295 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,351 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,352 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,372 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,390 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,447 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,447 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,467 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,486 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,543 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,543 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,561 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,579 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,639 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,639 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,658 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,676 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,744 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,757 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,776 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,834 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,856 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,873 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,875 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,935 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,954 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,971 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:55,973 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,036 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,055 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,072 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,074 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,147 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,165 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,168 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,234 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,254 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,269 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,272 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,332 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,352 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,371 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,371 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,433 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,452 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,469 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,470 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,546 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,564 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,632 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,632 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,650 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,668 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,730 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,731 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,751 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,770 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,834 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,834 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,854 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,872 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,929 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,929 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,950 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:56,968 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,026 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,027 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,046 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,064 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,119 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,121 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,140 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,210 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,214 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,228 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,246 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,311 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,311 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,329 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,397 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,401 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,416 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,434 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,498 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,499 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,521 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,539 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,593 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,607 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,625 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,686 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,686 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,704 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,723 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,778 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,792 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,811 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,873 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,874 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,892 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,961 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,965 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,980 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:57,998 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,061 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,061 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,082 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,100 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,161 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,162 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,180 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,253 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,254 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,273 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,292 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,350 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,350 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,369 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,388 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,447 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,448 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,466 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,484 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,542 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,543 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,563 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,581 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,643 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,644 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,662 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,680 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,736 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,740 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,758 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,776 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,834 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,853 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,869 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,929 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,948 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,966 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:58,968 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,032 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,050 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,069 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,069 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,131 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,153 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,169 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,172 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,229 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,249 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,263 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,325 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,344 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,360 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,362 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,415 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,437 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,453 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,455 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,512 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,533 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,550 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,551 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,609 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,628 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,644 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,646 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,701 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,720 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,736 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,738 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,793 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,815 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,832 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,833 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,890 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,909 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,928 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,929 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:17:59,993 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,011 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,028 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,029 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,087 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,106 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,123 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,125 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,181 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,201 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,216 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,271 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,290 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,309 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,310 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,374 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,393 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,407 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,411 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,474 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,493 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,510 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,511 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,574 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,593 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,608 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,611 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,672 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,693 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,709 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,711 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,770 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,790 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,806 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,808 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,870 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,891 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,908 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,909 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,968 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:00,987 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,003 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,005 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,062 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,083 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,097 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,100 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,158 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,179 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,196 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,197 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,254 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,275 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,292 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,293 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,351 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,370 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,386 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,388 - INFO - End of video file reached
2025-11-24 18:18:01,441 - INFO - Video capture loop ended
2025-11-24 18:18:01,445 - INFO - Video thread started with source: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:18:01,455 - INFO - ✓ Video file opened: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:18:01,464 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,480 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,482 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,540 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,561 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,577 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,579 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,635 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,655 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,672 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,729 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,749 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,768 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,769 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,826 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,845 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,861 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,863 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,919 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,938 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,955 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:01,957 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,018 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,036 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,055 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,055 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,115 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,137 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,154 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,155 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,217 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,236 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,253 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,255 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,316 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,337 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,354 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,356 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,415 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,438 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,454 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,456 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,518 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,537 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,554 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,555 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,614 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,633 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,651 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,651 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,711 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,730 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,746 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,747 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,805 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,825 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,843 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,844 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,906 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,925 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,941 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,943 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:02,999 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,019 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,036 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,038 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,137 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,155 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,157 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,217 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,237 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,252 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,255 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,309 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,331 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,347 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,348 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,409 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,430 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,445 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,506 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,525 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,541 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,543 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,606 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,625 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,641 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,643 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,708 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,727 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,743 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,745 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,801 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,822 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,839 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,840 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,899 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,918 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,937 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,938 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:03,999 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,020 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,037 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,039 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,100 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,121 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,137 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,139 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,202 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,221 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,238 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,239 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,295 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,315 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,332 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,333 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,393 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,411 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,428 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,429 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,484 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,503 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,519 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,522 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,578 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,601 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,618 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,620 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,677 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,698 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,715 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,716 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,777 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,797 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,812 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,814 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,869 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,891 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,907 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,909 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,973 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:04,992 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,007 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,010 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,084 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,103 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,107 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,171 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,191 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,207 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,210 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,279 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,297 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,299 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,364 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,385 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,459 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,461 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,482 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,500 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,566 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,566 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,585 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,604 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,667 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,668 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,686 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,705 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,763 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,764 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,782 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,800 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,859 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,862 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,879 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,897 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,957 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,958 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,980 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:05,998 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,054 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,058 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,074 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,093 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,148 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,149 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,170 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,189 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,244 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,245 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,264 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,282 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,339 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,339 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,358 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,377 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,439 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,442 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,461 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,479 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,543 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,544 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,561 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,579 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,634 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,637 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,655 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,674 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,733 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,733 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,751 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,770 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,831 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,832 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,850 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,868 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,933 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,934 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:06,953 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,023 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,027 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,045 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,063 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,126 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,130 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,148 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,166 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,230 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,233 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,251 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,269 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,330 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,333 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,350 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,369 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,431 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,433 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,450 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,468 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,537 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,537 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,556 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,575 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,638 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,652 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,671 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,729 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,732 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,749 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,767 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,825 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,828 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,847 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,865 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,922 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,922 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,943 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:07,962 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,018 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,018 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,040 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,059 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,111 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,128 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,146 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,207 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,207 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,226 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,244 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,298 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,298 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,316 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,334 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,399 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,402 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,419 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,438 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,504 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,504 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,523 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,542 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,605 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,605 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,624 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,642 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,698 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,701 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,720 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,738 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,792 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,793 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,812 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,830 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,892 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,893 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,911 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,930 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,988 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:08,988 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,007 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,025 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,084 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,097 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,116 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,180 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,181 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,199 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,217 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,274 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,274 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,295 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,313 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,374 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,374 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,392 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,410 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,466 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,469 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,487 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,506 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,564 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,581 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,599 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,659 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,660 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,681 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,699 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,756 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,759 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,777 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,795 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,851 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,854 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,872 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,890 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,946 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,946 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,964 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:09,982 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,041 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,041 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,060 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,078 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,136 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,137 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,156 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,224 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,229 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,244 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,262 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,320 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,324 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,339 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,357 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,414 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,414 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,432 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,450 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,513 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,514 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,532 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,550 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,608 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,609 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,627 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,645 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,704 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,705 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,723 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,793 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,797 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,811 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,829 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,889 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,892 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,909 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,927 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,984 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:10,987 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,006 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,024 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,112 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,113 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,132 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,151 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,218 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,221 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,240 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,312 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,313 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,330 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,348 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,407 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,408 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,426 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,445 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,496 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,515 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,533 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,596 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,597 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,615 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,633 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,688 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,692 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,712 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,783 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,786 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,804 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,824 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,880 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,894 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,912 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,975 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,975 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:11,994 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,012 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,070 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,071 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,089 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,107 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,164 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,164 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,182 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,200 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,263 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,263 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,282 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,300 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,355 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,355 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,375 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,393 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,450 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,451 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,469 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,488 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,548 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,548 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,566 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,584 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,644 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,645 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,663 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,681 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,739 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,740 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,759 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,777 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,833 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,834 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,853 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,871 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,928 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,944 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:12,962 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,022 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,022 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,043 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,061 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,118 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,118 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,136 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,155 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,211 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,230 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,248 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,313 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,313 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,331 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,349 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,413 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,413 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,432 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,450 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,516 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,516 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,534 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,553 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,617 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,617 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,635 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,654 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,712 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,713 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,732 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,750 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,808 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,808 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,827 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,845 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,902 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,902 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,924 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,942 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:13,998 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,013 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,031 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,095 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,095 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,115 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,189 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,190 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,208 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,227 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,284 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,284 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,302 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,320 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,381 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,381 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,401 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,420 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,477 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,478 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,498 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,516 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,573 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,576 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,593 - INFO - End of video file reached
2025-11-24 18:18:14,595 - INFO - Video capture loop ended
2025-11-24 18:18:14,668 - INFO - Video thread started with source: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:18:14,668 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,677 - INFO - ✓ Video file opened: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:18:14,687 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,705 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,763 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,764 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,782 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,800 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,860 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,860 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,879 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,897 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,953 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,953 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,974 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:14,993 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,049 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,049 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,068 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,086 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,141 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,141 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,160 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,178 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,239 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,241 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,260 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,278 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,336 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,336 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,354 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,373 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,428 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,444 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,462 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,523 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,524 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,542 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,560 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,614 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,615 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,636 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,654 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,710 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,725 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,743 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,803 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,803 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,822 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,840 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,898 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,911 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,928 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:15,994 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,012 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,029 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,030 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,087 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,106 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,122 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,124 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,179 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,200 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,217 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,218 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,272 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,292 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,309 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,310 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,370 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,391 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,407 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,409 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,472 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,491 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,508 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,510 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,581 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,599 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,601 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,659 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,680 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,694 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,698 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,751 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,773 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,790 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,791 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,850 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,868 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,883 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,886 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,946 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,964 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,980 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:16,982 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,042 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,060 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,076 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,078 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,135 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,156 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,173 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,175 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,229 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,250 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,267 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,268 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,325 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,346 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,362 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,364 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,418 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,441 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,456 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,513 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,536 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,552 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,611 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,632 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,649 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,650 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,708 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,729 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,746 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,747 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,808 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,826 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,843 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,844 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,902 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,920 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,937 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,939 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:17,994 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,015 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,032 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,033 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,095 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,114 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,130 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,132 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,191 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,209 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,226 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,228 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,281 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,303 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,321 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,322 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,377 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,395 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,413 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,413 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,472 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,493 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,507 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,512 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,570 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,591 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,608 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,610 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,670 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,688 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,704 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,707 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,781 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,799 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,803 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,870 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,890 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,906 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,908 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,967 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:18,990 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,006 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,008 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,070 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,090 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,105 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,108 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,201 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,221 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,239 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,240 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,311 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,333 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,349 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,351 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,413 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,433 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,449 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,451 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,517 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,536 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,552 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,554 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,615 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,636 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,653 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,655 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,716 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,736 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,750 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,807 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,828 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,844 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,847 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,899 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,921 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,937 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,940 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:19,995 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,013 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,030 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,031 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,093 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,115 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,131 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,134 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,207 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,225 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,243 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,244 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,303 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,324 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,340 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,342 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,398 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,417 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,433 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,435 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,494 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,512 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,528 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,530 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,585 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,607 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,623 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,626 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,681 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,702 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,719 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,720 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,776 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,798 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,814 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,816 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,878 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,898 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,915 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,916 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,974 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:20,995 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,012 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,013 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,067 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,089 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,106 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,162 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,183 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,200 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,202 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,262 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,281 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,297 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,299 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,360 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,379 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,395 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,397 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,460 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,479 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,495 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,497 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,554 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,572 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,589 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,591 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,651 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,672 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,688 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,691 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,754 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,773 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,790 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,793 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,870 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,888 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,891 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,952 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,974 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,989 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:21,992 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,053 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,075 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,091 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,093 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,149 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,168 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,187 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,188 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,245 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,263 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,281 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,282 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,343 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,364 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,381 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,382 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,447 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,466 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,482 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,483 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,548 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,566 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,582 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,583 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,649 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,667 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,683 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,685 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,742 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,764 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,780 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,782 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,844 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,862 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,878 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,880 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,939 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,958 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,974 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:22,976 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,036 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,056 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,069 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,128 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,148 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,165 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,166 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,223 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,244 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,261 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,264 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,323 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,341 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,357 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,360 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,430 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,448 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,450 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,516 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,534 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,552 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,608 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,627 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,645 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,646 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,704 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,724 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,742 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,743 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,805 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,827 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,843 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,845 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,900 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,922 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,938 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:23,999 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,022 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,040 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,041 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,100 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,122 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,139 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,141 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,203 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,225 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,242 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,245 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,359 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,377 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,383 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,443 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,462 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,480 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,481 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,549 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,567 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,584 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,586 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,652 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,672 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,688 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,749 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,768 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,785 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,786 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,848 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,869 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,885 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,887 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,951 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,974 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,990 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:24,992 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,077 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,093 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,095 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,155 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,174 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,193 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,193 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,258 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,277 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,293 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,295 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,360 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,379 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,395 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,397 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,459 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,480 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,497 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,498 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,563 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,582 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,598 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,600 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,665 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,684 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,703 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,704 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,769 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,789 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,806 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,807 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,861 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,879 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,896 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,897 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,968 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:25,986 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,003 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,005 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,071 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,090 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,107 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,108 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,172 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,191 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,208 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,210 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,287 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,305 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,308 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,370 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,392 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,404 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,410 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,474 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,493 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,509 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,511 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,576 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,594 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,611 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,612 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,676 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,698 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,716 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,716 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,776 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,794 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,810 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,812 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,867 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,888 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,905 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,907 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,979 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,997 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:26,999 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,065 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,083 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,100 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,102 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,162 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,183 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,196 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,267 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,286 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,302 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,305 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,369 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,388 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,404 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,407 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,481 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,499 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,501 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,564 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,582 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,599 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,600 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,660 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,679 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,695 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,696 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,760 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,779 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,797 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,798 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,864 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,885 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,902 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,903 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,967 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:27,990 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,007 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,007 - INFO - End of video file reached
2025-11-24 18:18:28,008 - INFO - Video capture loop ended
2025-11-24 18:18:28,071 - INFO - Video thread started with source: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:18:28,080 - INFO - ✓ Video file opened: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:18:28,090 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,107 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,109 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,170 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,192 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,205 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,266 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,286 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,302 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,305 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,361 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,381 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,398 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,399 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,456 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,474 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,491 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,493 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,557 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,575 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,591 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,594 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,650 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,670 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,686 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,688 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,748 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,767 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,784 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,786 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,849 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,870 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,887 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,889 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,950 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,972 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,988 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:28,991 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,047 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,069 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,086 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,088 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,150 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,173 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,186 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,191 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,250 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,269 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,286 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,288 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,347 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,365 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,382 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,383 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,441 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,462 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,478 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,479 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,537 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,556 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,573 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,575 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,647 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,665 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,668 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,726 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,747 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,763 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,765 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,826 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,847 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,863 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,865 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,928 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,947 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,964 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:29,965 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,030 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,048 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,065 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,066 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,132 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,152 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,170 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,171 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,233 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,255 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,272 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,274 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,345 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,363 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,380 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,381 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,435 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,455 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,471 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,473 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,532 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,551 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,568 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,569 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,628 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,646 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,663 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,664 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,734 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,752 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,769 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,771 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,835 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,856 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,869 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,931 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,949 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,965 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:30,967 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,021 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,043 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,059 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,061 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,117 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,138 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,151 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,209 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,229 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,246 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,247 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,321 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,342 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,356 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,361 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,426 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,444 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,460 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,462 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,522 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,542 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,560 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,560 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,615 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,636 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,653 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,654 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,712 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,730 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,747 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,748 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,808 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,828 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,845 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,846 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,899 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,918 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,936 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,937 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:31,998 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,016 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,035 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,035 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,089 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,112 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,129 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,130 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,189 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,208 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,224 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,226 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,283 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,303 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,320 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,322 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,376 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,397 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,414 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,415 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,471 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,492 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,510 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,512 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,607 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,625 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,629 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,693 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,712 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,728 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,730 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,799 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,818 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,833 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,837 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,909 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,927 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,930 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:32,988 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,007 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,023 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,025 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,088 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,109 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,125 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,128 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,196 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,214 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,231 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,232 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,302 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,321 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,337 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,339 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,401 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,422 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,436 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,491 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,512 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,528 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,530 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,589 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,608 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,624 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,626 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,679 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,700 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,717 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,718 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,784 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,803 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,822 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,823 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,895 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,914 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,931 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:33,932 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,001 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,023 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,040 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,042 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,107 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,125 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,141 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,143 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,196 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,217 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,234 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,235 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,295 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,314 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,330 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,333 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,404 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,423 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,425 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,483 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,505 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,521 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,523 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,588 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,607 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,622 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,625 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,686 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,705 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,722 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,723 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,805 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,824 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,840 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,842 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,911 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,931 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,946 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:34,949 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,011 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,032 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,048 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,050 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,119 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,141 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,155 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,159 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,219 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,237 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,254 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,255 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,310 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,330 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,347 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,348 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,404 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,425 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,443 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,444 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,500 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,521 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,540 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,540 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,595 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,613 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,630 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,631 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,689 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,712 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,724 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,787 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,805 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,822 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,823 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,878 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,897 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,913 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,915 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,974 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:35,992 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,009 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,010 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,067 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,088 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,105 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,107 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,161 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,179 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,196 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,197 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,263 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,282 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,298 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,299 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,356 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,377 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,394 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,395 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,450 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,470 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,486 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,488 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,557 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,575 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,579 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,633 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,651 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,669 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,670 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,731 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,752 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,769 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,770 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,824 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,845 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,862 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,863 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,920 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,939 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,956 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:36,957 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,027 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,045 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,048 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,102 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,122 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,138 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,141 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,215 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,233 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,233 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,299 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,321 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,337 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,339 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,405 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,425 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,438 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,497 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,515 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,532 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,533 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,593 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,614 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,630 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,631 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,689 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,708 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,726 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,726 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,784 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,803 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,820 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,821 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,879 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,897 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,915 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,915 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,980 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:37,998 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,015 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,017 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,073 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,092 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,108 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,110 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,168 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,186 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,202 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,204 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,274 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,293 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,295 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,356 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,374 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,390 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,392 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,448 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,466 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,482 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,485 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,544 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,563 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,577 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,631 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,650 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,669 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,670 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,731 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,749 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,766 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,768 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,825 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,844 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,862 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,863 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,927 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,949 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:38,962 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,019 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,040 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,054 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,112 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,132 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,149 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,150 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,209 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,231 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,247 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,249 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,303 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,321 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,339 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,341 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,394 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,413 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,431 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,432 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,492 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,510 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,526 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,528 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,585 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,604 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,620 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,622 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,677 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,695 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,712 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,713 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,773 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,792 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,807 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,810 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,866 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,884 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,900 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,902 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,960 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,979 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,995 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:39,996 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,050 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,069 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,085 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,087 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,143 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,162 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,180 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,180 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,243 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,264 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,281 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,282 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,341 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,361 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,376 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,379 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,437 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,459 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,475 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,476 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,534 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,555 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,568 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,574 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,670 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,688 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,690 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,746 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,766 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,784 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,784 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,843 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,862 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,880 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,882 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,942 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,963 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:40,980 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,039 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,057 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,075 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,128 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,128 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,150 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,168 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,223 - INFO - End of video file reached
2025-11-24 18:18:41,224 - INFO - Video capture loop ended
2025-11-24 18:18:41,224 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,227 - INFO - Video thread started with source: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:18:41,236 - INFO - ✓ Video file opened: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:18:41,245 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,263 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,320 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,323 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,341 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,360 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,413 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,413 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,434 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,453 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,509 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,523 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,541 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,600 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,601 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,620 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,638 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,697 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,697 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,715 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,733 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,792 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,795 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,812 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,830 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,885 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,887 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,905 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,924 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,979 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,980 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:41,998 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,016 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,070 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,071 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,089 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,108 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,164 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,167 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,185 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,203 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,262 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,266 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,283 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,301 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,357 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,359 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,376 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,394 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,472 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,475 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,493 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,511 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,579 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,580 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,598 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,616 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,670 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,671 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,692 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,710 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,767 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,768 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,786 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,805 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,860 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,863 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,881 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,899 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,957 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,957 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,975 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:42,993 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,049 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,049 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,067 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,086 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,143 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,143 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,161 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,180 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,237 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,239 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,258 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,276 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,328 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,331 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,346 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,364 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,422 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,422 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,443 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,460 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,514 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,515 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,532 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,550 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,609 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,610 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,628 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,646 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,710 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,711 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,729 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,747 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,801 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,802 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,822 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,841 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,897 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,897 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,915 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,933 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,997 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:43,998 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,016 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,035 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,099 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,103 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,120 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,138 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,196 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,199 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,217 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,236 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,296 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,296 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,314 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,333 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,388 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,391 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,409 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,427 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,488 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,491 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,509 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,527 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,584 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,584 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,603 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,621 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,681 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,681 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,702 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,721 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,776 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,780 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,798 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,816 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,873 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,873 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,894 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,912 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,969 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,969 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:44,987 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,006 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,065 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,065 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,083 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,102 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,164 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,166 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,185 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,203 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,258 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,261 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,278 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,296 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,355 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,356 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,374 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,393 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,449 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,449 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,467 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,485 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,542 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,542 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,560 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,578 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,631 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,631 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,653 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,671 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,731 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,731 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,752 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,825 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,826 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,845 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,863 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,921 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,921 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,942 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:45,960 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,016 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,017 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,036 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,113 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,116 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,134 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,154 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,222 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,223 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,245 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,263 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,320 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,323 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,342 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,360 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,413 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,418 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,435 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,453 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,511 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,511 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,529 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,547 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,600 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,604 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,623 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,641 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,693 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,694 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,715 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,733 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,795 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,795 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,813 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,831 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,887 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,887 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,906 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,924 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,980 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:46,982 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,000 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,018 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,079 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,080 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,098 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,116 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,174 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,177 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,195 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,213 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,269 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,272 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,291 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,309 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,361 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,364 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,382 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,400 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,460 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,461 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,479 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,498 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,555 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,555 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,574 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,592 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,645 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,645 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,667 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,685 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,741 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,744 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,763 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,781 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,842 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,843 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,863 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,931 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,931 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,953 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:47,971 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,025 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,026 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,044 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,062 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,120 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,121 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,139 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,157 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,215 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,235 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,308 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,312 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,330 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,348 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,402 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,406 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,423 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,442 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,526 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,526 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,546 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,564 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,616 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,634 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,652 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,713 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,713 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,732 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,750 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,812 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,812 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,833 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,853 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,910 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,923 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:48,942 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,001 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,003 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,021 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,040 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,095 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,095 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,113 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,131 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,188 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,189 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,207 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,225 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,280 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,281 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,299 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,317 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,380 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,380 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,400 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,419 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,477 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,477 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,495 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,514 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,569 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,572 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,591 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,609 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,661 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,665 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,683 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,701 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,755 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,774 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,788 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,792 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,851 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,873 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,889 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,891 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,948 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,966 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,983 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:49,984 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,041 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,060 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,077 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,078 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,138 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,157 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,173 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,225 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,243 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,261 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,264 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,319 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,338 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,357 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,357 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,417 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,435 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,452 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,453 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,511 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,530 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,546 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,548 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,605 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,624 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,640 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,642 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,698 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,716 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,732 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,734 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,793 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,811 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,827 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,829 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,889 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,908 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,925 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,926 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,980 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:50,998 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,015 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,016 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,073 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,092 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,109 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,110 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,167 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,186 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,203 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,204 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,263 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,282 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,298 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,300 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,360 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,378 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,395 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,396 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,449 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,470 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,487 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,488 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,542 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,563 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,579 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,581 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,633 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,655 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,672 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,673 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,731 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,749 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,766 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,767 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,821 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,842 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,859 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,860 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,921 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,943 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,959 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:51,961 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,014 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,035 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,052 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,054 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,107 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,128 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,145 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,146 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,202 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,223 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,239 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,241 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,296 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,314 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,331 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,332 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,396 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,415 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,432 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,433 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,492 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,510 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,527 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,528 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,584 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,604 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,618 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,678 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,698 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,712 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,771 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,792 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,806 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,872 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,891 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,908 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,909 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,965 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,984 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:52,999 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,001 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,060 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,079 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,095 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,096 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,153 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,172 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,189 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,191 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,252 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,273 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,290 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,291 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,351 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,369 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,387 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,389 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,444 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,464 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,481 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,482 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,547 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,567 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,586 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,587 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,652 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,673 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,690 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,692 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,750 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,769 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,785 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,787 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,863 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,880 - INFO - End of video file reached
2025-11-24 18:18:53,881 - INFO - Video capture loop ended
2025-11-24 18:18:53,884 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,956 - INFO - Video thread started with source: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:18:53,965 - INFO - ✓ Video file opened: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:18:53,975 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,991 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:53,993 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,053 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,074 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,092 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,093 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,156 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,175 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,191 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,193 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,254 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,273 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,288 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,350 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,373 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,389 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,392 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,467 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,486 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,490 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,560 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,579 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,597 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,599 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,664 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,683 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,701 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,702 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,763 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,784 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,801 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,802 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,869 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,888 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,904 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,907 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,977 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:54,995 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,064 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,064 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,082 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,100 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,155 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,157 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,175 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,193 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,247 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,250 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,270 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,346 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,351 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,369 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,387 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,450 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,450 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,468 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,486 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,539 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,540 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,559 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,577 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,639 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,641 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,658 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,676 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,732 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,732 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,753 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,772 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,839 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,840 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,858 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,876 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,932 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,936 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,954 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:55,974 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,032 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,049 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,067 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,134 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,139 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,157 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,176 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,238 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,252 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,270 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,336 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,336 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,358 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,377 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,440 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,443 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,460 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,479 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,545 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,546 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,564 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,583 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,687 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,699 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,718 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,785 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,785 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,804 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,822 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,883 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,883 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,907 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,925 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,984 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:56,986 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,003 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,021 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,086 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,086 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,104 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,123 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,179 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,182 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,200 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,271 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,275 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,290 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,308 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,372 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,372 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,390 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,409 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,467 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,467 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,485 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,503 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,568 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,568 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,586 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,605 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,664 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,665 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,683 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,701 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,758 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,758 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,780 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,798 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,864 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,865 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,883 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,901 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,964 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,964 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:57,982 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,000 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,058 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,059 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,079 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,097 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,155 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,156 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,176 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,194 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,252 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,252 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,270 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,288 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,344 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,347 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,365 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,383 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,440 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,441 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,462 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,480 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,540 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,540 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,562 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,580 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,644 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,646 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,665 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,683 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,747 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,747 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,768 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,786 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,850 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,854 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,873 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,892 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,951 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,955 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,973 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:58,992 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,054 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,055 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,073 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,148 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,153 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,167 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,186 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,247 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,249 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,269 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,288 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,346 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,347 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,365 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,383 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,446 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,448 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,466 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,484 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,549 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,550 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,569 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,587 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,648 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,651 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,670 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,689 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,757 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,757 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,777 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,853 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,855 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,877 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,895 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,955 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,955 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,974 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:18:59,992 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,053 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,054 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,075 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,093 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,155 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,155 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,175 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,193 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,252 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,253 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,274 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,293 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,351 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,351 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,370 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,388 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,444 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,445 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,466 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,484 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,548 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,548 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,567 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,586 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,645 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,659 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,677 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,742 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,743 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,762 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,781 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,840 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,840 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,858 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,876 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,939 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,939 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,960 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:00,979 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,034 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,038 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,056 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,075 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,134 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,137 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,155 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,174 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,231 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,245 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,263 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,326 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,329 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,347 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,365 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,424 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,428 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,443 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,462 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,520 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,521 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,542 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,560 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,615 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,616 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,637 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,656 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,714 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,714 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,733 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,751 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,807 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,808 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,828 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,846 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,903 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,903 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,924 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:01,942 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,011 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,011 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,077 - INFO - Video thread started with source: Camera
2025-11-24 18:19:02,078 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,079 - ERROR - ❌ No camera found!
2025-11-24 18:19:02,096 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,113 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,114 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,180 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,183 - INFO - Video thread started with source: Camera
2025-11-24 18:19:02,184 - ERROR - ❌ No camera found!
2025-11-24 18:19:02,202 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,218 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,220 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,285 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,285 - INFO - Video thread started with source: Camera
2025-11-24 18:19:02,287 - ERROR - ❌ No camera found!
2025-11-24 18:19:02,305 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,320 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,324 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,384 - INFO - Video thread started with source: Camera
2025-11-24 18:19:02,385 - ERROR - ❌ No camera found!
2025-11-24 18:19:02,399 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,417 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,420 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,482 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,484 - INFO - Video thread started with source: Camera
2025-11-24 18:19:02,485 - ERROR - ❌ No camera found!
2025-11-24 18:19:02,503 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,519 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,521 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,579 - INFO - Video thread started with source: Camera
2025-11-24 18:19:02,580 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,581 - ERROR - ❌ No camera found!
2025-11-24 18:19:02,599 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,615 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,616 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,681 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,681 - INFO - Video thread started with source: Camera
2025-11-24 18:19:02,682 - ERROR - ❌ No camera found!
2025-11-24 18:19:02,699 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,715 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,717 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,782 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,784 - INFO - Video thread started with source: Camera
2025-11-24 18:19:02,785 - ERROR - ❌ No camera found!
2025-11-24 18:19:02,802 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,819 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,820 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,885 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,885 - INFO - Video thread started with source: Camera
2025-11-24 18:19:02,886 - ERROR - ❌ No camera found!
2025-11-24 18:19:02,905 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,921 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,982 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:02,985 - INFO - Video thread started with source: Camera
2025-11-24 18:19:02,987 - ERROR - ❌ No camera found!
2025-11-24 18:19:03,001 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,020 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,020 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,083 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,086 - INFO - Video thread started with source: Camera
2025-11-24 18:19:03,087 - ERROR - ❌ No camera found!
2025-11-24 18:19:03,104 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,119 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,123 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,178 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,182 - INFO - Video thread started with source: Camera
2025-11-24 18:19:03,183 - ERROR - ❌ No camera found!
2025-11-24 18:19:03,197 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,214 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,215 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,281 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,284 - INFO - Video thread started with source: Camera
2025-11-24 18:19:03,285 - ERROR - ❌ No camera found!
2025-11-24 18:19:03,301 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,318 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,319 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,385 - INFO - Video thread started with source: Camera
2025-11-24 18:19:03,386 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,387 - ERROR - ❌ No camera found!
2025-11-24 18:19:03,406 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,422 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,425 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,488 - INFO - Video thread started with source: Camera
2025-11-24 18:19:03,489 - ERROR - ❌ No camera found!
2025-11-24 18:19:03,504 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,523 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,524 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,588 - INFO - Video thread started with source: Camera
2025-11-24 18:19:03,589 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,590 - ERROR - ❌ No camera found!
2025-11-24 18:19:03,608 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,625 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,627 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,688 - INFO - Video thread started with source: Camera
2025-11-24 18:19:03,689 - ERROR - ❌ No camera found!
2025-11-24 18:19:03,703 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,722 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,724 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,786 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,787 - INFO - Video thread started with source: Camera
2025-11-24 18:19:03,787 - ERROR - ❌ No camera found!
2025-11-24 18:19:03,806 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,822 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,825 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,885 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,888 - INFO - Video thread started with source: Camera
2025-11-24 18:19:03,890 - ERROR - ❌ No camera found!
2025-11-24 18:19:03,906 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,922 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,925 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,989 - INFO - Video thread started with source: Camera
2025-11-24 18:19:03,990 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:03,990 - ERROR - ❌ No camera found!
2025-11-24 18:19:04,008 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,026 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,027 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,090 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,091 - INFO - Video thread started with source: Camera
2025-11-24 18:19:04,092 - ERROR - ❌ No camera found!
2025-11-24 18:19:04,109 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,127 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,128 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,189 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,191 - INFO - Video thread started with source: Camera
2025-11-24 18:19:04,192 - ERROR - ❌ No camera found!
2025-11-24 18:19:04,209 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,224 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,227 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,284 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,287 - INFO - Video thread started with source: Camera
2025-11-24 18:19:04,288 - ERROR - ❌ No camera found!
2025-11-24 18:19:04,302 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,320 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,320 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,383 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,383 - INFO - Video thread started with source: Camera
2025-11-24 18:19:04,384 - ERROR - ❌ No camera found!
2025-11-24 18:19:04,401 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,417 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,420 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,480 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,481 - INFO - Video thread started with source: Camera
2025-11-24 18:19:04,482 - ERROR - ❌ No camera found!
2025-11-24 18:19:04,500 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,516 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,518 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,579 - INFO - Video thread started with source: Camera
2025-11-24 18:19:04,579 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,580 - ERROR - ❌ No camera found!
2025-11-24 18:19:04,597 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,614 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,615 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,676 - INFO - Video thread started with source: Camera
2025-11-24 18:19:04,676 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,677 - ERROR - ❌ No camera found!
2025-11-24 18:19:04,695 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,711 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,713 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,772 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,774 - INFO - Video thread started with source: Camera
2025-11-24 18:19:04,775 - ERROR - ❌ No camera found!
2025-11-24 18:19:04,792 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,810 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,908 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,912 - INFO - Video thread started with source: Camera
2025-11-24 18:19:04,913 - ERROR - ❌ No camera found!
2025-11-24 18:19:04,927 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,946 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:04,946 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,011 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,012 - INFO - Video thread started with source: Camera
2025-11-24 18:19:05,013 - ERROR - ❌ No camera found!
2025-11-24 18:19:05,030 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,047 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,048 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,111 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,113 - INFO - Video thread started with source: Camera
2025-11-24 18:19:05,114 - ERROR - ❌ No camera found!
2025-11-24 18:19:05,131 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,149 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,149 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,213 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,215 - INFO - Video thread started with source: Camera
2025-11-24 18:19:05,216 - ERROR - ❌ No camera found!
2025-11-24 18:19:05,232 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,250 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,251 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,314 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,316 - INFO - Video thread started with source: Camera
2025-11-24 18:19:05,317 - ERROR - ❌ No camera found!
2025-11-24 18:19:05,334 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,351 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,353 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,415 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,417 - INFO - Video thread started with source: Camera
2025-11-24 18:19:05,418 - ERROR - ❌ No camera found!
2025-11-24 18:19:05,435 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,450 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,453 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,516 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,517 - INFO - Video thread started with source: Camera
2025-11-24 18:19:05,518 - ERROR - ❌ No camera found!
2025-11-24 18:19:05,535 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,552 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,553 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,614 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,617 - INFO - Video thread started with source: Camera
2025-11-24 18:19:05,618 - ERROR - ❌ No camera found!
2025-11-24 18:19:05,633 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,650 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,651 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,709 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,712 - INFO - Video thread started with source: Camera
2025-11-24 18:19:05,713 - ERROR - ❌ No camera found!
2025-11-24 18:19:05,728 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,744 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,746 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,808 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,808 - INFO - Video thread started with source: Camera
2025-11-24 18:19:05,809 - ERROR - ❌ No camera found!
2025-11-24 18:19:05,826 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,842 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,844 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,901 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,903 - INFO - Video thread started with source: Camera
2025-11-24 18:19:05,903 - ERROR - ❌ No camera found!
2025-11-24 18:19:05,920 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,936 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,939 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,996 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:05,997 - INFO - Video thread started with source: Camera
2025-11-24 18:19:05,998 - ERROR - ❌ No camera found!
2025-11-24 18:19:06,015 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,032 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,033 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,094 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,096 - INFO - Video thread started with source: Camera
2025-11-24 18:19:06,097 - ERROR - ❌ No camera found!
2025-11-24 18:19:06,114 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,131 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,132 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,197 - INFO - Video thread started with source: Camera
2025-11-24 18:19:06,197 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,198 - ERROR - ❌ No camera found!
2025-11-24 18:19:06,216 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,233 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,234 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,300 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,302 - INFO - Video thread started with source: Camera
2025-11-24 18:19:06,303 - ERROR - ❌ No camera found!
2025-11-24 18:19:06,320 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,339 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,340 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,401 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,402 - INFO - Video thread started with source: Camera
2025-11-24 18:19:06,404 - ERROR - ❌ No camera found!
2025-11-24 18:19:06,420 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,439 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,440 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,497 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,499 - INFO - Video thread started with source: Camera
2025-11-24 18:19:06,500 - ERROR - ❌ No camera found!
2025-11-24 18:19:06,517 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,534 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,535 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,594 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,596 - INFO - Video thread started with source: Camera
2025-11-24 18:19:06,597 - ERROR - ❌ No camera found!
2025-11-24 18:19:06,614 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,631 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,632 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,693 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,696 - INFO - Video thread started with source: Camera
2025-11-24 18:19:06,697 - ERROR - ❌ No camera found!
2025-11-24 18:19:06,714 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,730 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,732 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,795 - INFO - Video thread started with source: Camera
2025-11-24 18:19:06,797 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,797 - ERROR - ❌ No camera found!
2025-11-24 18:19:06,815 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,832 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,833 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,895 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,895 - INFO - Video thread started with source: Camera
2025-11-24 18:19:06,896 - ERROR - ❌ No camera found!
2025-11-24 18:19:06,913 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,930 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,931 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,987 - INFO - Video thread started with source: Camera
2025-11-24 18:19:06,987 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:06,989 - ERROR - ❌ No camera found!
2025-11-24 18:19:07,008 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:07,024 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:07,026 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:07,081 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:07,083 - INFO - Video thread started with source: Camera
2025-11-24 18:19:07,084 - ERROR - ❌ No camera found!
2025-11-24 18:19:07,099 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:07,117 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:07,117 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:07,177 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:07,180 - INFO - Video thread started with source: Camera
2025-11-24 18:19:07,182 - ERROR - ❌ No camera found!
2025-11-24 18:19:07,196 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:07,213 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:07,215 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:07,273 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:07,275 - INFO - Video thread started with source: Camera
2025-11-24 18:19:07,276 - ERROR - ❌ No camera found!
2025-11-24 18:19:07,293 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:07,310 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:07,310 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:07,368 - INFO - End of video file reached
2025-11-24 18:19:07,371 - INFO - Video capture loop ended
2025-11-24 18:19:07,371 - INFO - Video thread started with source: Camera
2025-11-24 18:19:07,373 - ERROR - ❌ No camera found!
2025-11-24 18:19:07,406 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:07,467 - INFO - Video thread started with source: Camera
2025-11-24 18:19:07,468 - ERROR - ❌ No camera found!
2025-11-24 18:19:07,503 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:07,561 - INFO - Video thread started with source: Camera
2025-11-24 18:19:07,562 - ERROR - ❌ No camera found!
2025-11-24 18:19:07,597 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:07,656 - INFO - Video thread started with source: Camera
2025-11-24 18:19:07,657 - ERROR - ❌ No camera found!
2025-11-24 18:19:07,769 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:07,839 - INFO - Video file uploaded: assets/temp_videos/Screen Recording 2025-11-24 at 6.07.31 PM.mov
2025-11-24 18:19:07,840 - INFO - Video thread started with source: assets/temp_videos/Screen Recording 2025-11-24 at 6.07.31 PM.mov
2025-11-24 18:19:07,857 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:07,867 - INFO - ✓ Video file opened: assets/temp_videos/Screen Recording 2025-11-24 at 6.07.31 PM.mov
2025-11-24 18:19:08,001 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:08,029 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:08,113 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:08,155 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:08,174 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:08,226 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:08,227 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:08,326 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:08,340 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:08,387 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:08,410 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:08,436 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:08,534 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:08,541 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:08,602 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:08,638 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:08,649 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:08,695 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:08,755 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:08,810 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:08,852 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:08,864 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:08,910 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:08,965 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:09,030 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:09,067 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:09,079 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:09,126 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:09,186 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:09,250 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:09,287 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:09,304 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:09,355 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:09,418 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:09,482 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:09,518 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:09,529 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:09,578 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:09,633 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:09,697 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:09,732 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:09,745 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:09,791 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:09,843 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:09,910 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:09,913 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:09,960 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:09,983 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:10,010 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:10,130 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:10,132 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:10,178 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:10,202 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:10,228 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:10,344 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:10,345 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:10,392 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:10,414 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:10,496 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:10,567 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:10,568 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:10,619 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:10,640 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:10,670 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:10,795 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:10,795 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:10,842 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:10,865 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:10,892 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:11,029 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:11,030 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:11,076 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:11,100 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:11,124 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:11,246 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:11,247 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:11,294 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:11,317 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:11,343 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:11,462 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:11,463 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:11,509 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:11,533 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:11,558 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:11,672 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:11,681 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:11,727 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:11,750 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:11,775 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:11,893 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:11,893 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:11,941 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:11,963 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:12,048 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:12,103 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:12,117 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:12,174 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:12,176 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:12,278 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:12,340 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:12,341 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:12,387 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:12,411 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:12,488 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:12,556 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:12,558 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:12,604 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:12,627 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:12,654 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:12,768 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:12,770 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:12,815 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:12,839 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:12,865 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:12,985 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:12,986 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:13,033 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:13,056 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:13,134 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:13,202 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:13,204 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:13,250 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:13,274 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:13,301 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:13,419 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:13,420 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:13,472 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:13,490 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:13,578 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:13,643 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:13,643 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:13,693 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:13,714 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:13,742 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:13,868 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:13,869 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:13,916 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:13,939 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:13,965 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:14,073 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:14,086 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:14,135 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:14,143 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:14,231 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:14,299 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:14,300 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:14,348 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:14,371 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:14,398 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:14,518 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:14,518 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:14,566 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:14,589 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:14,619 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:14,747 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:14,749 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:14,799 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:14,819 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:14,908 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:14,980 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:14,980 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:15,031 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:15,051 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:15,141 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:15,214 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:15,214 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:15,263 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:15,285 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:15,311 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:15,429 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:15,430 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:15,476 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:15,499 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:15,525 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:15,644 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:15,644 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:15,690 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:15,714 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:15,793 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:15,854 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:15,861 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:15,908 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:15,931 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:16,027 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:16,069 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:16,116 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:16,151 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:16,162 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:16,261 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:16,268 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:16,333 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:16,369 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:16,381 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:16,430 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:16,491 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:16,552 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:16,588 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:16,599 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:16,648 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:16,706 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:16,772 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:16,792 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:16,821 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:16,916 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:16,917 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:16,985 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:17,022 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:17,032 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:17,129 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:17,133 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:17,197 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:17,234 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:17,246 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:17,295 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:17,350 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:17,417 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:17,453 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:17,465 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:17,516 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:17,579 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:17,639 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:17,674 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:17,686 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:17,737 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:17,799 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:17,862 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:17,898 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:17,909 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:17,957 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:18,016 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:18,081 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:18,117 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:18,128 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:18,176 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:18,236 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:18,297 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:18,333 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:18,345 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:18,452 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:18,456 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:18,526 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:18,545 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:18,577 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:18,615 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:18,626 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:18,755 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:18,757 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:18,809 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:18,827 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:18,921 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:18,994 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:18,995 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:19,042 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:19,065 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:19,093 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:19,218 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:19,220 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:19,269 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:19,290 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:19,375 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:19,443 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:19,443 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:19,490 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:19,514 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:19,541 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:19,660 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:19,660 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:19,706 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:19,730 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:19,754 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:19,863 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:19,877 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:19,923 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:19,932 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:20,021 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:20,092 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:20,092 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:20,142 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:20,163 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:20,194 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:20,316 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:20,358 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:20,395 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:20,409 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:20,512 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:20,520 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:20,584 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:20,621 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:20,632 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:20,732 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:20,741 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:20,805 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:20,841 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:20,852 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:20,902 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:20,960 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:21,022 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:21,058 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:21,071 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:21,177 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:21,184 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:21,249 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:21,287 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:21,298 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:21,345 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:21,408 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:21,468 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:21,503 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:21,514 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:21,562 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:21,621 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:21,685 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:21,721 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:21,734 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:21,782 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:21,839 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:21,900 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:21,937 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:21,947 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:21,994 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:22,055 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:22,116 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:22,151 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:22,162 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:22,210 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:22,267 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:22,332 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:22,369 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:22,382 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:22,430 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:22,492 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:22,555 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:22,576 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:22,604 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:22,695 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:22,703 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:22,765 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:22,801 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:22,812 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:22,915 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:22,917 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:22,983 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:23,003 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:23,032 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:23,124 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:23,126 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:23,192 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:23,229 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:23,240 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:23,288 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:23,345 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:23,406 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:23,442 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:23,456 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:23,506 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:23,563 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:23,623 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:23,635 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:23,681 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:23,705 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:23,792 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:23,867 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:23,867 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:23,915 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:23,938 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:23,965 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:24,056 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:24,091 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:24,128 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:24,139 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:24,189 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:24,243 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:24,309 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:24,344 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:24,356 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:24,404 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:24,457 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:24,523 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:24,559 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:24,570 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:24,667 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:24,676 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:24,738 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:24,772 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:24,785 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:24,834 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:24,898 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:24,965 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:25,001 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:25,014 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:25,067 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:25,132 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:25,195 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:25,230 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:25,240 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:25,288 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:25,344 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:25,406 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:25,427 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:25,455 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:25,551 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:25,555 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:25,610 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:25,667 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:25,669 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:25,716 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:25,776 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:25,835 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:25,871 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:25,882 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:25,931 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:25,989 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:26,046 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:26,082 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:26,092 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:26,141 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:26,200 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:26,266 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:26,285 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:26,320 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:26,419 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:26,420 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:26,486 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:26,523 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:26,532 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:26,579 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:26,637 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:26,700 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:26,736 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:26,746 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:26,848 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:26,856 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:26,917 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:26,954 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:26,966 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:27,015 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:27,078 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:27,139 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:27,176 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:27,188 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:27,236 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:27,293 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:27,358 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:27,393 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:27,406 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:27,512 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:27,515 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:27,583 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:27,620 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:27,632 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:27,681 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:27,740 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:27,801 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:27,837 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:27,848 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:27,945 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:27,948 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:28,018 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:28,054 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:28,066 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:28,112 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:28,173 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:28,234 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:28,272 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:28,284 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:28,334 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:28,397 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:28,456 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:28,492 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:28,503 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:28,555 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:28,614 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:28,685 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:28,687 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:28,738 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:28,758 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:28,845 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:28,915 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:28,916 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:28,962 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:28,985 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:29,010 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:29,117 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:29,131 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:29,179 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:29,186 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:29,278 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:29,346 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:29,347 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:29,393 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:29,417 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:29,443 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:29,555 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:29,569 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:29,619 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:29,625 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:29,716 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:29,787 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:29,788 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:29,834 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:29,858 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:29,885 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:30,003 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:30,005 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:30,051 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:30,075 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:30,099 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:30,216 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:30,218 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:30,265 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:30,289 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:30,363 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:30,434 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:30,436 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:30,482 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:30,506 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:30,529 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:30,648 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:30,649 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:30,695 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:30,719 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:30,744 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:30,853 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:30,867 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:30,916 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:30,923 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:31,022 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:31,098 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:31,098 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:31,148 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:31,170 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:31,198 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:31,317 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:31,317 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:31,365 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:31,390 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:31,416 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:31,537 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:31,537 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:31,583 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:31,608 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:31,633 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:31,743 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:31,757 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:31,803 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:31,812 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:31,902 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:31,970 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:31,972 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:32,020 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:32,041 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:32,070 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:32,191 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:32,199 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:32,244 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:32,268 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:32,294 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:32,416 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:32,416 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:32,463 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:32,486 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:32,514 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:32,632 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:32,634 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:32,682 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:32,706 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:32,735 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:32,863 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:32,865 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:32,913 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:32,934 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:33,019 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:33,086 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:33,088 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:33,132 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:33,157 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:33,182 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:33,303 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:33,303 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:33,351 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:33,372 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:33,455 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:33,512 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:33,526 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:33,573 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:33,581 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:33,671 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:33,738 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:33,740 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:33,786 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:33,811 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:33,891 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:33,960 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:33,962 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:34,007 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:34,032 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:34,108 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:34,175 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:34,177 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:34,223 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:34,246 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:34,272 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:34,381 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:34,392 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:34,433 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:34,470 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:34,481 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:34,601 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:34,603 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:34,649 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:34,673 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:34,699 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:34,814 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:34,822 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:34,867 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:34,892 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:34,916 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:35,047 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:35,049 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:35,099 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:35,119 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:35,150 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:35,278 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:35,278 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:35,323 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:35,348 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:35,421 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:35,488 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:35,490 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:35,535 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:35,560 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:35,633 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:35,700 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:35,702 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:35,749 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:35,772 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:35,801 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:35,918 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:35,928 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:35,975 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:35,998 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:36,083 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:36,143 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:36,158 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:36,205 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:36,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:36,306 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:36,372 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:36,375 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:36,419 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:36,456 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:36,466 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:36,584 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:36,586 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:36,632 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:36,656 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:36,680 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:36,795 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:36,804 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:36,851 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:36,874 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:36,953 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:37,020 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:37,020 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:37,068 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:37,092 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:37,117 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:37,241 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:37,241 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:37,287 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:37,311 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:37,337 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:37,447 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:37,456 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:37,506 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:37,528 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:37,556 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:37,665 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:37,680 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:37,725 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:37,740 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:37,775 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:37,899 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:37,901 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:37,945 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:37,971 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:38,041 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:38,083 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:38,116 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:38,163 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:38,178 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:38,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:38,332 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:38,333 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:38,377 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:38,402 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:38,423 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:38,539 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:38,541 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:38,584 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:38,620 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:38,630 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:38,749 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:38,749 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:38,795 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:38,819 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:38,821 - INFO - End of video file reached
2025-11-24 18:19:38,822 - INFO - Video capture loop ended
2025-11-24 18:19:38,897 - INFO - Video thread started with source: assets/temp_videos/Screen Recording 2025-11-24 at 6.07.31 PM.mov
2025-11-24 18:19:38,921 - INFO - ✓ Video file opened: assets/temp_videos/Screen Recording 2025-11-24 at 6.07.31 PM.mov
2025-11-24 18:19:38,969 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:39,003 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:39,041 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:39,060 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:39,159 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:39,197 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:39,221 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:39,273 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:39,275 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:39,377 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:39,428 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:39,443 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:39,489 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:39,497 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:39,582 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:39,649 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:39,651 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:39,698 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:39,722 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:39,747 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:39,865 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:39,867 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:39,916 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:39,937 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:39,965 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:40,070 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:40,084 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:40,136 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:40,144 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:40,247 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:40,311 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:40,311 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:40,359 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:40,382 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:40,410 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:40,535 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:40,535 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:40,587 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:40,608 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:40,730 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:40,793 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:40,794 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:40,840 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:40,864 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:40,889 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:41,007 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:41,009 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:41,056 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:41,079 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:41,155 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:41,224 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:41,225 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:41,269 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:41,294 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:41,319 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:41,433 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:41,434 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:41,482 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:41,505 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:41,530 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:41,649 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:41,649 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:41,696 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:41,719 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:41,796 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:41,867 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:41,869 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:41,915 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:41,938 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:42,015 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:42,086 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:42,087 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:42,134 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:42,158 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:42,183 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:42,289 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:42,301 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:42,347 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:42,362 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:42,397 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:42,514 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:42,515 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:42,560 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:42,584 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:42,610 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:42,723 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:42,724 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:42,771 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:42,794 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:42,821 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:42,938 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:42,939 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:42,984 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:43,009 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:43,035 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:43,155 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:43,155 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:43,200 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:43,225 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:43,250 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:43,364 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:43,365 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:43,413 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:43,436 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:43,462 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:43,579 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:43,584 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:43,630 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:43,654 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:43,681 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:43,807 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:43,808 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:43,857 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:43,877 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:43,910 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:44,032 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:44,032 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:44,083 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:44,103 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:44,192 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:44,229 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:44,263 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:44,299 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:44,313 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:44,362 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:44,426 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:44,487 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:44,508 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:44,535 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:44,632 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:44,635 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:44,702 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:44,739 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:44,750 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:44,846 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:44,855 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:44,916 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:44,953 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:44,964 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:45,013 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:45,065 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:45,134 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:45,135 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:45,180 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:45,205 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:45,228 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:45,347 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:45,348 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:45,393 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:45,418 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:45,441 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:45,557 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:45,558 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:45,604 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:45,628 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:45,654 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:45,770 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:45,771 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:45,817 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:45,841 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:45,923 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:45,992 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:45,992 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:46,039 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:46,064 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:46,088 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:46,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:46,214 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:46,262 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:46,283 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:46,313 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:46,423 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:46,436 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:46,486 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:46,495 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:46,580 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:46,649 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:46,651 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:46,698 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:46,721 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:46,749 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:46,859 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:46,874 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:46,921 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:46,928 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:46,969 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:47,063 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:47,080 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:47,142 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:47,145 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:47,193 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:47,261 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:47,325 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:47,361 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:47,376 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:47,426 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:47,490 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:47,550 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:47,586 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:47,601 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:47,652 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:47,718 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:47,781 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:47,818 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:47,836 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:47,943 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:47,946 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:48,016 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:48,018 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:48,068 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:48,088 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:48,122 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:48,226 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:48,240 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:48,287 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:48,301 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:48,338 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:48,452 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:48,462 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:48,503 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:48,541 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:48,553 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:48,676 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:48,676 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:48,723 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:48,746 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:48,775 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:48,896 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:48,897 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:48,945 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:48,967 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:48,995 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:49,113 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:49,115 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:49,163 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:49,184 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:49,213 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:49,332 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:49,332 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:49,380 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:49,403 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:49,429 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:49,549 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:49,549 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:49,595 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:49,619 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:49,644 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:49,761 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:49,761 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:49,806 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:49,840 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:49,912 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:49,982 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:49,982 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:50,036 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:50,054 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:50,089 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:50,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:50,213 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:50,260 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:50,283 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:50,309 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:50,425 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:50,427 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:50,473 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:50,496 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:50,523 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:50,642 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:50,642 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:50,689 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:50,713 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:50,739 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:50,862 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:50,869 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:50,918 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:50,940 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:50,970 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:51,103 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:51,104 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:51,150 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:51,174 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:51,200 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:51,325 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:51,325 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:51,371 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:51,395 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:51,422 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:51,540 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:51,542 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:51,588 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:51,612 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:51,637 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:51,747 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:51,760 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:51,807 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:51,830 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:51,857 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:51,978 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:51,979 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:52,023 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:52,060 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:52,073 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:52,184 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:52,195 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:52,241 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:52,264 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:52,342 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:52,403 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:52,417 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:52,465 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:52,472 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:52,513 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:52,632 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:52,633 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:52,678 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:52,702 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:52,728 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:52,849 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:52,849 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:52,896 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:52,919 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:52,946 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:53,066 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:53,068 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:53,116 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:53,138 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:53,167 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:53,295 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:53,297 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:53,342 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:53,367 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:53,440 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:53,509 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:53,509 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:53,557 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:53,578 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:53,607 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:53,697 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:53,756 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:53,793 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:53,810 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:53,910 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:53,914 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:53,981 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:54,018 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:54,030 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:54,078 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:54,138 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:54,198 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:54,233 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:54,244 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:54,342 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:54,345 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:54,412 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:54,448 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:54,460 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:54,509 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:54,574 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:54,632 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:54,668 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:54,679 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:54,726 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:54,780 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:54,848 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:54,883 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:54,894 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:54,942 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:55,011 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:55,036 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:55,094 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:55,102 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:55,150 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:55,257 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:55,257 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:55,320 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:55,342 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:55,371 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:55,418 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:55,476 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:55,540 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:55,575 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:55,586 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:55,637 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:55,694 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:55,750 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:55,796 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:55,808 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:55,855 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:55,917 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:55,972 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:56,015 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:56,025 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:56,075 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:56,137 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:56,195 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:56,232 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:56,243 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:56,291 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:56,349 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:56,404 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:56,445 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:56,456 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:56,507 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:56,562 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:56,620 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:56,656 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:56,667 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:56,718 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:56,775 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:56,839 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:56,875 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:56,886 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:56,986 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:56,992 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:57,054 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:57,090 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:57,100 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:57,148 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:57,207 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:57,264 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:57,300 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:57,313 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:57,409 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:57,419 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:57,479 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:57,515 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:57,527 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:57,576 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:57,640 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:57,701 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:57,738 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:57,750 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:57,797 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:57,858 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:57,920 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:57,955 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:57,965 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:58,013 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:58,075 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:58,134 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:58,170 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:58,182 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:58,229 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:58,287 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:58,351 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:58,386 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:58,396 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:58,443 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:58,505 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:58,560 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:58,605 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:58,620 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:58,671 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:58,737 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:58,800 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:58,836 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:58,852 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:58,960 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:58,963 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:59,032 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:59,069 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:59,085 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:59,194 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:59,194 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:59,268 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:59,290 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:59,320 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:59,359 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:59,427 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:59,498 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:59,499 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:59,546 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:59,569 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:59,598 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:59,721 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:59,721 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:59,767 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:59,791 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:59,816 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:59,924 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:59,937 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:59,986 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:19:59,993 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:00,082 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:00,152 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:00,154 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:00,200 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:00,224 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:00,247 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:00,366 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:00,366 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:00,412 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:00,436 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:00,461 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:00,581 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:00,582 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:00,629 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:00,653 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:00,736 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:00,805 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:00,806 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:00,855 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:00,877 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:00,907 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:01,032 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:01,034 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:01,083 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:01,105 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:01,190 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:01,260 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:01,260 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:01,307 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:01,331 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:01,405 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:01,473 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:01,475 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:01,521 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:01,544 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:01,623 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:01,693 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:01,695 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:01,740 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:01,766 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:01,791 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:01,911 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:01,911 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:01,958 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:01,982 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:02,008 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:02,130 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:02,132 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:02,178 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:02,202 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:02,229 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:02,359 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:02,359 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:02,410 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:02,430 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:02,511 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:02,582 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:02,584 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:02,634 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:02,655 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:02,743 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:02,814 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:02,816 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:02,865 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:02,888 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:02,917 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:03,040 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:03,042 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:03,090 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:03,112 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:03,143 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:03,269 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:03,271 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:03,316 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:03,340 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:03,365 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:03,473 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:03,487 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:03,537 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:03,543 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:03,587 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:03,702 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:03,712 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:03,759 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:03,783 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:03,810 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:03,932 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:03,934 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:03,979 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:04,003 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:04,030 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:04,136 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:04,150 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:04,200 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:04,208 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:04,298 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:04,358 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:04,372 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:04,420 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:04,427 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:04,521 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:04,582 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:04,582 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:04,635 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:04,651 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:04,684 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:04,803 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:04,804 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:04,850 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:04,874 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:04,899 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:05,007 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:05,021 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:05,069 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:05,077 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:05,167 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:05,236 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:05,236 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:05,285 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:05,308 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:05,383 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:05,442 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:05,451 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:05,498 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:05,522 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:05,632 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:05,705 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:05,705 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:05,752 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:05,776 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:05,801 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:05,922 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:05,923 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:05,968 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:05,993 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:06,071 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:06,140 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:06,142 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:06,187 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:06,211 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:06,287 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:06,354 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:06,356 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:06,401 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:06,425 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:06,451 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:06,567 - INFO - Video thread started with source: Camera
2025-11-24 18:20:06,568 - ERROR - ❌ No camera found!
2025-11-24 18:20:06,613 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:06,620 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:06,657 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:06,693 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:06,706 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:06,773 - INFO - Video thread started with source: Camera
2025-11-24 18:20:06,775 - ERROR - ❌ No camera found!
2025-11-24 18:20:06,790 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:06,824 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:06,839 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:06,888 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:06,893 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:06,988 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:06,988 - INFO - Video thread started with source: Camera
2025-11-24 18:20:06,992 - ERROR - ❌ No camera found!
2025-11-24 18:20:07,036 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:07,050 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:07,101 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:07,109 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:07,211 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:07,217 - INFO - Video thread started with source: Camera
2025-11-24 18:20:07,218 - ERROR - ❌ No camera found!
2025-11-24 18:20:07,280 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:07,281 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:07,329 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:07,352 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:07,379 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:07,434 - INFO - Video thread started with source: Camera
2025-11-24 18:20:07,435 - ERROR - ❌ No camera found!
2025-11-24 18:20:07,479 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:07,492 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:07,530 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:07,548 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:07,578 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:07,641 - INFO - Video thread started with source: Camera
2025-11-24 18:20:07,642 - ERROR - ❌ No camera found!
2025-11-24 18:20:07,686 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:07,696 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:07,738 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:07,766 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:07,788 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:07,854 - INFO - Video thread started with source: Camera
2025-11-24 18:20:07,855 - ERROR - ❌ No camera found!
2025-11-24 18:20:07,901 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:07,917 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:07,970 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:07,976 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:08,062 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:08,066 - INFO - Video thread started with source: Camera
2025-11-24 18:20:08,067 - ERROR - ❌ No camera found!
2025-11-24 18:20:08,110 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:08,127 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:08,174 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:08,180 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:08,273 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:08,278 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:08,278 - INFO - Video thread started with source: Camera
2025-11-24 18:20:08,279 - ERROR - ❌ No camera found!
2025-11-24 18:20:08,338 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:08,354 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:08,392 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:08,486 - INFO - Video thread started with source: Camera
2025-11-24 18:20:08,487 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:08,497 - ERROR - ❌ No camera found!
2025-11-24 18:20:08,498 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:08,561 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:08,576 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:08,613 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:08,698 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:08,703 - INFO - Video thread started with source: Camera
2025-11-24 18:20:08,704 - ERROR - ❌ No camera found!
2025-11-24 18:20:08,705 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:08,763 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:08,783 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:08,810 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:08,857 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:08,912 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:08,914 - INFO - Video thread started with source: Camera
2025-11-24 18:20:08,915 - ERROR - ❌ No camera found!
2025-11-24 18:20:08,968 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:08,991 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:09,017 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:09,109 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:09,111 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:09,114 - INFO - Video thread started with source: Camera
2025-11-24 18:20:09,115 - ERROR - ❌ No camera found!
2025-11-24 18:20:09,163 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:09,190 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:09,209 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:09,315 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:09,320 - INFO - Video thread started with source: Camera
2025-11-24 18:20:09,322 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:09,322 - ERROR - ❌ No camera found!
2025-11-24 18:20:09,377 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:09,399 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:09,424 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:09,471 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:09,524 - INFO - Video thread started with source: Camera
2025-11-24 18:20:09,525 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:09,526 - ERROR - ❌ No camera found!
2025-11-24 18:20:09,583 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:09,600 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:09,635 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:09,663 - INFO - End of video file reached
2025-11-24 18:20:09,664 - INFO - Video capture loop ended
2025-11-24 18:20:09,723 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:09,723 - INFO - Video thread started with source: Camera
2025-11-24 18:20:09,724 - ERROR - ❌ No camera found!
2025-11-24 18:20:09,798 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:09,900 - INFO - Video thread started with source: Camera
2025-11-24 18:20:09,900 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:09,901 - ERROR - ❌ No camera found!
2025-11-24 18:20:09,974 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:10,081 - INFO - Video thread started with source: Camera
2025-11-24 18:20:10,082 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:10,082 - ERROR - ❌ No camera found!
2025-11-24 18:20:10,173 - INFO - Video thread started with source: Camera
2025-11-24 18:20:10,174 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:10,175 - ERROR - ❌ No camera found!
2025-11-24 18:20:10,265 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:10,266 - INFO - Video thread started with source: Camera
2025-11-24 18:20:10,267 - ERROR - ❌ No camera found!
2025-11-24 18:20:10,357 - INFO - Video thread started with source: Camera
2025-11-24 18:20:10,365 - ERROR - ❌ No camera found!
2025-11-24 18:20:10,365 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:10,459 - INFO - Video thread started with source: Camera
2025-11-24 18:20:10,460 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:10,461 - ERROR - ❌ No camera found!
2025-11-24 18:20:10,553 - INFO - Video thread started with source: Camera
2025-11-24 18:20:10,555 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:10,555 - ERROR - ❌ No camera found!
2025-11-24 18:20:10,647 - INFO - Video thread started with source: Camera
2025-11-24 18:20:10,647 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:10,649 - ERROR - ❌ No camera found!
2025-11-24 18:20:10,743 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:10,743 - INFO - Video thread started with source: Camera
2025-11-24 18:20:10,744 - ERROR - ❌ No camera found!
2025-11-24 18:20:10,836 - INFO - Video thread started with source: Camera
2025-11-24 18:20:10,838 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:10,838 - ERROR - ❌ No camera found!
2025-11-24 18:20:10,932 - INFO - Video thread started with source: Camera
2025-11-24 18:20:10,933 - ERROR - ❌ No camera found!
2025-11-24 18:20:10,965 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:11,024 - INFO - Video thread started with source: Camera
2025-11-24 18:20:11,025 - ERROR - ❌ No camera found!
2025-11-24 18:20:11,059 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:11,114 - INFO - Video thread started with source: Camera
2025-11-24 18:20:11,115 - ERROR - ❌ No camera found!
2025-11-24 18:20:11,149 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:11,204 - INFO - Video thread started with source: Camera
2025-11-24 18:20:11,205 - ERROR - ❌ No camera found!
2025-11-24 18:20:11,289 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:11,292 - INFO - Video thread started with source: Camera
2025-11-24 18:20:11,294 - ERROR - ❌ No camera found!
2025-11-24 18:20:11,386 - INFO - Video thread started with source: Camera
2025-11-24 18:20:11,387 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:11,387 - ERROR - ❌ No camera found!
2025-11-24 18:20:11,479 - INFO - Video thread started with source: Camera
2025-11-24 18:20:11,480 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:11,480 - ERROR - ❌ No camera found!
2025-11-24 18:20:11,573 - INFO - Video thread started with source: Camera
2025-11-24 18:20:11,574 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:11,574 - ERROR - ❌ No camera found!
2025-11-24 18:20:11,660 - INFO - Video thread started with source: Camera
2025-11-24 18:20:11,661 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:11,663 - ERROR - ❌ No camera found!
2025-11-24 18:20:11,752 - INFO - Video thread started with source: Camera
2025-11-24 18:20:11,753 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:11,753 - ERROR - ❌ No camera found!
2025-11-24 18:20:11,841 - INFO - Video thread started with source: Camera
2025-11-24 18:20:11,842 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:11,843 - ERROR - ❌ No camera found!
2025-11-24 18:20:11,929 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:11,929 - INFO - Video thread started with source: Camera
2025-11-24 18:20:11,931 - ERROR - ❌ No camera found!
2025-11-24 18:20:12,022 - INFO - Video thread started with source: Camera
2025-11-24 18:20:12,023 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:12,024 - ERROR - ❌ No camera found!
2025-11-24 18:20:12,110 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:12,111 - INFO - Video thread started with source: Camera
2025-11-24 18:20:12,112 - ERROR - ❌ No camera found!
2025-11-24 18:20:12,202 - INFO - Video thread started with source: Camera
2025-11-24 18:20:12,202 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:12,203 - ERROR - ❌ No camera found!
2025-11-24 18:20:12,296 - INFO - Video thread started with source: Camera
2025-11-24 18:20:12,296 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:12,299 - ERROR - ❌ No camera found!
2025-11-24 18:20:12,389 - INFO - Video thread started with source: Camera
2025-11-24 18:20:12,390 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:12,390 - ERROR - ❌ No camera found!
2025-11-24 18:20:12,484 - INFO - Video thread started with source: Camera
2025-11-24 18:20:12,485 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:12,486 - ERROR - ❌ No camera found!
2025-11-24 18:20:12,579 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:12,580 - INFO - Video thread started with source: Camera
2025-11-24 18:20:12,581 - ERROR - ❌ No camera found!
2025-11-24 18:20:12,673 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:12,673 - INFO - Video thread started with source: Camera
2025-11-24 18:20:12,675 - ERROR - ❌ No camera found!
2025-11-24 18:20:12,766 - INFO - Video thread started with source: Camera
2025-11-24 18:20:12,766 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:12,767 - ERROR - ❌ No camera found!
2025-11-24 18:20:12,854 - INFO - Video thread started with source: Camera
2025-11-24 18:20:12,855 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:12,857 - ERROR - ❌ No camera found!
2025-11-24 18:20:12,942 - INFO - Video thread started with source: Camera
2025-11-24 18:20:12,943 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:12,943 - ERROR - ❌ No camera found!
2025-11-24 18:20:13,034 - INFO - Video thread started with source: Camera
2025-11-24 18:20:13,035 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:13,036 - ERROR - ❌ No camera found!
2025-11-24 18:20:13,123 - INFO - Video thread started with source: Camera
2025-11-24 18:20:13,124 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:13,126 - ERROR - ❌ No camera found!
2025-11-24 18:20:13,209 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:13,210 - INFO - Video thread started with source: Camera
2025-11-24 18:20:13,211 - ERROR - ❌ No camera found!
2025-11-24 18:20:13,299 - INFO - Video thread started with source: Camera
2025-11-24 18:20:13,300 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:13,301 - ERROR - ❌ No camera found!
2025-11-24 18:20:13,387 - INFO - Video thread started with source: Camera
2025-11-24 18:20:13,387 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:13,389 - ERROR - ❌ No camera found!
2025-11-24 18:20:13,474 - INFO - Video thread started with source: Camera
2025-11-24 18:20:13,474 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:13,475 - ERROR - ❌ No camera found!
2025-11-24 18:20:13,565 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:13,566 - INFO - Video thread started with source: Camera
2025-11-24 18:20:13,566 - ERROR - ❌ No camera found!
2025-11-24 18:20:13,653 - INFO - Video thread started with source: Camera
2025-11-24 18:20:13,653 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:13,653 - ERROR - ❌ No camera found!
2025-11-24 18:20:13,740 - INFO - Video thread started with source: Camera
2025-11-24 18:20:13,740 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:13,741 - ERROR - ❌ No camera found!
2025-11-24 18:20:13,829 - INFO - Video thread started with source: Camera
2025-11-24 18:20:13,830 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:13,830 - ERROR - ❌ No camera found!
2025-11-24 18:20:13,919 - INFO - Video thread started with source: Camera
2025-11-24 18:20:13,920 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:13,921 - ERROR - ❌ No camera found!
2025-11-24 18:20:14,006 - INFO - Video thread started with source: Camera
2025-11-24 18:20:14,006 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:14,008 - ERROR - ❌ No camera found!
2025-11-24 18:20:14,098 - INFO - Video thread started with source: Camera
2025-11-24 18:20:14,098 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:14,099 - ERROR - ❌ No camera found!
2025-11-24 18:20:14,185 - INFO - Video thread started with source: Camera
2025-11-24 18:20:14,185 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:14,186 - ERROR - ❌ No camera found!
2025-11-24 18:20:14,272 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:14,272 - INFO - Video thread started with source: Camera
2025-11-24 18:20:14,273 - ERROR - ❌ No camera found!
2025-11-24 18:20:14,362 - INFO - Video thread started with source: Camera
2025-11-24 18:20:14,363 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:14,363 - ERROR - ❌ No camera found!
2025-11-24 18:20:14,449 - INFO - Video thread started with source: Camera
2025-11-24 18:20:14,450 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:14,450 - ERROR - ❌ No camera found!
2025-11-24 18:20:14,539 - INFO - Video thread started with source: Camera
2025-11-24 18:20:14,539 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:14,540 - ERROR - ❌ No camera found!
2025-11-24 18:20:14,630 - INFO - Video thread started with source: Camera
2025-11-24 18:20:14,631 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:14,631 - ERROR - ❌ No camera found!
2025-11-24 18:20:14,718 - INFO - Video thread started with source: Camera
2025-11-24 18:20:14,718 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:14,719 - ERROR - ❌ No camera found!
2025-11-24 18:20:14,804 - INFO - Video thread started with source: Camera
2025-11-24 18:20:14,805 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:14,805 - ERROR - ❌ No camera found!
2025-11-24 18:20:14,893 - INFO - Video thread started with source: Camera
2025-11-24 18:20:14,894 - ERROR - ❌ No camera found!
2025-11-24 18:20:14,925 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:14,982 - INFO - Video thread started with source: Camera
2025-11-24 18:20:14,983 - ERROR - ❌ No camera found!
2025-11-24 18:20:15,017 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:15,072 - INFO - Video thread started with source: Camera
2025-11-24 18:20:15,073 - ERROR - ❌ No camera found!
2025-11-24 18:20:15,107 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:15,165 - INFO - Video thread started with source: Camera
2025-11-24 18:20:15,166 - ERROR - ❌ No camera found!
2025-11-24 18:20:15,200 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:15,257 - INFO - Video thread started with source: Camera
2025-11-24 18:20:15,258 - ERROR - ❌ No camera found!
2025-11-24 18:20:15,293 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:15,347 - INFO - Video thread started with source: Camera
2025-11-24 18:20:15,349 - ERROR - ❌ No camera found!
2025-11-24 18:20:15,436 - INFO - Video thread started with source: Camera
2025-11-24 18:20:15,437 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:15,437 - ERROR - ❌ No camera found!
2025-11-24 18:20:15,522 - INFO - Video thread started with source: Camera
2025-11-24 18:20:15,523 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:15,524 - ERROR - ❌ No camera found!
2025-11-24 18:20:15,614 - INFO - Video thread started with source: Camera
2025-11-24 18:20:15,615 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:15,615 - ERROR - ❌ No camera found!
2025-11-24 18:20:15,704 - INFO - Video thread started with source: Camera
2025-11-24 18:20:15,704 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:15,705 - ERROR - ❌ No camera found!
2025-11-24 18:20:15,800 - INFO - Video thread started with source: Camera
2025-11-24 18:20:15,801 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:15,801 - ERROR - ❌ No camera found!
2025-11-24 18:20:15,895 - INFO - Video thread started with source: Camera
2025-11-24 18:20:15,897 - ERROR - ❌ No camera found!
2025-11-24 18:20:15,930 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:15,991 - INFO - Video thread started with source: Camera
2025-11-24 18:20:15,992 - ERROR - ❌ No camera found!
2025-11-24 18:20:16,025 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:16,083 - INFO - Video thread started with source: Camera
2025-11-24 18:20:16,084 - ERROR - ❌ No camera found!
2025-11-24 18:20:16,118 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:16,175 - INFO - Video thread started with source: Camera
2025-11-24 18:20:16,176 - ERROR - ❌ No camera found!
2025-11-24 18:20:16,211 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:16,270 - INFO - Video thread started with source: Camera
2025-11-24 18:20:16,271 - ERROR - ❌ No camera found!
2025-11-24 18:20:16,305 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:16,363 - INFO - Video thread started with source: Camera
2025-11-24 18:20:16,365 - ERROR - ❌ No camera found!
2025-11-24 18:20:16,453 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:16,457 - INFO - Video thread started with source: Camera
2025-11-24 18:20:16,458 - ERROR - ❌ No camera found!
2025-11-24 18:20:16,546 - INFO - Video thread started with source: Camera
2025-11-24 18:20:16,547 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:16,547 - ERROR - ❌ No camera found!
2025-11-24 18:20:16,634 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:16,637 - INFO - Video thread started with source: Camera
2025-11-24 18:20:16,638 - ERROR - ❌ No camera found!
2025-11-24 18:20:16,723 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:16,723 - INFO - Video thread started with source: Camera
2025-11-24 18:20:16,724 - ERROR - ❌ No camera found!
2025-11-24 18:20:16,811 - INFO - Video thread started with source: Camera
2025-11-24 18:20:16,811 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:16,812 - ERROR - ❌ No camera found!
2025-11-24 18:20:16,898 - INFO - Video thread started with source: Camera
2025-11-24 18:20:16,899 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:16,900 - ERROR - ❌ No camera found!
2025-11-24 18:20:16,996 - INFO - Video thread started with source: Camera
2025-11-24 18:20:16,996 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:16,997 - ERROR - ❌ No camera found!
2025-11-24 18:20:17,085 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:17,085 - INFO - Video thread started with source: Camera
2025-11-24 18:20:17,086 - ERROR - ❌ No camera found!
2025-11-24 18:20:17,179 - INFO - Video thread started with source: Camera
2025-11-24 18:20:17,179 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:17,180 - ERROR - ❌ No camera found!
2025-11-24 18:20:17,409 - INFO - Video thread started with source: Camera
2025-11-24 18:20:17,465 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:17,466 - ERROR - ❌ No camera found!
2025-11-24 18:20:17,524 - INFO - Video file uploaded: assets/temp_videos/Screen Recording 2025-11-24 at 6.00.09 PM.mov
2025-11-24 18:20:17,525 - INFO - Video thread started with source: assets/temp_videos/Screen Recording 2025-11-24 at 6.00.09 PM.mov
2025-11-24 18:20:17,537 - INFO - ✓ Video file opened: assets/temp_videos/Screen Recording 2025-11-24 at 6.00.09 PM.mov
2025-11-24 18:20:17,542 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:17,714 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:17,743 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:17,744 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:17,907 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:17,912 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:17,942 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:18,020 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:18,046 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:18,071 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:18,100 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:18,115 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:18,182 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:18,233 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:18,241 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:18,264 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:18,361 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:18,391 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:18,393 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:18,419 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:18,493 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:18,521 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:18,551 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:18,581 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:18,586 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:18,675 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:18,703 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:18,706 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:18,733 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:18,821 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:18,828 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:18,860 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:18,888 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:18,896 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:18,988 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:19,018 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:19,020 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:19,048 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:19,134 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:19,142 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:19,171 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:19,199 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:19,207 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:19,297 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:19,328 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:19,329 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:19,356 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:19,430 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:19,466 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:19,498 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:19,527 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:19,529 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:19,625 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:19,654 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:19,656 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:19,683 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:19,760 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:19,788 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:19,817 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:19,848 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:19,853 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:19,944 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:19,975 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:19,976 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:20,002 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:20,100 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:20,108 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:20,140 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:20,169 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:20,175 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:20,280 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:20,312 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:20,312 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:20,342 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:20,435 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:20,441 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:20,471 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:20,501 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:20,508 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:20,605 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:20,631 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:20,635 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:20,666 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:20,752 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:20,758 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:20,786 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:20,816 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:20,824 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:20,911 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:20,942 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:20,944 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:20,971 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:21,071 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:21,075 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:21,106 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:21,134 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:21,145 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:21,232 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:21,248 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:21,265 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:21,301 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:21,406 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:21,413 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:21,443 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:21,473 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:21,480 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:21,574 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:21,604 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:21,607 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:21,634 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:21,726 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:21,733 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:21,765 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:21,794 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:21,800 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:21,895 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:21,926 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:21,927 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:21,954 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:22,046 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:22,053 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:22,084 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:22,115 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:22,120 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:22,214 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:22,231 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:22,247 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:22,277 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:22,370 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:22,377 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:22,407 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:22,435 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:22,444 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:22,530 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:22,562 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:22,563 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:22,593 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:22,688 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:22,695 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:22,724 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:22,751 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:22,760 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:22,844 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:22,875 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:22,877 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:22,903 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:22,994 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,001 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,035 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,065 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,066 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,157 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,187 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,189 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,217 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,283 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,309 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,341 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,360 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,369 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,464 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,495 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,496 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,525 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,590 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,619 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,648 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,678 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,684 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,776 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,805 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,806 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,834 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,922 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,930 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,961 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,989 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:23,997 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:24,093 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:24,122 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:24,123 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:24,149 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:24,238 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:24,245 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:24,275 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:24,303 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:24,312 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:24,396 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:24,427 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:24,429 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:24,457 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:24,521 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:24,550 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:24,581 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:24,610 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:24,616 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:24,705 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:24,736 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:24,737 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:24,767 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:24,833 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:24,862 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:24,893 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:24,920 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:24,923 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:25,020 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:25,050 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:25,052 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:25,082 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:25,172 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:25,180 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:25,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:25,242 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:25,248 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:25,346 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:25,377 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:25,378 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:25,406 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:25,501 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:25,512 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:25,543 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:25,571 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:25,572 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:25,674 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:25,703 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:25,705 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:25,733 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:25,826 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:25,833 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:25,865 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:25,895 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:25,899 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:25,988 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:26,000 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:26,016 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:26,045 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:26,129 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:26,139 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:26,169 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:26,200 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:26,205 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:26,298 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:26,313 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:26,329 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:26,358 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:26,452 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:26,460 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:26,491 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:26,519 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:26,526 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:26,616 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:26,629 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:26,647 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:26,677 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:26,766 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:26,767 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:26,798 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:26,829 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:26,837 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:26,922 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:26,952 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:26,954 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:26,982 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:27,068 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:27,075 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:27,103 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:27,133 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:27,139 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:27,228 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:27,258 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:27,259 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:27,285 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:27,386 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:27,393 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:27,423 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:27,450 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:27,460 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:27,553 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:27,584 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:27,585 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:27,616 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:27,687 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:27,717 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:27,748 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:27,779 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:27,781 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:27,875 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:27,905 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:27,907 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:27,935 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:28,028 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:28,037 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:28,066 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:28,097 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:28,103 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:28,195 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:28,224 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:28,226 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:28,253 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:28,351 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:28,360 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:28,389 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:28,417 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:28,426 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:28,514 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:28,546 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:28,548 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:28,578 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:28,662 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:28,669 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:28,699 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:28,730 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:28,736 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:28,829 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:28,856 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:28,860 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:28,889 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:28,954 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:28,981 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:29,011 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:29,039 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:29,047 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:29,139 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:29,169 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:29,171 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:29,200 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:29,291 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:29,296 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:29,328 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:29,357 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:29,364 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:29,463 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:29,495 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:29,496 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:29,524 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:29,616 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:29,625 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:29,653 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:29,682 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:29,690 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:29,777 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:29,808 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:29,809 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:29,835 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:29,904 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:29,932 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:29,963 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:29,992 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:29,999 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:30,087 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:30,118 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:30,120 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:30,150 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:30,238 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:30,246 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:30,275 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:30,302 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:30,312 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:30,403 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:30,432 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:30,433 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:30,463 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:30,530 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:30,563 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:30,595 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:30,603 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:30,623 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:30,720 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:30,750 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:30,752 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:30,782 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:30,876 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:30,881 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:30,913 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:30,943 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:30,950 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:31,041 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:31,069 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:31,070 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:31,099 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:31,184 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:31,189 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:31,220 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:31,250 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:31,257 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:31,344 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:31,374 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:31,375 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:31,401 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:31,491 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:31,496 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:31,526 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:31,554 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:31,640 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:31,648 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:31,680 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:31,709 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:31,715 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:31,811 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:31,842 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:31,844 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:31,869 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:31,947 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:31,973 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:32,003 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:32,033 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:32,044 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:32,136 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:32,166 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:32,168 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:32,197 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:32,281 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:32,319 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:32,351 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:32,357 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:32,385 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:32,485 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:32,496 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:32,527 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:32,555 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:32,557 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:32,656 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:32,685 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:32,687 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:32,716 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:32,806 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:32,812 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:32,843 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:32,873 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:32,879 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:32,976 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:33,006 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:33,008 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:33,034 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:33,126 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:33,131 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:33,162 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:33,190 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:33,200 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:33,295 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:33,326 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:33,328 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:33,353 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:33,447 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:33,453 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:33,484 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:33,515 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:33,521 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:33,608 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:33,636 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:33,638 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:33,665 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:33,733 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:33,762 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:33,791 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:33,813 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:33,820 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:33,922 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:33,951 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:33,952 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:33,981 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:34,066 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:34,075 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:34,104 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:34,133 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:34,140 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:34,229 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:34,261 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:34,263 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:34,290 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:34,356 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:34,384 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:34,415 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:34,426 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:34,446 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:34,542 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:34,570 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:34,571 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:34,598 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:34,690 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:34,696 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:34,726 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:34,754 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:34,762 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:34,849 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:34,877 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:34,881 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:34,909 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:34,998 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:35,007 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:35,034 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:35,064 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:35,070 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:35,156 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:35,184 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:35,187 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:35,216 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:35,311 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:35,317 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:35,350 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:35,381 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:35,383 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:35,474 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:35,506 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:35,507 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:35,534 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:35,626 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:35,633 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:35,665 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:35,695 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:35,700 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:35,790 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:35,819 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:35,821 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:35,850 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:35,944 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:35,950 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:35,982 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:36,013 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:36,018 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:36,116 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:36,130 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:36,148 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:36,178 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:36,272 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:36,280 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:36,310 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:36,341 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:36,346 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:36,444 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:36,474 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:36,476 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:36,503 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:36,604 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:36,611 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:36,641 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:36,669 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:36,677 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:36,767 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:36,798 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:36,799 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:36,826 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:36,913 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:36,921 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:36,950 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:36,981 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:36,987 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:37,077 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:37,107 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:37,108 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:37,135 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:37,222 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:37,230 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:37,262 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:37,290 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:37,292 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:37,384 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:37,412 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:37,416 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:37,446 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:37,531 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:37,539 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:37,567 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:37,597 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:37,603 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:37,696 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:37,728 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:37,729 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:37,756 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:37,825 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:37,855 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:37,886 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:37,916 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:37,921 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:38,006 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:38,035 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:38,038 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:38,066 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:38,156 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:38,163 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:38,193 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:38,221 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:38,229 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:38,322 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:38,353 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:38,354 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:38,383 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:38,470 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:38,477 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:38,506 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:38,534 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:38,542 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:38,628 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:38,658 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:38,661 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:38,686 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:38,779 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:38,785 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:38,817 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:38,848 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:38,853 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:38,944 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:38,973 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:38,975 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:39,000 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:39,092 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:39,098 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:39,128 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:39,157 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:39,165 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:39,261 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:39,293 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:39,294 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:39,320 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:39,411 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:39,417 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:39,448 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:39,478 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:39,484 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:39,570 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:39,600 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:39,602 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:39,630 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:39,721 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:39,727 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:39,758 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:39,788 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:39,794 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:39,881 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:39,911 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:39,916 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:39,939 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:40,033 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:40,039 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:40,069 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:40,099 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:40,106 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:40,194 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:40,223 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:40,225 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:40,251 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:40,343 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:40,347 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:40,377 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:40,407 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:40,416 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:40,509 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:40,533 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:40,550 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:40,581 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:40,637 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:40,671 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:40,699 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:40,710 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:40,729 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:40,821 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:40,852 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:40,854 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:40,883 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:40,967 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:40,974 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:41,005 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:41,033 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:41,041 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:41,127 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:41,157 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:41,159 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:41,184 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:41,254 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:41,282 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:41,313 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:41,343 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:41,350 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:41,441 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:41,469 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:41,471 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:41,499 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:41,593 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:41,599 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:41,630 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:41,660 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:41,666 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:41,761 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:41,778 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:41,791 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:41,820 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:41,920 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:41,927 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:41,957 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:41,985 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:41,994 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:42,092 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:42,117 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:42,132 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:42,163 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:42,244 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:42,272 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:42,300 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:42,315 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:42,390 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:42,430 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:42,440 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:42,468 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:42,553 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:42,553 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:42,588 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:42,616 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:42,628 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:42,647 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:42,745 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:42,775 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:42,777 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:42,803 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:42,897 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:42,902 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:42,933 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:42,963 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:42,973 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:43,060 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:43,090 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:43,091 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:43,117 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:43,205 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:43,213 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:43,244 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:43,271 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:43,279 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:43,413 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:43,417 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:43,444 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:43,472 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:43,563 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:43,570 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:43,600 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:43,631 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:43,636 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:43,724 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:43,753 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:43,754 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:43,783 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:43,875 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:43,881 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:43,912 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:43,941 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:43,948 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:44,039 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:44,056 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:44,070 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:44,100 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:44,199 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:44,200 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:44,232 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:44,263 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:44,269 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:44,359 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:44,390 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:44,391 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:44,417 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:44,504 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:44,513 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:44,547 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:44,578 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:44,580 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:44,668 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:44,700 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:44,700 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:44,731 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:44,820 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:44,825 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:44,854 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:44,883 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:44,890 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:44,980 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:45,012 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:45,013 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:45,039 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:45,126 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:45,130 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:45,160 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:45,189 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:45,200 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:45,291 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:45,322 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:45,327 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:45,352 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:45,450 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:45,457 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:45,487 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:45,516 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:45,523 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:45,603 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:45,656 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:45,661 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:45,684 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:45,789 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:45,793 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:45,824 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:45,852 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:45,864 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:45,932 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:45,982 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:45,991 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:46,012 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:46,091 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:46,114 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:46,141 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:46,169 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:46,184 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:46,254 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:46,298 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:46,303 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:46,332 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:46,362 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:46,436 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:46,464 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:46,495 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:46,506 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:46,599 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:46,629 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:46,630 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:46,657 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:46,746 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:46,753 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:46,784 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:46,815 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:46,820 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:46,911 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:46,943 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:46,943 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:46,970 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:47,063 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:47,069 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:47,100 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:47,130 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:47,137 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:47,234 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:47,265 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:47,267 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:47,296 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:47,364 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:47,396 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:47,427 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:47,457 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:47,459 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:47,556 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:47,584 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:47,586 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:47,614 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:47,705 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:47,713 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:47,743 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:47,770 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:47,779 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:47,869 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:47,898 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:47,900 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:47,928 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:48,015 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:48,023 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:48,052 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:48,083 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:48,089 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:48,192 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:48,222 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:48,223 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:48,250 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:48,346 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:48,353 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:48,384 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:48,414 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:48,420 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:48,517 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:48,545 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:48,550 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:48,579 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:48,665 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:48,673 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:48,701 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:48,731 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:48,737 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:48,828 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:48,859 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:48,860 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:48,888 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:48,982 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:48,987 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:49,019 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:49,049 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:49,055 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:49,159 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:49,189 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:49,190 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:49,218 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:49,316 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:49,321 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:49,353 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:49,383 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:49,391 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:49,479 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:49,510 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:49,512 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:49,538 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:49,629 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:49,635 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:49,667 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:49,697 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:49,703 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:49,791 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:49,819 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:49,821 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:49,850 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:49,941 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:49,949 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:49,980 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:50,009 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:50,017 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:50,103 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:50,133 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:50,135 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:50,164 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:50,234 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:50,261 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:50,291 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:50,319 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:50,327 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:50,397 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:50,446 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:50,454 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:50,477 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:50,551 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:50,575 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:50,607 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:50,635 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:50,644 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:50,716 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:50,764 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:50,772 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:50,794 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:50,822 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:50,896 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:50,922 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:50,950 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:50,966 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:50,978 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:51,065 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:51,090 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:51,099 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:51,130 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:51,215 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:51,221 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:51,250 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:51,282 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:51,290 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:51,379 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:51,409 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:51,410 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:51,437 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:51,537 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:51,538 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:51,569 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:51,598 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:51,608 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:51,698 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:51,729 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:51,734 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:51,757 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:51,838 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:51,843 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:51,896 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:51,927 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:51,933 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:52,034 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:52,066 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:52,070 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:52,098 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:52,197 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:52,205 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:52,235 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:52,266 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:52,272 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:52,367 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:52,382 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:52,398 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:52,428 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:52,512 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:52,523 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:52,551 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:52,581 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:52,587 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:52,681 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:52,712 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:52,713 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:52,740 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:52,807 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:52,838 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:52,867 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:52,898 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:52,903 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:53,008 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:53,033 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:53,039 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:53,067 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:53,164 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:53,171 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:53,200 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:53,231 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:53,237 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:53,335 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:53,360 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:53,376 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:53,409 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:53,490 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:53,501 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:53,541 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:53,560 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:53,569 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:53,664 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:53,695 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:53,698 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:53,725 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:53,822 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:53,829 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:53,862 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:53,893 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:53,896 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:53,987 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:54,013 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:54,018 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:54,048 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:54,132 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:54,139 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:54,167 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:54,199 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:54,208 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:54,302 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:54,332 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:54,334 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:54,367 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:54,490 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:54,497 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:54,526 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:54,555 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:54,566 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:54,641 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:54,691 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:54,698 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:54,719 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:54,820 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:54,820 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:54,851 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:54,881 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:54,890 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:54,980 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:55,012 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:55,016 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:55,042 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:55,140 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:55,141 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:55,173 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:55,201 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:55,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:55,280 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:55,331 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:55,334 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:55,363 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:55,459 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:55,463 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:55,494 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:55,523 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:55,533 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:55,622 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:55,638 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:55,653 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:55,683 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:55,759 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:55,765 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:55,814 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:55,840 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:55,846 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:55,875 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:55,961 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:55,975 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:55,999 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:56,030 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:56,112 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:56,119 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:56,148 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:56,178 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:56,185 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:56,279 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:56,308 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:56,315 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:56,337 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:56,417 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:56,437 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:56,467 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:56,497 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:56,507 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:56,577 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:56,625 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:56,634 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:56,652 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:56,682 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:56,736 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:56,767 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:56,802 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:56,828 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:56,833 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:56,926 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:56,958 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:56,959 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:56,985 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:57,078 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:57,085 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:57,115 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:57,145 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:57,151 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:57,245 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:57,275 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:57,276 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:57,303 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:57,376 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:57,402 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:57,435 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:57,464 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:57,469 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:57,570 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:57,599 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:57,601 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:57,629 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:57,715 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:57,720 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:57,750 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:57,782 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:57,786 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:57,880 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:57,910 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:57,910 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:57,939 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:58,029 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:58,036 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:58,067 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:58,097 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:58,103 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:58,190 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:58,205 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:58,219 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:58,249 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:58,324 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:58,351 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:58,383 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:58,412 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:58,420 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:58,507 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:58,537 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:58,539 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:58,566 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:58,637 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:58,666 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:58,698 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:58,728 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:58,734 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:58,823 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:58,851 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:58,853 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:58,881 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:58,952 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:58,980 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:59,011 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:59,039 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:59,047 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:59,141 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:59,172 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:59,176 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:59,201 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:59,293 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:59,297 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:59,330 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:59,360 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:59,367 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:59,456 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:59,473 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:59,486 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:59,516 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:59,609 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:59,616 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:59,647 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:59,677 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:59,683 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:59,770 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:59,798 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:59,800 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:59,829 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:59,931 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:59,937 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:20:59,969 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:00,000 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:00,006 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:00,103 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:00,118 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:00,133 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:00,165 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:00,262 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:00,269 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:00,300 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:00,330 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:00,335 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:00,434 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:00,465 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:00,466 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:00,496 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:00,592 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:00,600 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:00,632 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:00,663 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:00,665 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:00,764 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:00,790 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:00,796 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:00,824 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:00,909 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:00,918 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:00,949 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:00,980 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:00,981 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:01,073 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:01,104 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:01,105 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:01,132 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:01,224 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:01,230 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:01,264 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:01,295 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:01,296 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:01,387 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:01,417 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:01,419 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:01,448 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:01,548 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:01,548 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:01,579 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:01,607 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:01,617 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:01,685 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:01,735 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:01,743 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:01,764 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:01,844 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:01,867 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:01,900 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:01,931 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:01,937 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:02,033 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:02,050 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:02,065 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:02,095 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:02,161 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:02,190 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:02,218 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:02,249 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:02,254 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:02,349 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:02,379 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:02,383 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:02,413 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:02,504 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:02,511 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:02,542 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:02,572 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:02,578 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:02,677 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:02,707 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:02,713 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:02,736 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:02,828 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:02,834 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:02,864 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:02,895 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:02,900 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:02,989 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:03,020 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:03,025 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:03,049 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:03,140 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:03,148 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:03,179 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:03,210 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:03,215 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:03,290 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:03,330 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:03,343 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:03,373 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:03,469 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:03,475 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:03,505 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:03,533 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:03,544 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:03,632 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:03,664 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:03,668 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:03,695 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:03,793 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:03,800 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:03,832 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:03,862 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:03,868 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:03,956 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:03,984 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:03,986 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:04,015 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:04,110 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:04,118 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:04,150 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:04,180 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:04,182 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:04,278 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:04,308 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:04,310 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:04,336 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:04,414 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:04,442 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:04,474 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:04,495 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:04,502 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:04,610 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:04,639 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:04,646 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:04,668 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:04,756 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:04,756 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:04,807 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:04,836 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:04,846 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:04,945 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:04,975 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:04,976 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:05,003 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:05,100 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:05,105 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:05,134 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:05,166 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:05,175 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:05,272 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:05,301 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:05,307 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:05,332 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:05,426 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:05,433 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:05,467 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:05,501 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:05,502 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:05,621 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:05,650 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:05,652 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:05,682 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:05,778 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:05,786 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:05,826 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:05,848 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:05,856 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:05,943 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:05,972 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:05,974 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:06,002 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:06,072 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:06,105 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:06,135 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:06,165 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:06,171 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:06,266 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:06,298 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:06,301 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:06,328 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:06,410 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:06,417 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:06,449 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:06,482 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:06,485 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:06,576 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:06,605 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:06,607 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:06,633 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:06,711 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:06,736 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:06,766 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:06,796 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:06,804 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:06,895 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:06,928 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:06,931 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:06,957 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:07,056 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:07,057 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:07,084 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:07,115 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:07,126 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:07,222 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:07,253 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:07,259 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:07,283 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:07,372 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:07,381 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:07,419 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:07,444 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:07,449 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:07,532 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:07,564 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:07,564 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:07,594 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:07,659 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:07,690 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:07,718 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:07,748 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:07,754 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:07,841 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:07,871 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:07,873 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:07,899 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:07,968 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:07,996 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:08,027 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:08,056 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:08,063 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:08,154 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:08,184 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:08,185 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:08,215 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:08,281 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:08,311 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:08,341 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:08,353 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:08,369 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:08,466 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:08,499 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:08,500 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:08,529 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:08,615 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:08,636 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:08,666 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:08,685 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:08,696 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:08,799 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:08,807 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:08,831 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:08,916 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:08,942 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:08,970 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:08,999 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:09,011 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:09,080 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:09,121 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:09,131 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:09,163 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:09,241 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:09,270 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:09,301 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:09,331 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:09,337 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:09,431 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:09,463 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:09,464 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:09,492 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:09,561 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:09,591 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:09,621 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:09,649 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:09,657 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:09,749 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:09,779 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:09,785 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:09,811 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:09,904 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:09,912 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:09,942 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:09,970 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:09,979 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:10,067 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:10,099 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:10,102 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:10,129 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:10,217 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:10,225 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:10,256 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:10,285 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:10,292 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:10,380 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:10,412 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:10,412 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:10,440 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:10,528 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:10,536 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:10,571 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:10,599 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:10,601 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:10,693 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:10,725 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:10,726 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:10,753 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:10,848 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:10,856 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:10,885 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:10,915 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:10,922 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:11,013 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:11,045 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:11,046 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:11,074 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:11,164 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:11,170 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:11,201 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:11,232 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:11,237 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:11,332 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:11,364 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:11,366 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:11,396 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:11,463 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:11,490 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:11,519 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:11,543 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:11,549 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:11,630 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:11,683 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:11,687 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:11,716 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:11,811 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:11,819 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:11,849 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:11,880 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:11,885 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:11,981 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:12,013 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:12,014 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:12,044 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:12,142 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:12,149 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:12,181 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:12,211 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:12,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:12,302 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:12,333 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:12,337 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:12,364 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:12,467 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:12,468 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:12,498 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:12,529 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:12,538 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:12,629 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:12,660 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:12,661 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:12,688 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:12,776 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:12,782 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:12,814 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:12,845 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:12,850 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:12,936 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:12,967 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:12,968 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:12,997 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:13,085 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:13,090 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:13,120 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:13,150 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:13,161 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:13,248 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:13,274 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:13,278 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:13,306 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:13,395 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:13,400 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:13,432 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:13,463 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:13,468 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:13,560 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:13,590 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:13,592 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:13,618 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:13,719 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:13,728 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:13,758 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:13,785 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:13,794 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:13,888 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:13,916 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:13,918 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:13,947 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:14,040 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:14,047 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:14,080 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:14,109 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:14,111 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:14,208 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:14,238 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:14,240 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:14,269 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:14,349 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:14,380 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:14,411 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:14,420 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:14,440 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:14,537 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:14,567 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:14,567 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:14,598 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:14,694 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:14,704 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:14,735 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:14,765 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:14,767 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:14,865 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:14,896 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:14,898 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:14,928 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:15,020 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:15,027 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:15,058 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:15,087 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:15,094 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:15,182 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:15,213 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:15,215 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:15,243 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:15,342 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:15,344 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:15,372 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:15,400 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:15,413 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:15,482 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:15,524 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:15,533 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:15,564 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:15,668 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:15,668 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:15,700 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:15,731 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:15,738 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:15,830 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:15,862 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:15,863 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:15,891 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:15,985 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:15,996 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:16,026 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:16,054 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:16,056 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:16,156 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:16,187 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:16,189 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:16,216 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:16,297 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:16,299 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:16,346 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:16,377 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:16,388 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:16,462 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:16,499 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:16,500 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:16,525 - INFO - Video thread started with source: Camera
2025-11-24 18:21:16,526 - ERROR - ❌ No camera found!
2025-11-24 18:21:16,534 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:16,603 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:16,619 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:16,649 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:16,673 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:16,679 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:16,769 - INFO - Video thread started with source: Camera
2025-11-24 18:21:16,771 - ERROR - ❌ No camera found!
2025-11-24 18:21:16,801 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:16,806 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:16,834 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:16,914 - INFO - Video thread started with source: Camera
2025-11-24 18:21:16,916 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:16,916 - ERROR - ❌ No camera found!
2025-11-24 18:21:16,924 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:16,955 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:16,982 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:16,990 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:17,062 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:17,063 - INFO - Video thread started with source: Camera
2025-11-24 18:21:17,064 - ERROR - ❌ No camera found!
2025-11-24 18:21:17,093 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:17,097 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:17,121 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:17,191 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:17,191 - INFO - Video thread started with source: Camera
2025-11-24 18:21:17,193 - ERROR - ❌ No camera found!
2025-11-24 18:21:17,198 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:17,231 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:17,261 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:17,266 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:17,333 - INFO - Video thread started with source: Camera
2025-11-24 18:21:17,334 - ERROR - ❌ No camera found!
2025-11-24 18:21:17,342 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:17,370 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:17,371 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:17,399 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:17,471 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:17,472 - INFO - Video thread started with source: Camera
2025-11-24 18:21:17,472 - ERROR - ❌ No camera found!
2025-11-24 18:21:17,478 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:17,508 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:17,535 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:17,544 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:17,613 - INFO - Video thread started with source: Camera
2025-11-24 18:21:17,614 - ERROR - ❌ No camera found!
2025-11-24 18:21:17,636 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:17,648 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:17,666 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:17,696 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:17,754 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:17,755 - INFO - Video thread started with source: Camera
2025-11-24 18:21:17,756 - ERROR - ❌ No camera found!
2025-11-24 18:21:17,784 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:17,815 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:17,825 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:17,901 - INFO - Video thread started with source: Camera
2025-11-24 18:21:17,902 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:17,904 - ERROR - ❌ No camera found!
2025-11-24 18:21:17,935 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:17,939 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:17,965 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,032 - INFO - Video thread started with source: Camera
2025-11-24 18:21:18,033 - ERROR - ❌ No camera found!
2025-11-24 18:21:18,033 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,041 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,070 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,100 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,105 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,174 - INFO - Video thread started with source: Camera
2025-11-24 18:21:18,179 - ERROR - ❌ No camera found!
2025-11-24 18:21:18,180 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,210 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,238 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,316 - INFO - Video thread started with source: Camera
2025-11-24 18:21:18,316 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,318 - ERROR - ❌ No camera found!
2025-11-24 18:21:18,323 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,351 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,383 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,388 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,464 - INFO - Video thread started with source: Camera
2025-11-24 18:21:18,465 - ERROR - ❌ No camera found!
2025-11-24 18:21:18,474 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,504 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,505 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,532 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,604 - INFO - Video thread started with source: Camera
2025-11-24 18:21:18,606 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,606 - ERROR - ❌ No camera found!
2025-11-24 18:21:18,613 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,646 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,676 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,681 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,740 - INFO - Video thread started with source: Camera
2025-11-24 18:21:18,742 - ERROR - ❌ No camera found!
2025-11-24 18:21:18,749 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,780 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,781 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,808 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,879 - INFO - Video thread started with source: Camera
2025-11-24 18:21:18,879 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,880 - ERROR - ❌ No camera found!
2025-11-24 18:21:18,887 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,916 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,946 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:18,951 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,019 - INFO - Video thread started with source: Camera
2025-11-24 18:21:19,020 - ERROR - ❌ No camera found!
2025-11-24 18:21:19,026 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,054 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,056 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,082 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,161 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,163 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,163 - INFO - Video thread started with source: Camera
2025-11-24 18:21:19,165 - ERROR - ❌ No camera found!
2025-11-24 18:21:19,194 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,224 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,233 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,293 - INFO - Video thread started with source: Camera
2025-11-24 18:21:19,294 - ERROR - ❌ No camera found!
2025-11-24 18:21:19,300 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,332 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,333 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,363 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,427 - INFO - Video thread started with source: Camera
2025-11-24 18:21:19,429 - ERROR - ❌ No camera found!
2025-11-24 18:21:19,429 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,436 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,467 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,498 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,504 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,565 - INFO - Video thread started with source: Camera
2025-11-24 18:21:19,566 - ERROR - ❌ No camera found!
2025-11-24 18:21:19,573 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,603 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,604 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,632 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,703 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,705 - INFO - Video thread started with source: Camera
2025-11-24 18:21:19,706 - ERROR - ❌ No camera found!
2025-11-24 18:21:19,711 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,741 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,768 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,777 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,841 - INFO - Video thread started with source: Camera
2025-11-24 18:21:19,842 - ERROR - ❌ No camera found!
2025-11-24 18:21:19,849 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,880 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,882 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,911 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,978 - INFO - Video thread started with source: Camera
2025-11-24 18:21:19,978 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:19,979 - ERROR - ❌ No camera found!
2025-11-24 18:21:19,988 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,029 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,048 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,061 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,132 - INFO - Video thread started with source: Camera
2025-11-24 18:21:20,133 - ERROR - ❌ No camera found!
2025-11-24 18:21:20,143 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,173 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,174 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,202 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,318 - INFO - Video thread started with source: Camera
2025-11-24 18:21:20,320 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,320 - ERROR - ❌ No camera found!
2025-11-24 18:21:20,326 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,355 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,383 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,391 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,467 - INFO - Video thread started with source: Camera
2025-11-24 18:21:20,472 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,473 - ERROR - ❌ No camera found!
2025-11-24 18:21:20,502 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,507 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,532 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,612 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,613 - INFO - Video thread started with source: Camera
2025-11-24 18:21:20,614 - ERROR - ❌ No camera found!
2025-11-24 18:21:20,620 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,653 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,729 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,736 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,762 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,789 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,799 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,813 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,840 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,865 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,869 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,891 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,916 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,938 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,943 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,970 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:20,997 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:21,008 - INFO - Video thread started with source: Camera
2025-11-24 18:21:21,010 - ERROR - ❌ No camera found!
2025-11-24 18:21:21,010 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:21,026 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:21,109 - INFO - Video thread started with source: Camera
2025-11-24 18:21:21,110 - ERROR - ❌ No camera found!
2025-11-24 18:21:21,115 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:21,143 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:21,146 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:21,208 - INFO - Video thread started with source: Camera
2025-11-24 18:21:21,210 - ERROR - ❌ No camera found!
2025-11-24 18:21:21,214 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:21,239 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:21,306 - INFO - Video thread started with source: Camera
2025-11-24 18:21:21,307 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:21,308 - ERROR - ❌ No camera found!
2025-11-24 18:21:21,311 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:21,337 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:21,405 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:21,406 - INFO - Video thread started with source: Camera
2025-11-24 18:21:21,407 - ERROR - ❌ No camera found!
2025-11-24 18:21:21,409 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:21,435 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:21,513 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:21,513 - INFO - Video thread started with source: Camera
2025-11-24 18:21:21,516 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:21,516 - ERROR - ❌ No camera found!
2025-11-24 18:21:21,546 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:21,618 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:21,621 - INFO - Video thread started with source: Camera
2025-11-24 18:21:21,623 - ERROR - ❌ No camera found!
2025-11-24 18:21:21,626 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:21,653 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:21,722 - INFO - Video thread started with source: Camera
2025-11-24 18:21:21,723 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:21,723 - ERROR - ❌ No camera found!
2025-11-24 18:21:21,728 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:21,753 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:21,817 - INFO - Video thread started with source: Camera
2025-11-24 18:21:21,817 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:21,818 - ERROR - ❌ No camera found!
2025-11-24 18:21:21,822 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:21,849 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:21,913 - INFO - Video thread started with source: Camera
2025-11-24 18:21:21,914 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:21,916 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:21,916 - ERROR - ❌ No camera found!
2025-11-24 18:21:21,944 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,006 - INFO - Video thread started with source: Camera
2025-11-24 18:21:22,008 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,008 - ERROR - ❌ No camera found!
2025-11-24 18:21:22,011 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,041 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,101 - INFO - Video thread started with source: Camera
2025-11-24 18:21:22,102 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,102 - ERROR - ❌ No camera found!
2025-11-24 18:21:22,106 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,129 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,191 - INFO - Video thread started with source: Camera
2025-11-24 18:21:22,192 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,193 - ERROR - ❌ No camera found!
2025-11-24 18:21:22,197 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,225 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,292 - INFO - Video thread started with source: Camera
2025-11-24 18:21:22,294 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,294 - ERROR - ❌ No camera found!
2025-11-24 18:21:22,299 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,326 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,388 - INFO - Video thread started with source: Camera
2025-11-24 18:21:22,388 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,390 - ERROR - ❌ No camera found!
2025-11-24 18:21:22,392 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,416 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,481 - INFO - Video thread started with source: Camera
2025-11-24 18:21:22,482 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,483 - ERROR - ❌ No camera found!
2025-11-24 18:21:22,485 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,514 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,576 - INFO - Video thread started with source: Camera
2025-11-24 18:21:22,577 - ERROR - ❌ No camera found!
2025-11-24 18:21:22,577 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,580 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,608 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,672 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,672 - INFO - Video thread started with source: Camera
2025-11-24 18:21:22,674 - ERROR - ❌ No camera found!
2025-11-24 18:21:22,678 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,703 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,766 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,767 - INFO - Video thread started with source: Camera
2025-11-24 18:21:22,768 - ERROR - ❌ No camera found!
2025-11-24 18:21:22,772 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,797 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,858 - INFO - Video thread started with source: Camera
2025-11-24 18:21:22,858 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,859 - ERROR - ❌ No camera found!
2025-11-24 18:21:22,862 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,888 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,952 - INFO - Video thread started with source: Camera
2025-11-24 18:21:22,953 - ERROR - ❌ No camera found!
2025-11-24 18:21:22,956 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,980 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:22,984 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:23,041 - INFO - Video thread started with source: Camera
2025-11-24 18:21:23,042 - ERROR - ❌ No camera found!
2025-11-24 18:21:23,045 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:23,071 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:23,075 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:23,135 - INFO - Video thread started with source: Camera
2025-11-24 18:21:23,136 - ERROR - ❌ No camera found!
2025-11-24 18:21:23,140 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:23,163 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:23,170 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:23,227 - INFO - Video thread started with source: Camera
2025-11-24 18:21:23,229 - ERROR - ❌ No camera found!
2025-11-24 18:21:23,231 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:23,257 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:23,260 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:23,321 - INFO - Video thread started with source: Camera
2025-11-24 18:21:23,322 - ERROR - ❌ No camera found!
2025-11-24 18:21:23,326 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:23,349 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:23,357 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:23,415 - INFO - Video thread started with source: Camera
2025-11-24 18:21:23,416 - ERROR - ❌ No camera found!
2025-11-24 18:21:23,421 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:23,446 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:23,450 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:23,570 - INFO - Camera disabled
2025-11-24 18:21:23,574 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:23,597 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:23,605 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:23,673 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:23,696 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:23,763 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:23,769 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:23,796 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:23,871 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:23,875 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:23,899 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:23,966 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:23,993 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:23,998 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:24,059 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:24,083 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:24,144 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:24,150 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:24,177 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:24,242 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:24,265 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:24,271 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:24,332 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:24,359 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:24,419 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:24,423 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:24,447 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:24,515 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:24,519 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:24,545 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:24,608 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:24,631 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:24,694 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:24,699 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:24,724 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:24,790 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:24,814 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:24,819 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:24,884 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:24,912 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:24,971 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:24,974 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:24,998 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:25,064 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:25,090 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:25,153 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:25,155 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:25,180 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:25,246 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:25,272 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:25,328 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:25,336 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:25,361 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:25,425 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:25,448 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:25,453 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:25,515 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:25,542 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:25,604 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:25,607 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:25,631 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:25,695 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:25,720 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:25,784 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:25,788 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:25,813 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:25,879 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:25,903 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:25,962 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:25,967 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:25,992 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:26,062 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:26,086 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:26,144 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:26,148 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:26,174 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:26,237 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:26,262 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:26,328 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:26,331 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:26,357 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:26,420 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:26,445 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:26,504 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:26,509 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:26,533 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:26,600 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:26,625 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:26,686 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:26,692 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:26,716 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:26,790 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:26,814 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:26,817 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:26,888 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:26,913 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:26,971 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:26,978 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:27,004 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:27,067 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:27,093 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:27,157 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:27,159 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:27,183 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:27,248 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:27,275 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:27,336 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:27,340 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:27,364 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:27,430 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:27,456 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:27,520 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:27,524 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:27,547 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:27,611 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:27,636 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:27,695 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:27,702 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:27,727 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:27,789 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:27,798 - INFO - Camera enabled
2025-11-24 18:21:27,798 - INFO - Video thread started with source: Camera
2025-11-24 18:21:27,799 - ERROR - ❌ No camera found!
2025-11-24 18:21:27,815 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:27,944 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:27,944 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:27,945 - INFO - Video thread started with source: Camera
2025-11-24 18:21:27,946 - ERROR - ❌ No camera found!
2025-11-24 18:21:27,970 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:28,043 - INFO - Video thread started with source: Camera
2025-11-24 18:21:28,043 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:28,044 - ERROR - ❌ No camera found!
2025-11-24 18:21:28,046 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:28,071 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:28,136 - INFO - Video thread started with source: Camera
2025-11-24 18:21:28,137 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:28,137 - ERROR - ❌ No camera found!
2025-11-24 18:21:28,140 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:28,164 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:28,234 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:28,236 - INFO - Video thread started with source: Camera
2025-11-24 18:21:28,237 - ERROR - ❌ No camera found!
2025-11-24 18:21:28,241 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:28,266 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:28,334 - INFO - Video thread started with source: Camera
2025-11-24 18:21:28,335 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:28,335 - ERROR - ❌ No camera found!
2025-11-24 18:21:28,339 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:28,363 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:28,426 - INFO - Video thread started with source: Camera
2025-11-24 18:21:28,427 - ERROR - ❌ No camera found!
2025-11-24 18:21:28,429 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:28,454 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:28,458 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:28,522 - INFO - Video thread started with source: Camera
2025-11-24 18:21:28,524 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:28,525 - ERROR - ❌ No camera found!
2025-11-24 18:21:28,550 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:28,554 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:28,619 - INFO - Video thread started with source: Camera
2025-11-24 18:21:28,620 - ERROR - ❌ No camera found!
2025-11-24 18:21:28,622 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:28,646 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:28,652 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:28,711 - INFO - Video thread started with source: Camera
2025-11-24 18:21:28,712 - ERROR - ❌ No camera found!
2025-11-24 18:21:28,715 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:28,741 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:28,746 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:28,804 - INFO - Video thread started with source: Camera
2025-11-24 18:21:28,805 - ERROR - ❌ No camera found!
2025-11-24 18:21:28,808 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:28,836 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:28,839 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:28,902 - INFO - Video thread started with source: Camera
2025-11-24 18:21:28,903 - ERROR - ❌ No camera found!
2025-11-24 18:21:28,905 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:28,930 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:28,936 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,002 - INFO - Video thread started with source: Camera
2025-11-24 18:21:29,003 - ERROR - ❌ No camera found!
2025-11-24 18:21:29,008 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,032 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,038 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,099 - INFO - Video thread started with source: Camera
2025-11-24 18:21:29,100 - ERROR - ❌ No camera found!
2025-11-24 18:21:29,106 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,130 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,133 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,196 - INFO - Video thread started with source: Camera
2025-11-24 18:21:29,197 - ERROR - ❌ No camera found!
2025-11-24 18:21:29,203 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,229 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,231 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,288 - INFO - Video thread started with source: Camera
2025-11-24 18:21:29,289 - ERROR - ❌ No camera found!
2025-11-24 18:21:29,292 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,316 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,323 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,384 - INFO - Video thread started with source: Camera
2025-11-24 18:21:29,387 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,388 - ERROR - ❌ No camera found!
2025-11-24 18:21:29,412 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,417 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,478 - INFO - Video thread started with source: Camera
2025-11-24 18:21:29,480 - ERROR - ❌ No camera found!
2025-11-24 18:21:29,483 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,508 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,514 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,574 - INFO - Video thread started with source: Camera
2025-11-24 18:21:29,575 - ERROR - ❌ No camera found!
2025-11-24 18:21:29,578 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,604 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,609 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,671 - INFO - Video thread started with source: Camera
2025-11-24 18:21:29,673 - ERROR - ❌ No camera found!
2025-11-24 18:21:29,676 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,702 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,706 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,773 - INFO - Video thread started with source: Camera
2025-11-24 18:21:29,775 - ERROR - ❌ No camera found!
2025-11-24 18:21:29,777 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,802 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,807 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,866 - INFO - Video thread started with source: Camera
2025-11-24 18:21:29,867 - ERROR - ❌ No camera found!
2025-11-24 18:21:29,872 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,896 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,901 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,959 - INFO - Video thread started with source: Camera
2025-11-24 18:21:29,960 - ERROR - ❌ No camera found!
2025-11-24 18:21:29,964 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,990 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:29,995 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,055 - INFO - Video thread started with source: Camera
2025-11-24 18:21:30,056 - ERROR - ❌ No camera found!
2025-11-24 18:21:30,059 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,083 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,089 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,150 - INFO - Video thread started with source: Camera
2025-11-24 18:21:30,151 - ERROR - ❌ No camera found!
2025-11-24 18:21:30,154 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,179 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,186 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,243 - INFO - Video thread started with source: Camera
2025-11-24 18:21:30,245 - ERROR - ❌ No camera found!
2025-11-24 18:21:30,248 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,274 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,279 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,334 - INFO - Video thread started with source: Camera
2025-11-24 18:21:30,336 - ERROR - ❌ No camera found!
2025-11-24 18:21:30,339 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,363 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,370 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,427 - INFO - Video thread started with source: Camera
2025-11-24 18:21:30,428 - ERROR - ❌ No camera found!
2025-11-24 18:21:30,431 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,457 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,462 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,521 - INFO - Video thread started with source: Camera
2025-11-24 18:21:30,523 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,524 - ERROR - ❌ No camera found!
2025-11-24 18:21:30,549 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,554 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,621 - INFO - Video thread started with source: Camera
2025-11-24 18:21:30,622 - ERROR - ❌ No camera found!
2025-11-24 18:21:30,625 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,650 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,655 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,714 - INFO - Video thread started with source: Camera
2025-11-24 18:21:30,715 - ERROR - ❌ No camera found!
2025-11-24 18:21:30,719 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,744 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,749 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,805 - INFO - Video thread started with source: Camera
2025-11-24 18:21:30,807 - ERROR - ❌ No camera found!
2025-11-24 18:21:30,810 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,835 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,841 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,902 - INFO - Video thread started with source: Camera
2025-11-24 18:21:30,904 - ERROR - ❌ No camera found!
2025-11-24 18:21:30,907 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,931 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,937 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:30,995 - INFO - Video thread started with source: Camera
2025-11-24 18:21:30,996 - ERROR - ❌ No camera found!
2025-11-24 18:21:30,999 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,025 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,030 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,090 - INFO - Video thread started with source: Camera
2025-11-24 18:21:31,092 - ERROR - ❌ No camera found!
2025-11-24 18:21:31,095 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,121 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,125 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,184 - INFO - Video thread started with source: Camera
2025-11-24 18:21:31,185 - ERROR - ❌ No camera found!
2025-11-24 18:21:31,189 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,213 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,220 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,274 - INFO - Video thread started with source: Camera
2025-11-24 18:21:31,275 - ERROR - ❌ No camera found!
2025-11-24 18:21:31,281 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,308 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,310 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,371 - INFO - Video thread started with source: Camera
2025-11-24 18:21:31,373 - ERROR - ❌ No camera found!
2025-11-24 18:21:31,376 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,400 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,406 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,464 - INFO - Video thread started with source: Camera
2025-11-24 18:21:31,465 - ERROR - ❌ No camera found!
2025-11-24 18:21:31,470 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,495 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,500 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,560 - INFO - Video thread started with source: Camera
2025-11-24 18:21:31,562 - ERROR - ❌ No camera found!
2025-11-24 18:21:31,565 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,593 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,597 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,660 - INFO - Video thread started with source: Camera
2025-11-24 18:21:31,661 - ERROR - ❌ No camera found!
2025-11-24 18:21:31,665 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,692 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,696 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,752 - INFO - Video thread started with source: Camera
2025-11-24 18:21:31,753 - ERROR - ❌ No camera found!
2025-11-24 18:21:31,757 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,782 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,787 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,845 - INFO - Video thread started with source: Camera
2025-11-24 18:21:31,845 - ERROR - ❌ No camera found!
2025-11-24 18:21:31,848 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,874 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,879 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,942 - INFO - Video thread started with source: Camera
2025-11-24 18:21:31,944 - ERROR - ❌ No camera found!
2025-11-24 18:21:31,947 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,974 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:31,977 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:32,044 - INFO - Video thread started with source: Camera
2025-11-24 18:21:32,045 - ERROR - ❌ No camera found!
2025-11-24 18:21:32,049 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:32,077 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:32,080 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:32,143 - INFO - Video thread started with source: Camera
2025-11-24 18:21:32,144 - ERROR - ❌ No camera found!
2025-11-24 18:21:32,148 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:32,175 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:32,178 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:32,236 - INFO - Video thread started with source: Camera
2025-11-24 18:21:32,237 - ERROR - ❌ No camera found!
2025-11-24 18:21:32,240 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:32,265 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:32,271 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:32,334 - INFO - Video thread started with source: Camera
2025-11-24 18:21:32,336 - ERROR - ❌ No camera found!
2025-11-24 18:21:32,341 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:32,365 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:32,371 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:32,434 - INFO - Video thread started with source: Camera
2025-11-24 18:21:32,435 - ERROR - ❌ No camera found!
2025-11-24 18:21:32,438 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:32,465 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:32,469 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:32,526 - INFO - Video thread started with source: Camera
2025-11-24 18:21:32,528 - ERROR - ❌ No camera found!
2025-11-24 18:21:32,532 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:32,559 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:32,562 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:32,619 - INFO - Video thread started with source: Camera
2025-11-24 18:21:32,621 - ERROR - ❌ No camera found!
2025-11-24 18:21:32,625 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:32,649 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:32,654 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:32,713 - INFO - Video thread started with source: Camera
2025-11-24 18:21:32,716 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:32,716 - ERROR - ❌ No camera found!
2025-11-24 18:21:32,742 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:32,747 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:32,816 - INFO - Camera disabled
2025-11-24 18:21:32,817 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:32,881 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:32,907 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:32,981 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:32,983 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:33,010 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:33,072 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:33,096 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:33,156 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:33,159 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:33,183 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:33,253 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:33,280 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:33,340 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:33,344 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:33,367 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:33,432 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:33,459 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:33,516 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:33,522 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:33,547 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:33,613 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:33,639 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:33,704 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:33,704 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:33,729 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:33,799 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:33,826 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:33,829 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:33,891 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:33,916 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:33,975 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:33,981 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:34,008 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:34,070 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:34,096 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:34,100 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:34,165 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:34,192 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:34,250 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:34,256 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:34,280 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:34,350 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:34,374 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:34,431 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:34,438 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:34,462 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:34,528 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:34,550 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:34,556 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:34,622 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:34,646 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:34,704 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:34,710 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:34,733 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:34,801 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:34,827 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:34,893 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:34,898 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:34,924 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:34,999 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:35,071 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:35,078 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:35,102 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:35,164 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:35,169 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:35,194 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:35,259 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:35,283 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:35,288 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:35,350 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:35,377 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:35,438 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:35,445 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:35,469 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:35,528 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:35,536 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:35,561 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:35,624 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:35,648 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:35,655 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:35,716 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:35,743 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:35,804 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:35,807 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:35,833 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:35,901 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:35,929 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:35,931 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:35,994 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:36,020 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:36,025 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:36,089 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:36,112 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:36,172 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:36,177 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:36,200 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:36,269 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:36,294 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:36,295 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:36,361 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:36,386 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:36,447 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:36,454 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:36,480 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:36,543 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:36,545 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:36,571 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:36,637 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:36,661 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:36,722 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:36,726 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:36,751 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:36,817 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:36,820 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:36,846 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:36,913 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:36,939 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:37,007 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:37,014 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:37,039 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:37,102 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:37,128 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:37,130 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:37,193 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:37,216 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:37,277 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:37,282 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:37,308 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:37,373 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:37,397 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:37,457 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:37,462 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:37,487 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:37,559 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:37,583 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:37,589 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:37,655 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:37,680 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:37,742 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:37,748 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:37,774 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:37,835 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:37,835 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:37,861 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:37,930 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:37,954 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,019 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,026 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,050 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,122 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,125 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,149 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,220 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,245 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,310 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,314 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,339 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,410 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,433 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,505 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,506 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,508 - ERROR - Task exception was never retrieved
future: <Task finished name='Task-184744' coro=<WebSocketProtocol13.write_message.<locals>.wrapper() done, defined at /home/tech4biz/work/tools/Driver_DSMS_ADAS/venv/lib/python3.12/site-packages/tornado/websocket.py:1111> exception=WebSocketClosedError()>
Traceback (most recent call last):
  File "/home/tech4biz/work/tools/Driver_DSMS_ADAS/venv/lib/python3.12/site-packages/tornado/websocket.py", line 1113, in wrapper
    await fut
tornado.iostream.StreamClosedError: Stream is closed

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/tech4biz/work/tools/Driver_DSMS_ADAS/venv/lib/python3.12/site-packages/tornado/websocket.py", line 1115, in wrapper
    raise WebSocketClosedError()
tornado.websocket.WebSocketClosedError
2025-11-24 18:21:38,530 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,598 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,626 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,629 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,653 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,678 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,699 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,705 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,728 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,754 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,768 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,782 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,789 - INFO - Video thread started with source: Camera
2025-11-24 18:21:38,792 - ERROR - ❌ No camera found!
2025-11-24 18:21:38,809 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,894 - INFO - Video thread started with source: Camera
2025-11-24 18:21:38,895 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,896 - ERROR - ❌ No camera found!
2025-11-24 18:21:38,899 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,927 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:38,996 - INFO - Video thread started with source: Camera
2025-11-24 18:21:38,997 - ERROR - ❌ No camera found!
2025-11-24 18:21:38,997 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,000 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,028 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,096 - INFO - Video thread started with source: Camera
2025-11-24 18:21:39,098 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,098 - ERROR - ❌ No camera found!
2025-11-24 18:21:39,100 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,128 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,191 - INFO - Video thread started with source: Camera
2025-11-24 18:21:39,192 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,192 - ERROR - ❌ No camera found!
2025-11-24 18:21:39,195 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,221 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,284 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,285 - INFO - Video thread started with source: Camera
2025-11-24 18:21:39,287 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,288 - ERROR - ❌ No camera found!
2025-11-24 18:21:39,314 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,386 - INFO - Video thread started with source: Camera
2025-11-24 18:21:39,388 - ERROR - ❌ No camera found!
2025-11-24 18:21:39,389 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,394 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,419 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,480 - INFO - Video thread started with source: Camera
2025-11-24 18:21:39,481 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,481 - ERROR - ❌ No camera found!
2025-11-24 18:21:39,485 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,512 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,572 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,575 - INFO - Video thread started with source: Camera
2025-11-24 18:21:39,577 - ERROR - ❌ No camera found!
2025-11-24 18:21:39,578 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,605 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,671 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,672 - INFO - Video thread started with source: Camera
2025-11-24 18:21:39,672 - ERROR - ❌ No camera found!
2025-11-24 18:21:39,677 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,700 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,762 - INFO - Video thread started with source: Camera
2025-11-24 18:21:39,764 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,764 - ERROR - ❌ No camera found!
2025-11-24 18:21:39,768 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,792 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,856 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,859 - INFO - Video thread started with source: Camera
2025-11-24 18:21:39,859 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,861 - ERROR - ❌ No camera found!
2025-11-24 18:21:39,883 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,952 - INFO - Video thread started with source: Camera
2025-11-24 18:21:39,952 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,954 - ERROR - ❌ No camera found!
2025-11-24 18:21:39,957 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:39,982 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,044 - INFO - Video thread started with source: Camera
2025-11-24 18:21:40,044 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,045 - ERROR - ❌ No camera found!
2025-11-24 18:21:40,049 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,076 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,146 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,147 - INFO - Video thread started with source: Camera
2025-11-24 18:21:40,148 - ERROR - ❌ No camera found!
2025-11-24 18:21:40,150 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,177 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,244 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,244 - INFO - Video thread started with source: Camera
2025-11-24 18:21:40,245 - ERROR - ❌ No camera found!
2025-11-24 18:21:40,248 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,274 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,337 - INFO - Video thread started with source: Camera
2025-11-24 18:21:40,339 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,339 - ERROR - ❌ No camera found!
2025-11-24 18:21:40,343 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,367 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,434 - INFO - Video thread started with source: Camera
2025-11-24 18:21:40,436 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,437 - ERROR - ❌ No camera found!
2025-11-24 18:21:40,439 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,463 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,528 - INFO - Video thread started with source: Camera
2025-11-24 18:21:40,529 - ERROR - ❌ No camera found!
2025-11-24 18:21:40,530 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,533 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,559 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,623 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,623 - INFO - Video thread started with source: Camera
2025-11-24 18:21:40,624 - ERROR - ❌ No camera found!
2025-11-24 18:21:40,628 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,654 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,716 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,717 - INFO - Video thread started with source: Camera
2025-11-24 18:21:40,720 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,720 - ERROR - ❌ No camera found!
2025-11-24 18:21:40,746 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,811 - INFO - Video thread started with source: Camera
2025-11-24 18:21:40,812 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,813 - ERROR - ❌ No camera found!
2025-11-24 18:21:40,816 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,842 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,902 - INFO - Video thread started with source: Camera
2025-11-24 18:21:40,903 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,904 - ERROR - ❌ No camera found!
2025-11-24 18:21:40,908 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,932 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,995 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:40,996 - INFO - Video thread started with source: Camera
2025-11-24 18:21:40,997 - ERROR - ❌ No camera found!
2025-11-24 18:21:40,999 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:41,025 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:41,089 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:41,089 - INFO - Video thread started with source: Camera
2025-11-24 18:21:41,091 - ERROR - ❌ No camera found!
2025-11-24 18:21:41,093 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:41,116 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:41,183 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:41,186 - INFO - Video thread started with source: Camera
2025-11-24 18:21:41,188 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:41,189 - ERROR - ❌ No camera found!
2025-11-24 18:21:41,213 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:41,279 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:41,282 - INFO - Video thread started with source: Camera
2025-11-24 18:21:41,284 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:41,284 - ERROR - ❌ No camera found!
2025-11-24 18:21:41,308 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:41,373 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:41,375 - INFO - Video thread started with source: Camera
2025-11-24 18:21:41,376 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:41,377 - ERROR - ❌ No camera found!
2025-11-24 18:21:41,400 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:41,467 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:41,468 - INFO - Video thread started with source: Camera
2025-11-24 18:21:41,470 - ERROR - ❌ No camera found!
2025-11-24 18:21:41,474 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:41,498 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:41,561 - INFO - Video thread started with source: Camera
2025-11-24 18:21:41,561 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:41,562 - ERROR - ❌ No camera found!
2025-11-24 18:21:41,566 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:41,590 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:41,653 - INFO - Video thread started with source: Camera
2025-11-24 18:21:41,653 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:41,654 - ERROR - ❌ No camera found!
2025-11-24 18:21:41,658 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:41,682 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:41,811 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:41,814 - INFO - Camera disabled
2025-11-24 18:21:41,815 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:41,843 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:41,914 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:41,917 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:41,944 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:42,024 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:42,098 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:42,100 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:42,128 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:42,191 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:42,214 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:42,276 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:42,279 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:42,306 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:42,376 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:42,399 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:42,460 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:42,467 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:42,493 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:42,557 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:42,581 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:42,644 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:42,648 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:42,673 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:42,739 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:42,763 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:42,823 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:42,825 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:42,849 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:42,915 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:42,942 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:43,002 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:43,005 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:43,028 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:43,095 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:43,119 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:43,177 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:43,183 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:43,210 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:43,274 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:43,276 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:43,299 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:43,368 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:43,395 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:43,457 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:43,463 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:43,487 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:43,557 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:43,580 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:43,648 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:43,649 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:43,676 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:43,740 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:43,763 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:43,824 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:43,830 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:43,858 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:43,929 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:43,956 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:44,020 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:44,027 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:44,050 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:44,117 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:44,146 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:44,231 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:44,256 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:44,331 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:44,357 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:44,418 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:44,420 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:44,445 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:44,515 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:44,541 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:44,601 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:44,604 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:44,630 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:44,700 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:44,727 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:44,794 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:44,797 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:44,824 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:44,888 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:44,913 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:44,978 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:44,985 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:45,011 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:45,069 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:45,075 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:45,098 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:45,166 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:45,193 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:45,253 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:45,258 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:45,283 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:45,346 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:45,349 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:45,375 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:45,439 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:45,462 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:45,525 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:45,528 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:45,553 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:45,621 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:45,646 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:45,708 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:45,711 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:45,734 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:45,805 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:45,829 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:45,887 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:45,894 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:45,917 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:45,989 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:46,014 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:46,075 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:46,082 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:46,108 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:46,175 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:46,200 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:46,261 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:46,267 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:46,295 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:46,360 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:46,383 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:46,445 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:46,448 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:46,473 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:46,539 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:46,563 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:46,629 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:46,633 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:46,659 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:46,741 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:46,811 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:46,813 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:46,838 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:46,907 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:46,932 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:47,002 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:47,004 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:47,029 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:47,095 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:47,121 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:47,186 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:47,188 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:47,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:47,278 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:47,302 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:47,370 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:47,375 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:47,399 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:47,462 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:47,488 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:47,547 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:47,553 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:47,579 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:47,643 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:47,645 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:47,671 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:47,737 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:47,762 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:47,822 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:47,826 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:47,849 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:47,922 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:47,948 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:47,950 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:48,012 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:48,037 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:48,042 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:48,108 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:48,131 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:48,197 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:48,199 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:48,226 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:48,290 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:48,314 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:48,378 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:48,381 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:48,407 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:48,473 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:48,498 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:48,558 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:48,564 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:48,590 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:48,655 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:48,679 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:48,747 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:48,750 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:48,778 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:48,849 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:48,875 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:48,939 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:48,946 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:48,972 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:49,043 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:49,067 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:49,138 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:49,141 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:49,165 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:49,235 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:49,261 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:49,329 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:49,331 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:49,357 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:49,429 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:49,453 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:49,524 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:49,526 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:49,549 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:49,619 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:49,645 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:49,705 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:49,707 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:49,731 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:49,798 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:49,824 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:49,886 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:49,893 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:49,915 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:49,982 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:49,985 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:50,010 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:50,131 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:50,132 - INFO - Camera enabled
2025-11-24 18:21:50,133 - INFO - Video thread started with source: Camera
2025-11-24 18:21:50,134 - ERROR - ❌ No camera found!
2025-11-24 18:21:50,157 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:50,165 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:50,234 - INFO - Video thread started with source: Camera
2025-11-24 18:21:50,235 - ERROR - ❌ No camera found!
2025-11-24 18:21:50,239 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:50,263 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:50,270 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:50,326 - INFO - Video thread started with source: Camera
2025-11-24 18:21:50,327 - ERROR - ❌ No camera found!
2025-11-24 18:21:50,331 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:50,357 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:50,361 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:50,418 - INFO - Video thread started with source: Camera
2025-11-24 18:21:50,419 - ERROR - ❌ No camera found!
2025-11-24 18:21:50,423 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:50,446 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:50,454 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:50,510 - INFO - Video thread started with source: Camera
2025-11-24 18:21:50,511 - ERROR - ❌ No camera found!
2025-11-24 18:21:50,513 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:50,539 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:50,545 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:50,601 - INFO - End of video file reached
2025-11-24 18:21:50,604 - INFO - Video capture loop ended
2025-11-24 18:21:50,604 - INFO - Video thread started with source: Camera
2025-11-24 18:21:50,605 - ERROR - ❌ No camera found!
2025-11-24 18:21:50,640 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:50,697 - INFO - Video thread started with source: Camera
2025-11-24 18:21:50,698 - ERROR - ❌ No camera found!
2025-11-24 18:21:50,786 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:50,787 - INFO - Video thread started with source: Camera
2025-11-24 18:21:50,788 - ERROR - ❌ No camera found!
2025-11-24 18:21:50,878 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:50,879 - INFO - Video thread started with source: Camera
2025-11-24 18:21:50,879 - ERROR - ❌ No camera found!
2025-11-24 18:21:50,967 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:50,968 - INFO - Video thread started with source: Camera
2025-11-24 18:21:50,969 - ERROR - ❌ No camera found!
2025-11-24 18:21:51,057 - INFO - Video thread started with source: Camera
2025-11-24 18:21:51,057 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:51,060 - ERROR - ❌ No camera found!
2025-11-24 18:21:51,146 - INFO - Video thread started with source: Camera
2025-11-24 18:21:51,146 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:51,148 - ERROR - ❌ No camera found!
2025-11-24 18:21:51,234 - INFO - Video thread started with source: Camera
2025-11-24 18:21:51,235 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:51,237 - ERROR - ❌ No camera found!
2025-11-24 18:21:51,324 - INFO - Video thread started with source: Camera
2025-11-24 18:21:51,325 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:51,325 - ERROR - ❌ No camera found!
2025-11-24 18:21:51,412 - INFO - Video thread started with source: Camera
2025-11-24 18:21:51,413 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:51,413 - ERROR - ❌ No camera found!
2025-11-24 18:21:51,501 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:51,501 - INFO - Video thread started with source: Camera
2025-11-24 18:21:51,502 - ERROR - ❌ No camera found!
2025-11-24 18:21:51,591 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:51,591 - INFO - Video thread started with source: Camera
2025-11-24 18:21:51,592 - ERROR - ❌ No camera found!
2025-11-24 18:21:51,680 - INFO - Video thread started with source: Camera
2025-11-24 18:21:51,681 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:51,681 - ERROR - ❌ No camera found!
2025-11-24 18:21:51,768 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:51,768 - INFO - Video thread started with source: Camera
2025-11-24 18:21:51,769 - ERROR - ❌ No camera found!
2025-11-24 18:21:51,856 - INFO - Video thread started with source: Camera
2025-11-24 18:21:51,857 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:51,857 - ERROR - ❌ No camera found!
2025-11-24 18:21:51,942 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:51,943 - INFO - Video thread started with source: Camera
2025-11-24 18:21:51,944 - ERROR - ❌ No camera found!
2025-11-24 18:21:52,031 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:52,031 - INFO - Video thread started with source: Camera
2025-11-24 18:21:52,032 - ERROR - ❌ No camera found!
2025-11-24 18:21:52,123 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:52,123 - INFO - Video thread started with source: Camera
2025-11-24 18:21:52,124 - ERROR - ❌ No camera found!
2025-11-24 18:21:52,213 - INFO - Video thread started with source: Camera
2025-11-24 18:21:52,213 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:52,214 - ERROR - ❌ No camera found!
2025-11-24 18:21:52,300 - INFO - Video thread started with source: Camera
2025-11-24 18:21:52,302 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:52,303 - ERROR - ❌ No camera found!
2025-11-24 18:21:52,392 - INFO - Video thread started with source: Camera
2025-11-24 18:21:52,392 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:52,394 - ERROR - ❌ No camera found!
2025-11-24 18:21:52,484 - INFO - Video thread started with source: Camera
2025-11-24 18:21:52,485 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:52,485 - ERROR - ❌ No camera found!
2025-11-24 18:21:52,571 - INFO - Video thread started with source: Camera
2025-11-24 18:21:52,571 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:52,571 - ERROR - ❌ No camera found!
2025-11-24 18:21:52,660 - INFO - Video thread started with source: Camera
2025-11-24 18:21:52,660 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:52,660 - ERROR - ❌ No camera found!
2025-11-24 18:21:52,748 - INFO - Video thread started with source: Camera
2025-11-24 18:21:52,748 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:52,748 - ERROR - ❌ No camera found!
2025-11-24 18:21:52,836 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:52,836 - INFO - Video thread started with source: Camera
2025-11-24 18:21:52,837 - ERROR - ❌ No camera found!
2025-11-24 18:21:52,924 - INFO - Video thread started with source: Camera
2025-11-24 18:21:52,924 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:52,925 - ERROR - ❌ No camera found!
2025-11-24 18:21:53,013 - INFO - Video thread started with source: Camera
2025-11-24 18:21:53,014 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:53,016 - ERROR - ❌ No camera found!
2025-11-24 18:21:53,101 - INFO - Video thread started with source: Camera
2025-11-24 18:21:53,102 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:53,102 - ERROR - ❌ No camera found!
2025-11-24 18:21:53,190 - INFO - Video thread started with source: Camera
2025-11-24 18:21:53,191 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:53,191 - ERROR - ❌ No camera found!
2025-11-24 18:21:53,278 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:53,279 - INFO - Video thread started with source: Camera
2025-11-24 18:21:53,280 - ERROR - ❌ No camera found!
2025-11-24 18:21:53,367 - INFO - Video thread started with source: Camera
2025-11-24 18:21:53,368 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:53,368 - ERROR - ❌ No camera found!
2025-11-24 18:21:53,464 - INFO - Video thread started with source: Camera
2025-11-24 18:21:53,466 - ERROR - ❌ No camera found!
2025-11-24 18:21:53,499 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:53,554 - INFO - Video thread started with source: Camera
2025-11-24 18:21:53,556 - ERROR - ❌ No camera found!
2025-11-24 18:21:53,590 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:53,645 - INFO - Video thread started with source: Camera
2025-11-24 18:21:53,646 - ERROR - ❌ No camera found!
2025-11-24 18:21:53,680 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:53,738 - INFO - Video thread started with source: Camera
2025-11-24 18:21:53,739 - ERROR - ❌ No camera found!
2025-11-24 18:21:53,773 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:53,828 - INFO - Video thread started with source: Camera
2025-11-24 18:21:53,829 - ERROR - ❌ No camera found!
2025-11-24 18:21:53,864 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:53,920 - INFO - Video thread started with source: Camera
2025-11-24 18:21:53,921 - ERROR - ❌ No camera found!
2025-11-24 18:21:53,955 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:54,010 - INFO - Video thread started with source: Camera
2025-11-24 18:21:54,011 - ERROR - ❌ No camera found!
2025-11-24 18:21:54,045 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:54,102 - INFO - Video thread started with source: Camera
2025-11-24 18:21:54,104 - ERROR - ❌ No camera found!
2025-11-24 18:21:54,137 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:54,192 - INFO - Video thread started with source: Camera
2025-11-24 18:21:54,193 - ERROR - ❌ No camera found!
2025-11-24 18:21:54,227 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:54,282 - INFO - Video thread started with source: Camera
2025-11-24 18:21:54,285 - ERROR - ❌ No camera found!
2025-11-24 18:21:54,317 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:54,372 - INFO - Video thread started with source: Camera
2025-11-24 18:21:54,373 - ERROR - ❌ No camera found!
2025-11-24 18:21:54,407 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:54,480 - INFO - Video thread started with source: Camera
2025-11-24 18:21:54,481 - ERROR - ❌ No camera found!
2025-11-24 18:21:54,516 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:54,586 - INFO - Video thread started with source: Camera
2025-11-24 18:21:54,587 - ERROR - ❌ No camera found!
2025-11-24 18:21:54,622 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:54,677 - INFO - Video thread started with source: Camera
2025-11-24 18:21:54,679 - ERROR - ❌ No camera found!
2025-11-24 18:21:54,713 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:54,770 - INFO - Video thread started with source: Camera
2025-11-24 18:21:54,771 - ERROR - ❌ No camera found!
2025-11-24 18:21:54,806 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:54,862 - INFO - Video thread started with source: Camera
2025-11-24 18:21:54,863 - ERROR - ❌ No camera found!
2025-11-24 18:21:54,897 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:54,960 - INFO - Video thread started with source: Camera
2025-11-24 18:21:54,964 - ERROR - ❌ No camera found!
2025-11-24 18:21:54,996 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:55,054 - INFO - Video thread started with source: Camera
2025-11-24 18:21:55,056 - ERROR - ❌ No camera found!
2025-11-24 18:21:55,089 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:55,162 - INFO - Video thread started with source: Camera
2025-11-24 18:21:55,163 - ERROR - ❌ No camera found!
2025-11-24 18:21:55,197 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:55,265 - INFO - Video thread started with source: Camera
2025-11-24 18:21:55,266 - ERROR - ❌ No camera found!
2025-11-24 18:21:55,300 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:55,365 - INFO - Video thread started with source: Camera
2025-11-24 18:21:55,366 - ERROR - ❌ No camera found!
2025-11-24 18:21:55,400 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:55,459 - INFO - Video thread started with source: Camera
2025-11-24 18:21:55,460 - ERROR - ❌ No camera found!
2025-11-24 18:21:55,494 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:55,549 - INFO - Video thread started with source: Camera
2025-11-24 18:21:55,550 - ERROR - ❌ No camera found!
2025-11-24 18:21:55,585 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:55,644 - INFO - Video thread started with source: Camera
2025-11-24 18:21:55,645 - ERROR - ❌ No camera found!
2025-11-24 18:21:55,678 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:55,741 - INFO - Video thread started with source: Camera
2025-11-24 18:21:55,743 - ERROR - ❌ No camera found!
2025-11-24 18:21:55,775 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:55,833 - INFO - Video thread started with source: Camera
2025-11-24 18:21:55,835 - ERROR - ❌ No camera found!
2025-11-24 18:21:55,868 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:55,934 - INFO - Video thread started with source: Camera
2025-11-24 18:21:55,935 - ERROR - ❌ No camera found!
2025-11-24 18:21:55,970 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:56,034 - INFO - Video thread started with source: Camera
2025-11-24 18:21:56,035 - ERROR - ❌ No camera found!
2025-11-24 18:21:56,069 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:56,125 - INFO - Video thread started with source: Camera
2025-11-24 18:21:56,127 - ERROR - ❌ No camera found!
2025-11-24 18:21:56,161 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:56,221 - INFO - Video thread started with source: Camera
2025-11-24 18:21:56,222 - ERROR - ❌ No camera found!
2025-11-24 18:21:56,256 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:56,313 - INFO - Video thread started with source: Camera
2025-11-24 18:21:56,314 - ERROR - ❌ No camera found!
2025-11-24 18:21:56,347 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:56,404 - INFO - Video thread started with source: Camera
2025-11-24 18:21:56,405 - ERROR - ❌ No camera found!
2025-11-24 18:21:56,440 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:56,500 - INFO - Video thread started with source: Camera
2025-11-24 18:21:56,501 - ERROR - ❌ No camera found!
2025-11-24 18:21:56,534 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:56,595 - INFO - Video thread started with source: Camera
2025-11-24 18:21:56,597 - ERROR - ❌ No camera found!
2025-11-24 18:21:56,630 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:56,691 - INFO - Video thread started with source: Camera
2025-11-24 18:21:56,693 - ERROR - ❌ No camera found!
2025-11-24 18:21:56,726 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:56,783 - INFO - Video thread started with source: Camera
2025-11-24 18:21:56,784 - ERROR - ❌ No camera found!
2025-11-24 18:21:56,819 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:56,874 - INFO - Video thread started with source: Camera
2025-11-24 18:21:56,876 - ERROR - ❌ No camera found!
2025-11-24 18:21:56,909 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:56,971 - INFO - Video thread started with source: Camera
2025-11-24 18:21:56,973 - ERROR - ❌ No camera found!
2025-11-24 18:21:57,006 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:57,062 - INFO - Video thread started with source: Camera
2025-11-24 18:21:57,065 - ERROR - ❌ No camera found!
2025-11-24 18:21:57,097 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:57,154 - INFO - Video thread started with source: Camera
2025-11-24 18:21:57,155 - ERROR - ❌ No camera found!
2025-11-24 18:21:57,190 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:57,246 - INFO - Video thread started with source: Camera
2025-11-24 18:21:57,247 - ERROR - ❌ No camera found!
2025-11-24 18:21:57,280 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:57,339 - INFO - Video thread started with source: Camera
2025-11-24 18:21:57,340 - ERROR - ❌ No camera found!
2025-11-24 18:21:57,375 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:57,434 - INFO - Video thread started with source: Camera
2025-11-24 18:21:57,436 - ERROR - ❌ No camera found!
2025-11-24 18:21:57,470 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:57,528 - INFO - Video thread started with source: Camera
2025-11-24 18:21:57,529 - ERROR - ❌ No camera found!
2025-11-24 18:21:57,563 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:21:57,624 - INFO - Video thread started with source: Camera
2025-11-24 18:21:57,625 - ERROR - ❌ No camera found!
2025-11-24 18:21:57,659 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 43399567 but received 43399566. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-24 18:22:24,172 - INFO - Loading models...
2025-11-24 18:22:24,197 - INFO - ✓ YOLO ONNX loaded
2025-11-24 18:22:24,239 - INFO - ✓ MediaPipe Face Mesh loaded
2025-11-24 18:22:24,244 - INFO - ✓ MediaPipe Pose loaded (for smoke & seatbelt)
2025-11-24 18:22:24,245 - ERROR - Task exception was never retrieved
future: <Task finished name='Task-36' coro=<WebSocketProtocol13.write_message.<locals>.wrapper() done, defined at /home/tech4biz/work/tools/Driver_DSMS_ADAS/venv/lib/python3.12/site-packages/tornado/websocket.py:1111> exception=WebSocketClosedError()>
Traceback (most recent call last):
  File "/home/tech4biz/work/tools/Driver_DSMS_ADAS/venv/lib/python3.12/site-packages/tornado/websocket.py", line 1113, in wrapper
    await fut
tornado.iostream.StreamClosedError: Stream is closed

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/tech4biz/work/tools/Driver_DSMS_ADAS/venv/lib/python3.12/site-packages/tornado/websocket.py", line 1115, in wrapper
    raise WebSocketClosedError()
tornado.websocket.WebSocketClosedError
2025-11-24 18:22:24,313 - INFO - Video thread started with source: Camera
2025-11-24 18:22:24,430 - INFO - ✓ Camera 0 opened successfully
2025-11-24 18:22:24,933 - INFO - Frame 0 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 18:22:25,169 - INFO - Frame 2 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 1
2025-11-24 18:22:25,377 - INFO - Frame 4 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 18:22:25,673 - INFO - Frame 6 | PERCLOS: 0.00 | Yaw: 4.7° | Alerts: 1
2025-11-24 18:22:25,868 - INFO - Frame 8 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-24 18:22:26,054 - INFO - Frame 10 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-24 18:22:26,325 - INFO - Frame 12 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 1
2025-11-24 18:22:26,526 - INFO - Frame 14 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 1
2025-11-24 18:22:26,731 - INFO - Frame 16 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-24 18:22:27,020 - INFO - Frame 18 | PERCLOS: 0.00 | Yaw: 4.7° | Alerts: 1
2025-11-24 18:22:27,231 - INFO - Frame 20 | PERCLOS: 0.00 | Yaw: 4.1° | Alerts: 1
2025-11-24 18:22:27,439 - INFO - Frame 22 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 18:22:27,710 - INFO - Frame 24 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 18:22:27,904 - INFO - Frame 26 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 18:22:28,100 - INFO - Frame 28 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:22:28,378 - INFO - Frame 30 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 18:22:28,576 - INFO - Frame 32 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 18:22:28,770 - INFO - Frame 34 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 18:22:29,042 - INFO - Frame 36 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 18:22:29,255 - INFO - Frame 38 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 18:22:29,457 - INFO - Frame 40 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 18:22:29,738 - INFO - Frame 42 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 18:22:29,947 - INFO - Frame 44 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 18:22:30,144 - INFO - Frame 46 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 18:22:30,420 - INFO - Frame 48 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 18:22:30,618 - INFO - Frame 50 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 18:22:30,811 - INFO - Frame 52 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 18:22:31,094 - INFO - Frame 54 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 18:22:31,298 - INFO - Frame 56 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-24 18:22:31,497 - INFO - Frame 58 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 18:22:31,781 - INFO - Frame 60 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 1
2025-11-24 18:22:31,993 - INFO - Frame 62 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 18:22:32,202 - INFO - Frame 64 | PERCLOS: 0.47 | Yaw: 2.0° | Alerts: 2
2025-11-24 18:22:32,480 - INFO - Frame 66 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 18:22:32,691 - INFO - Frame 68 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 18:22:32,894 - INFO - Frame 70 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:22:33,179 - INFO - Frame 72 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 18:22:33,384 - INFO - Frame 74 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 1
2025-11-24 18:22:33,589 - INFO - Frame 76 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 18:22:33,869 - INFO - Frame 78 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 0
2025-11-24 18:22:34,083 - INFO - Frame 80 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 0
2025-11-24 18:22:34,277 - INFO - Frame 82 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 0
2025-11-24 18:22:34,528 - INFO - Frame 84 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 0
2025-11-24 18:22:34,764 - INFO - Frame 86 | PERCLOS: 0.07 | Yaw: 1.9° | Alerts: 0
2025-11-24 18:22:34,952 - INFO - Frame 88 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 0
2025-11-24 18:22:35,222 - INFO - Frame 90 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 0
2025-11-24 18:22:35,423 - INFO - Frame 92 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 0
2025-11-24 18:22:35,621 - INFO - Frame 94 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 0
2025-11-24 18:22:35,898 - INFO - Frame 96 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 0
2025-11-24 18:22:36,106 - INFO - Frame 98 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 0
2025-11-24 18:22:36,311 - INFO - Frame 100 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 18:22:36,592 - INFO - Frame 102 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 18:22:36,798 - INFO - Frame 104 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 0
2025-11-24 18:22:36,997 - INFO - Frame 106 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 0
2025-11-24 18:22:37,268 - INFO - Frame 108 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 0
2025-11-24 18:22:37,466 - INFO - Frame 110 | PERCLOS: 0.00 | Yaw: 0.2° | Alerts: 0
2025-11-24 18:22:37,654 - INFO - Frame 112 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 18:22:37,931 - INFO - Frame 114 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 0
2025-11-24 18:22:38,139 - INFO - Frame 116 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 18:22:38,343 - INFO - Frame 118 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 0
2025-11-24 18:22:38,623 - INFO - Frame 120 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 0
2025-11-24 18:22:38,829 - INFO - Frame 122 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 0
2025-11-24 18:22:39,035 - INFO - Frame 124 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 0
2025-11-24 18:22:39,316 - INFO - Frame 126 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 0
2025-11-24 18:22:39,528 - INFO - Frame 128 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 0
2025-11-24 18:22:39,729 - INFO - Frame 130 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 0
2025-11-24 18:22:40,012 - INFO - Frame 132 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 0
2025-11-24 18:22:40,219 - INFO - Frame 134 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 0
2025-11-24 18:22:40,421 - INFO - Frame 136 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 0
2025-11-24 18:22:40,704 - INFO - Frame 138 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 0
2025-11-24 18:22:40,913 - INFO - Frame 140 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 0
2025-11-24 18:22:41,117 - INFO - Frame 142 | PERCLOS: 0.14 | Yaw: 1.9° | Alerts: 0
2025-11-24 18:22:41,401 - INFO - Frame 144 | PERCLOS: 0.47 | Yaw: 1.9° | Alerts: 1
2025-11-24 18:22:41,610 - INFO - Frame 146 | PERCLOS: 0.39 | Yaw: 2.1° | Alerts: 1
2025-11-24 18:22:41,813 - INFO - Frame 148 | PERCLOS: 0.45 | Yaw: 1.8° | Alerts: 1
2025-11-24 18:22:42,100 - INFO - Frame 150 | PERCLOS: 0.53 | Yaw: 1.9° | Alerts: 1
2025-11-24 18:22:42,311 - INFO - Frame 152 | PERCLOS: 0.37 | Yaw: 1.9° | Alerts: 1
2025-11-24 18:22:42,508 - INFO - Frame 154 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 0
2025-11-24 18:22:42,775 - INFO - Frame 156 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 0
2025-11-24 18:22:42,972 - INFO - Frame 158 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 0
2025-11-24 18:22:43,161 - INFO - Frame 160 | PERCLOS: 0.34 | Yaw: 1.9° | Alerts: 1
2025-11-24 18:22:43,437 - INFO - Frame 162 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 0
2025-11-24 18:22:43,634 - INFO - Frame 164 | PERCLOS: 0.27 | Yaw: 1.8° | Alerts: 0
2025-11-24 18:22:43,836 - INFO - Frame 166 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 0
2025-11-24 18:22:44,111 - INFO - Frame 168 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 0
2025-11-24 18:22:44,304 - INFO - Frame 170 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 0
2025-11-24 18:22:44,491 - INFO - Frame 172 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 0
2025-11-24 18:22:44,772 - INFO - Frame 174 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 0
2025-11-24 18:22:44,970 - INFO - Frame 176 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 0
2025-11-24 18:22:45,164 - INFO - Frame 178 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 0
2025-11-24 18:22:45,439 - INFO - Frame 180 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 0
2025-11-24 18:22:45,645 - INFO - Frame 182 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 0
2025-11-24 18:22:45,853 - INFO - Frame 184 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 0
2025-11-24 18:22:46,011 - INFO - Frame 186 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:22:46,116 - INFO - Frame 188 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:22:46,302 - INFO - Frame 190 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:22:46,397 - INFO - Frame 192 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:22:46,566 - INFO - Frame 194 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:22:46,657 - INFO - Frame 196 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:22:46,830 - INFO - Frame 198 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:22:46,927 - INFO - Frame 200 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:22:47,100 - INFO - Frame 202 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:22:47,201 - INFO - Frame 204 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:22:47,406 - INFO - Frame 206 | PERCLOS: 0.01 | Yaw: 7.7° | Alerts: 0
2025-11-24 18:22:47,601 - INFO - Frame 208 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 0
2025-11-24 18:22:47,880 - INFO - Frame 210 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 0
2025-11-24 18:22:48,088 - INFO - Frame 212 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 0
2025-11-24 18:22:48,281 - INFO - Frame 214 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 0
2025-11-24 18:22:48,554 - INFO - Frame 216 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 0
2025-11-24 18:22:48,755 - INFO - Frame 218 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 0
2025-11-24 18:22:48,957 - INFO - Frame 220 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 0
2025-11-24 18:22:49,243 - INFO - Frame 222 | PERCLOS: 0.22 | Yaw: -5.1° | Alerts: 0
2025-11-24 18:22:49,451 - INFO - Frame 224 | PERCLOS: 0.00 | Yaw: -7.5° | Alerts: 0
2025-11-24 18:22:49,652 - INFO - Frame 226 | PERCLOS: 0.00 | Yaw: -7.6° | Alerts: 0
2025-11-24 18:22:49,931 - INFO - Frame 228 | PERCLOS: 0.00 | Yaw: -7.3° | Alerts: 0
2025-11-24 18:22:50,138 - INFO - Frame 230 | PERCLOS: 0.00 | Yaw: -6.8° | Alerts: 0
2025-11-24 18:22:50,346 - INFO - Frame 232 | PERCLOS: 0.00 | Yaw: -4.7° | Alerts: 0
2025-11-24 18:22:50,631 - INFO - Frame 234 | PERCLOS: 0.42 | Yaw: -2.3° | Alerts: 1
2025-11-24 18:22:50,844 - INFO - Frame 236 | PERCLOS: 0.00 | Yaw: -3.9° | Alerts: 0
2025-11-24 18:22:51,043 - INFO - Frame 238 | PERCLOS: 0.00 | Yaw: -7.9° | Alerts: 0
2025-11-24 18:22:51,207 - INFO - Frame 240 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:22:51,309 - INFO - Frame 242 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:22:51,493 - INFO - Frame 244 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:22:51,590 - INFO - Frame 246 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:22:51,761 - INFO - Frame 248 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:22:51,889 - INFO - Frame 250 | PERCLOS: 0.00 | Yaw: -8.4° | Alerts: 0
2025-11-24 18:22:52,157 - INFO - Frame 252 | PERCLOS: 0.00 | Yaw: -5.2° | Alerts: 0
2025-11-24 18:22:52,360 - INFO - Frame 254 | PERCLOS: 0.00 | Yaw: -3.8° | Alerts: 0
2025-11-24 18:22:52,557 - INFO - Frame 256 | PERCLOS: 0.00 | Yaw: -2.8° | Alerts: 0
2025-11-24 18:22:52,845 - INFO - Frame 258 | PERCLOS: 0.00 | Yaw: -0.8° | Alerts: 0
2025-11-24 18:22:53,039 - INFO - Frame 260 | PERCLOS: 0.00 | Yaw: -0.0° | Alerts: 0
2025-11-24 18:22:53,238 - INFO - Frame 262 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 0
2025-11-24 18:22:53,508 - INFO - Frame 264 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 0
2025-11-24 18:22:53,708 - INFO - Frame 266 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 0
2025-11-24 18:22:53,905 - INFO - Frame 268 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 0
2025-11-24 18:22:54,166 - INFO - Frame 270 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 0
2025-11-24 18:22:54,375 - INFO - Frame 272 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 0
2025-11-24 18:22:54,563 - INFO - Frame 274 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 0
2025-11-24 18:22:54,836 - INFO - Frame 276 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 1
2025-11-24 18:22:55,028 - INFO - Frame 278 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 1
2025-11-24 18:22:55,217 - INFO - Frame 280 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 1
2025-11-24 18:22:55,484 - INFO - Frame 282 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 1
2025-11-24 18:22:55,676 - INFO - Frame 284 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 1
2025-11-24 18:22:55,863 - INFO - Frame 286 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 1
2025-11-24 18:22:56,151 - INFO - Frame 288 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 1
2025-11-24 18:22:56,360 - INFO - Frame 290 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 1
2025-11-24 18:22:56,568 - INFO - Frame 292 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 1
2025-11-24 18:22:56,845 - INFO - Frame 294 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 1
2025-11-24 18:22:57,066 - INFO - Frame 296 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 1
2025-11-24 18:22:57,279 - INFO - Frame 298 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 1
2025-11-24 18:22:57,562 - INFO - Frame 300 | PERCLOS: 0.35 | Yaw: 0.5° | Alerts: 2
2025-11-24 18:22:57,767 - INFO - Frame 302 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 1
2025-11-24 18:22:57,963 - INFO - Frame 304 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 1
2025-11-24 18:22:58,247 - INFO - Frame 306 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 1
2025-11-24 18:22:58,454 - INFO - Frame 308 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 1
2025-11-24 18:22:58,644 - INFO - Frame 310 | PERCLOS: 0.00 | Yaw: -0.0° | Alerts: 1
2025-11-24 18:22:58,909 - INFO - Frame 312 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 1
2025-11-24 18:22:59,098 - INFO - Frame 314 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:22:59,287 - INFO - Frame 316 | PERCLOS: 0.48 | Yaw: 1.9° | Alerts: 2
2025-11-24 18:22:59,552 - INFO - Frame 318 | PERCLOS: 0.00 | Yaw: 8.4° | Alerts: 1
2025-11-24 18:22:59,747 - INFO - Frame 320 | PERCLOS: 0.00 | Yaw: 10.5° | Alerts: 1
2025-11-24 18:22:59,927 - INFO - Frame 322 | PERCLOS: 0.00 | Yaw: 10.2° | Alerts: 1
2025-11-24 18:23:00,195 - INFO - Frame 324 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-24 18:23:00,392 - INFO - Frame 326 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 18:23:00,587 - INFO - Frame 328 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 18:23:00,863 - INFO - Frame 330 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-24 18:23:01,056 - INFO - Frame 332 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 18:23:01,254 - INFO - Frame 334 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 18:23:01,527 - INFO - Frame 336 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 18:23:01,731 - INFO - Frame 338 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 1
2025-11-24 18:23:01,928 - INFO - Frame 340 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 1
2025-11-24 18:23:02,198 - INFO - Frame 342 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-24 18:23:02,394 - INFO - Frame 344 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-24 18:23:02,578 - INFO - Frame 346 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 1
2025-11-24 18:23:02,838 - INFO - Frame 348 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 1
2025-11-24 18:23:03,042 - INFO - Frame 350 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 18:23:03,229 - INFO - Frame 352 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 2
2025-11-24 18:23:03,493 - INFO - Frame 354 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 2
2025-11-24 18:23:03,689 - INFO - Frame 356 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:23:03,877 - INFO - Frame 358 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 2
2025-11-24 18:23:04,147 - INFO - Frame 360 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 2
2025-11-24 18:23:04,336 - INFO - Frame 362 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 2
2025-11-24 18:23:04,521 - INFO - Frame 364 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 18:23:04,803 - INFO - Frame 366 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 2
2025-11-24 18:23:05,010 - INFO - Frame 368 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 2
2025-11-24 18:23:05,201 - INFO - Frame 370 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 2
2025-11-24 18:23:05,482 - INFO - Frame 372 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 2
2025-11-24 18:23:05,690 - INFO - Frame 374 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 18:23:05,884 - INFO - Frame 376 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 2
2025-11-24 18:23:06,171 - INFO - Frame 378 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 1
2025-11-24 18:23:06,373 - INFO - Frame 380 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 1
2025-11-24 18:23:06,571 - INFO - Frame 382 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 1
2025-11-24 18:23:06,850 - INFO - Frame 384 | PERCLOS: 0.12 | Yaw: 3.8° | Alerts: 1
2025-11-24 18:23:07,040 - INFO - Frame 386 | PERCLOS: 0.09 | Yaw: 4.1° | Alerts: 1
2025-11-24 18:23:07,229 - INFO - Frame 388 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 18:23:07,507 - INFO - Frame 390 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-24 18:23:07,712 - INFO - Frame 392 | PERCLOS: 0.38 | Yaw: 3.7° | Alerts: 2
2025-11-24 18:23:07,906 - INFO - Frame 394 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 18:23:08,171 - INFO - Frame 396 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 18:23:08,366 - INFO - Frame 398 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:23:08,559 - INFO - Frame 400 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 18:23:08,839 - INFO - Frame 402 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 2
2025-11-24 18:23:09,042 - INFO - Frame 404 | PERCLOS: 0.07 | Yaw: 7.4° | Alerts: 1
2025-11-24 18:23:09,238 - INFO - Frame 406 | PERCLOS: 0.00 | Yaw: 8.9° | Alerts: 1
2025-11-24 18:23:09,523 - INFO - Frame 408 | PERCLOS: 0.00 | Yaw: 9.9° | Alerts: 1
2025-11-24 18:23:09,723 - INFO - Frame 410 | PERCLOS: 0.00 | Yaw: 9.7° | Alerts: 1
2025-11-24 18:23:09,914 - INFO - Frame 412 | PERCLOS: 0.00 | Yaw: 9.3° | Alerts: 1
2025-11-24 18:23:10,179 - INFO - Frame 414 | PERCLOS: 0.00 | Yaw: 7.8° | Alerts: 2
2025-11-24 18:23:10,373 - INFO - Frame 416 | PERCLOS: 0.00 | Yaw: 6.9° | Alerts: 2
2025-11-24 18:23:10,553 - INFO - Frame 418 | PERCLOS: 0.00 | Yaw: 6.4° | Alerts: 1
2025-11-24 18:23:10,815 - INFO - Frame 420 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 2
2025-11-24 18:23:11,023 - INFO - Frame 422 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 2
2025-11-24 18:23:11,215 - INFO - Frame 424 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 2
2025-11-24 18:23:11,489 - INFO - Frame 426 | PERCLOS: 0.00 | Yaw: 5.4° | Alerts: 2
2025-11-24 18:23:11,680 - INFO - Frame 428 | PERCLOS: 0.00 | Yaw: 5.4° | Alerts: 2
2025-11-24 18:23:11,875 - INFO - Frame 430 | PERCLOS: 0.00 | Yaw: 5.4° | Alerts: 2
2025-11-24 18:23:12,159 - INFO - Frame 432 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 2
2025-11-24 18:23:12,364 - INFO - Frame 434 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 2
2025-11-24 18:23:12,561 - INFO - Frame 436 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 2
2025-11-24 18:23:12,839 - INFO - Frame 438 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 2
2025-11-24 18:23:13,049 - INFO - Frame 440 | PERCLOS: 0.00 | Yaw: 5.4° | Alerts: 2
2025-11-24 18:23:13,245 - INFO - Frame 442 | PERCLOS: 0.00 | Yaw: 5.4° | Alerts: 2
2025-11-24 18:23:13,527 - INFO - Frame 444 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-24 18:23:13,724 - INFO - Frame 446 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 1
2025-11-24 18:23:13,915 - INFO - Frame 448 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 18:23:14,192 - INFO - Frame 450 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:23:14,383 - INFO - Frame 452 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 18:23:14,565 - INFO - Frame 454 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 18:23:14,826 - INFO - Frame 456 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 18:23:15,012 - INFO - Frame 458 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 18:23:15,174 - INFO - Frame 460 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 18:23:15,370 - INFO - Frame 462 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-24 18:23:15,574 - INFO - Frame 464 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 18:23:15,769 - INFO - Frame 466 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 18:23:16,051 - INFO - Frame 468 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 1
2025-11-24 18:23:16,244 - INFO - Frame 470 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 18:23:16,431 - INFO - Frame 472 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 18:23:16,716 - INFO - Frame 474 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 1
2025-11-24 18:23:16,902 - INFO - Frame 476 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 1
2025-11-24 18:23:17,086 - INFO - Frame 478 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 1
2025-11-24 18:23:17,357 - INFO - Frame 480 | PERCLOS: 0.00 | Yaw: -0.0° | Alerts: 1
2025-11-24 18:23:17,542 - INFO - Frame 482 | PERCLOS: 0.00 | Yaw: -0.8° | Alerts: 1
2025-11-24 18:23:17,721 - INFO - Frame 484 | PERCLOS: 0.42 | Yaw: -1.2° | Alerts: 2
2025-11-24 18:23:17,988 - INFO - Frame 486 | PERCLOS: 0.00 | Yaw: -1.6° | Alerts: 1
2025-11-24 18:23:18,184 - INFO - Frame 488 | PERCLOS: 0.00 | Yaw: -1.8° | Alerts: 1
2025-11-24 18:23:18,369 - INFO - Frame 490 | PERCLOS: 0.00 | Yaw: -1.9° | Alerts: 1
2025-11-24 18:23:18,638 - INFO - Frame 492 | PERCLOS: 0.00 | Yaw: -2.5° | Alerts: 1
2025-11-24 18:23:18,830 - INFO - Frame 494 | PERCLOS: 0.00 | Yaw: -2.6° | Alerts: 1
2025-11-24 18:23:19,020 - INFO - Frame 496 | PERCLOS: 0.00 | Yaw: -2.0° | Alerts: 1
2025-11-24 18:23:19,284 - INFO - Frame 498 | PERCLOS: 0.00 | Yaw: -1.2° | Alerts: 2
2025-11-24 18:23:19,481 - INFO - Frame 500 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 1
2025-11-24 18:23:19,662 - INFO - Frame 502 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 1
2025-11-24 18:23:19,932 - INFO - Frame 504 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 18:23:20,133 - INFO - Frame 506 | PERCLOS: 0.04 | Yaw: 3.0° | Alerts: 1
2025-11-24 18:23:20,369 - INFO - Frame 508 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 18:23:20,640 - INFO - Frame 510 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 2
2025-11-24 18:23:20,831 - INFO - Frame 512 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-24 18:23:21,015 - INFO - Frame 514 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 1
2025-11-24 18:23:21,288 - INFO - Frame 516 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 18:23:21,495 - INFO - Frame 518 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 18:23:21,686 - INFO - Frame 520 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:23:21,965 - INFO - Frame 522 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 18:23:22,173 - INFO - Frame 524 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:23:22,362 - INFO - Frame 526 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 1
2025-11-24 18:23:22,635 - INFO - Frame 528 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 1
2025-11-24 18:23:22,842 - INFO - Frame 530 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:23:23,039 - INFO - Frame 532 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 1
2025-11-24 18:23:23,327 - INFO - Frame 534 | PERCLOS: 0.00 | Yaw: -1.3° | Alerts: 2
2025-11-24 18:23:23,530 - INFO - Frame 536 | PERCLOS: 0.00 | Yaw: -2.0° | Alerts: 1
2025-11-24 18:23:23,712 - INFO - Frame 538 | PERCLOS: 0.00 | Yaw: -2.2° | Alerts: 1
2025-11-24 18:23:23,977 - INFO - Frame 540 | PERCLOS: 0.00 | Yaw: -1.5° | Alerts: 1
2025-11-24 18:23:24,164 - INFO - Frame 542 | PERCLOS: 0.00 | Yaw: -1.2° | Alerts: 1
2025-11-24 18:23:24,341 - INFO - Frame 544 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 1
2025-11-24 18:23:24,609 - INFO - Frame 546 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 1
2025-11-24 18:23:24,810 - INFO - Frame 548 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 2
2025-11-24 18:23:24,993 - INFO - Frame 550 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 1
2025-11-24 18:23:25,273 - INFO - Frame 552 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 2
2025-11-24 18:23:25,483 - INFO - Frame 554 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 1
2025-11-24 18:23:25,666 - INFO - Frame 556 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 1
2025-11-24 18:23:25,938 - INFO - Frame 558 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 1
2025-11-24 18:23:26,129 - INFO - Frame 560 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 1
2025-11-24 18:23:26,316 - INFO - Frame 562 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:23:26,581 - INFO - Frame 564 | PERCLOS: 0.17 | Yaw: 3.0° | Alerts: 1
2025-11-24 18:23:26,776 - INFO - Frame 566 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 1
2025-11-24 18:23:26,976 - INFO - Frame 568 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 1
2025-11-24 18:23:27,259 - INFO - Frame 570 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 18:23:27,456 - INFO - Frame 572 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 1
2025-11-24 18:23:27,651 - INFO - Frame 574 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 18:23:27,925 - INFO - Frame 576 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 18:23:28,116 - INFO - Frame 578 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 18:23:28,313 - INFO - Frame 580 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-24 18:23:28,596 - INFO - Frame 582 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:23:28,805 - INFO - Frame 584 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:23:29,001 - INFO - Frame 586 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:23:29,279 - INFO - Frame 588 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 1
2025-11-24 18:23:29,489 - INFO - Frame 590 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 1
2025-11-24 18:23:29,680 - INFO - Frame 592 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 18:23:29,956 - INFO - Frame 594 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 18:23:30,161 - INFO - Frame 596 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 18:23:30,353 - INFO - Frame 598 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 1
2025-11-24 18:23:30,633 - INFO - Frame 600 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 18:23:30,832 - INFO - Frame 602 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 18:23:31,014 - INFO - Frame 604 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:23:31,275 - INFO - Frame 606 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-24 18:23:31,461 - INFO - Frame 608 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 1
2025-11-24 18:23:31,644 - INFO - Frame 610 | PERCLOS: 0.19 | Yaw: 3.2° | Alerts: 1
2025-11-24 18:23:31,911 - INFO - Frame 612 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 18:23:32,104 - INFO - Frame 614 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-24 18:23:32,299 - INFO - Frame 616 | PERCLOS: 0.00 | Yaw: 4.9° | Alerts: 1
2025-11-24 18:23:32,580 - INFO - Frame 618 | PERCLOS: 0.00 | Yaw: 5.4° | Alerts: 1
2025-11-24 18:23:32,783 - INFO - Frame 620 | PERCLOS: 0.00 | Yaw: 5.4° | Alerts: 1
2025-11-24 18:23:32,976 - INFO - Frame 622 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 1
2025-11-24 18:23:33,261 - INFO - Frame 624 | PERCLOS: 0.00 | Yaw: 5.4° | Alerts: 1
2025-11-24 18:23:33,464 - INFO - Frame 626 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 2
2025-11-24 18:23:33,659 - INFO - Frame 628 | PERCLOS: 0.00 | Yaw: 5.2° | Alerts: 2
2025-11-24 18:23:33,931 - INFO - Frame 630 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 2
2025-11-24 18:23:34,133 - INFO - Frame 632 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 2
2025-11-24 18:23:34,329 - INFO - Frame 634 | PERCLOS: 0.51 | Yaw: 5.2° | Alerts: 3
2025-11-24 18:23:34,610 - INFO - Frame 636 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 2
2025-11-24 18:23:34,815 - INFO - Frame 638 | PERCLOS: 0.00 | Yaw: 4.9° | Alerts: 2
2025-11-24 18:23:35,009 - INFO - Frame 640 | PERCLOS: 0.00 | Yaw: 4.9° | Alerts: 2
2025-11-24 18:23:35,294 - INFO - Frame 642 | PERCLOS: 0.00 | Yaw: 4.9° | Alerts: 2
2025-11-24 18:23:35,493 - INFO - Frame 644 | PERCLOS: 0.00 | Yaw: 4.9° | Alerts: 1
2025-11-24 18:23:35,678 - INFO - Frame 646 | PERCLOS: 0.00 | Yaw: 4.8° | Alerts: 2
2025-11-24 18:23:35,951 - INFO - Frame 648 | PERCLOS: 0.00 | Yaw: 4.9° | Alerts: 2
2025-11-24 18:23:36,147 - INFO - Frame 650 | PERCLOS: 0.00 | Yaw: 4.7° | Alerts: 2
2025-11-24 18:23:36,333 - INFO - Frame 652 | PERCLOS: 0.22 | Yaw: 4.7° | Alerts: 2
2025-11-24 18:23:36,591 - INFO - Frame 654 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 2
2025-11-24 18:23:36,794 - INFO - Frame 656 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 2
2025-11-24 18:23:36,994 - INFO - Frame 658 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 2
2025-11-24 18:23:37,263 - INFO - Frame 660 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 2
2025-11-24 18:23:37,475 - INFO - Frame 662 | PERCLOS: 0.00 | Yaw: 4.1° | Alerts: 1
2025-11-24 18:23:37,671 - INFO - Frame 664 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-24 18:23:37,942 - INFO - Frame 666 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 2
2025-11-24 18:23:38,144 - INFO - Frame 668 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 2
2025-11-24 18:23:38,343 - INFO - Frame 670 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 2
2025-11-24 18:23:38,625 - INFO - Frame 672 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 18:23:38,831 - INFO - Frame 674 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 2
2025-11-24 18:23:39,028 - INFO - Frame 676 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 18:23:39,311 - INFO - Frame 678 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 18:23:39,512 - INFO - Frame 680 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 1
2025-11-24 18:23:39,709 - INFO - Frame 682 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 2
2025-11-24 18:23:39,989 - INFO - Frame 684 | PERCLOS: 0.37 | Yaw: 5.0° | Alerts: 3
2025-11-24 18:23:40,199 - INFO - Frame 686 | PERCLOS: 0.11 | Yaw: 5.1° | Alerts: 2
2025-11-24 18:23:40,394 - INFO - Frame 688 | PERCLOS: 0.21 | Yaw: 5.0° | Alerts: 2
2025-11-24 18:23:40,685 - INFO - Frame 690 | PERCLOS: 0.04 | Yaw: 5.0° | Alerts: 1
2025-11-24 18:23:40,888 - INFO - Frame 692 | PERCLOS: 0.56 | Yaw: 4.9° | Alerts: 3
2025-11-24 18:23:41,083 - INFO - Frame 694 | PERCLOS: 0.55 | Yaw: 4.9° | Alerts: 3
2025-11-24 18:23:41,367 - INFO - Frame 696 | PERCLOS: 0.61 | Yaw: 4.7° | Alerts: 3
2025-11-24 18:23:41,576 - INFO - Frame 698 | PERCLOS: 0.57 | Yaw: 4.5° | Alerts: 3
2025-11-24 18:23:41,777 - INFO - Frame 700 | PERCLOS: 0.56 | Yaw: 4.5° | Alerts: 3
2025-11-24 18:23:42,056 - INFO - Frame 702 | PERCLOS: 0.36 | Yaw: 4.7° | Alerts: 2
2025-11-24 18:23:42,260 - INFO - Frame 704 | PERCLOS: 0.22 | Yaw: 4.6° | Alerts: 1
2025-11-24 18:23:42,459 - INFO - Frame 706 | PERCLOS: 0.00 | Yaw: 4.7° | Alerts: 1
2025-11-24 18:23:42,744 - INFO - Frame 708 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 1
2025-11-24 18:23:42,950 - INFO - Frame 710 | PERCLOS: 0.00 | Yaw: 5.1° | Alerts: 1
2025-11-24 18:23:43,140 - INFO - Frame 712 | PERCLOS: 0.00 | Yaw: 5.1° | Alerts: 1
2025-11-24 18:23:43,421 - INFO - Frame 714 | PERCLOS: 0.25 | Yaw: 5.0° | Alerts: 2
2025-11-24 18:23:43,612 - INFO - Frame 716 | PERCLOS: 0.35 | Yaw: 4.9° | Alerts: 2
2025-11-24 18:23:43,797 - INFO - Frame 718 | PERCLOS: 0.43 | Yaw: 4.7° | Alerts: 2
2025-11-24 18:23:44,072 - INFO - Frame 720 | PERCLOS: 0.44 | Yaw: 4.8° | Alerts: 3
2025-11-24 18:23:44,262 - INFO - Frame 722 | PERCLOS: 0.50 | Yaw: 4.8° | Alerts: 2
2025-11-24 18:23:44,450 - INFO - Frame 724 | PERCLOS: 0.39 | Yaw: 4.8° | Alerts: 3
2025-11-24 18:23:44,717 - INFO - Frame 726 | PERCLOS: 0.53 | Yaw: 4.8° | Alerts: 2
2025-11-24 18:23:44,915 - INFO - Frame 728 | PERCLOS: 0.43 | Yaw: 4.8° | Alerts: 2
2025-11-24 18:23:45,105 - INFO - Frame 730 | PERCLOS: 0.35 | Yaw: 4.9° | Alerts: 2
2025-11-24 18:23:45,371 - INFO - Frame 732 | PERCLOS: 0.08 | Yaw: 4.8° | Alerts: 1
2025-11-24 18:23:45,567 - INFO - Frame 734 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 1
2025-11-24 18:23:45,763 - INFO - Frame 736 | PERCLOS: 0.00 | Yaw: 5.1° | Alerts: 2
2025-11-24 18:23:46,039 - INFO - Frame 738 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 1
2025-11-24 18:23:46,242 - INFO - Frame 740 | PERCLOS: 0.00 | Yaw: 5.8° | Alerts: 1
2025-11-24 18:23:46,437 - INFO - Frame 742 | PERCLOS: 0.00 | Yaw: 5.8° | Alerts: 2
2025-11-24 18:23:46,716 - INFO - Frame 744 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 2
2025-11-24 18:23:46,925 - INFO - Frame 746 | PERCLOS: 0.00 | Yaw: 5.1° | Alerts: 1
2025-11-24 18:23:47,122 - INFO - Frame 748 | PERCLOS: 0.00 | Yaw: 4.9° | Alerts: 1
2025-11-24 18:23:47,402 - INFO - Frame 750 | PERCLOS: 0.00 | Yaw: 5.4° | Alerts: 1
2025-11-24 18:23:47,610 - INFO - Frame 752 | PERCLOS: 0.00 | Yaw: 6.1° | Alerts: 2
2025-11-24 18:23:47,807 - INFO - Frame 754 | PERCLOS: 0.00 | Yaw: 7.2° | Alerts: 1
2025-11-24 18:23:48,071 - INFO - Frame 756 | PERCLOS: 0.00 | Yaw: 9.9° | Alerts: 1
2025-11-24 18:23:48,273 - INFO - Frame 758 | PERCLOS: 0.00 | Yaw: 11.9° | Alerts: 2
2025-11-24 18:23:48,422 - INFO - Frame 760 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:23:48,525 - INFO - Frame 762 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:23:48,710 - INFO - Frame 764 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:23:48,813 - INFO - Frame 766 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:23:48,983 - INFO - Frame 768 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:23:49,081 - INFO - Frame 770 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:23:49,250 - INFO - Frame 772 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:23:49,348 - INFO - Frame 774 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:23:49,519 - INFO - Frame 776 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:23:49,618 - INFO - Frame 778 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:23:49,789 - INFO - Frame 780 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:23:49,887 - INFO - Frame 782 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:23:50,095 - INFO - Frame 784 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:23:50,382 - INFO - Frame 786 | PERCLOS: 0.00 | Yaw: 10.0° | Alerts: 0
2025-11-24 18:23:50,592 - INFO - Frame 788 | PERCLOS: 0.00 | Yaw: 10.7° | Alerts: 0
2025-11-24 18:23:50,789 - INFO - Frame 790 | PERCLOS: 0.00 | Yaw: 10.1° | Alerts: 0
2025-11-24 18:23:51,060 - INFO - Frame 792 | PERCLOS: 0.00 | Yaw: 10.0° | Alerts: 0
2025-11-24 18:23:51,254 - INFO - Frame 794 | PERCLOS: 0.00 | Yaw: 9.6° | Alerts: 0
2025-11-24 18:23:51,441 - INFO - Frame 796 | PERCLOS: 0.00 | Yaw: 9.7° | Alerts: 0
2025-11-24 18:23:51,714 - INFO - Frame 798 | PERCLOS: 0.00 | Yaw: 9.0° | Alerts: 0
2025-11-24 18:23:51,889 - INFO - Frame 800 | PERCLOS: 0.00 | Yaw: 9.5° | Alerts: 0
2025-11-24 18:23:52,012 - INFO - Frame 802 | PERCLOS: 0.00 | Yaw: 9.3° | Alerts: 0
2025-11-24 18:23:52,283 - INFO - Frame 804 | PERCLOS: 0.00 | Yaw: 9.1° | Alerts: 0
2025-11-24 18:23:52,488 - INFO - Frame 806 | PERCLOS: 0.00 | Yaw: 9.0° | Alerts: 0
2025-11-24 18:23:52,680 - INFO - Frame 808 | PERCLOS: 0.00 | Yaw: 9.0° | Alerts: 0
2025-11-24 18:23:52,967 - INFO - Frame 810 | PERCLOS: 0.15 | Yaw: 8.9° | Alerts: 0
2025-11-24 18:23:53,175 - INFO - Frame 812 | PERCLOS: 0.00 | Yaw: 8.2° | Alerts: 0
2025-11-24 18:23:53,369 - INFO - Frame 814 | PERCLOS: 0.00 | Yaw: 7.8° | Alerts: 1
2025-11-24 18:23:53,647 - INFO - Frame 816 | PERCLOS: 0.00 | Yaw: 6.5° | Alerts: 1
2025-11-24 18:23:53,842 - INFO - Frame 818 | PERCLOS: 0.00 | Yaw: 5.8° | Alerts: 1
2025-11-24 18:23:54,025 - INFO - Frame 820 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-24 18:23:54,286 - INFO - Frame 822 | PERCLOS: 0.00 | Yaw: 5.2° | Alerts: 1
2025-11-24 18:23:54,493 - INFO - Frame 824 | PERCLOS: 0.00 | Yaw: 4.7° | Alerts: 1
2025-11-24 18:23:54,681 - INFO - Frame 826 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 1
2025-11-24 18:23:54,946 - INFO - Frame 828 | PERCLOS: 0.00 | Yaw: 4.9° | Alerts: 1
2025-11-24 18:23:55,142 - INFO - Frame 830 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 1
2025-11-24 18:23:55,337 - INFO - Frame 832 | PERCLOS: 0.00 | Yaw: 4.9° | Alerts: 1
2025-11-24 18:23:55,622 - INFO - Frame 834 | PERCLOS: 0.00 | Yaw: 4.9° | Alerts: 1
2025-11-24 18:23:55,823 - INFO - Frame 836 | PERCLOS: 0.00 | Yaw: 4.9° | Alerts: 1
2025-11-24 18:23:56,020 - INFO - Frame 838 | PERCLOS: 0.00 | Yaw: 4.9° | Alerts: 1
2025-11-24 18:23:56,304 - INFO - Frame 840 | PERCLOS: 0.00 | Yaw: 4.9° | Alerts: 2
2025-11-24 18:23:56,511 - INFO - Frame 842 | PERCLOS: 0.00 | Yaw: 4.9° | Alerts: 1
2025-11-24 18:23:56,710 - INFO - Frame 844 | PERCLOS: 0.00 | Yaw: 4.9° | Alerts: 1
2025-11-24 18:23:56,992 - INFO - Frame 846 | PERCLOS: 0.00 | Yaw: 9.0° | Alerts: 1
2025-11-24 18:23:57,162 - INFO - Frame 848 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:23:57,266 - INFO - Frame 850 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:23:57,567 - INFO - Frame 852 | PERCLOS: 0.01 | Yaw: 6.6° | Alerts: 1
2025-11-24 18:23:57,774 - INFO - Frame 854 | PERCLOS: 0.00 | Yaw: 4.1° | Alerts: 1
2025-11-24 18:23:57,972 - INFO - Frame 856 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 18:23:58,257 - INFO - Frame 858 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 1
2025-11-24 18:23:58,459 - INFO - Frame 860 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 18:23:58,657 - INFO - Frame 862 | PERCLOS: 0.26 | Yaw: 3.6° | Alerts: 1
2025-11-24 18:23:58,945 - INFO - Frame 864 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:23:59,149 - INFO - Frame 866 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 1
2025-11-24 18:23:59,329 - INFO - Frame 868 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:23:59,611 - INFO - Frame 870 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 18:23:59,815 - INFO - Frame 872 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 18:24:00,007 - INFO - Frame 874 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 1
2025-11-24 18:24:00,282 - INFO - Frame 876 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 18:24:00,480 - INFO - Frame 878 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 1
2025-11-24 18:24:00,658 - INFO - Frame 880 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 18:24:00,935 - INFO - Frame 882 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 1
2025-11-24 18:24:01,137 - INFO - Frame 884 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 18:24:01,332 - INFO - Frame 886 | PERCLOS: 0.11 | Yaw: 1.8° | Alerts: 1
2025-11-24 18:24:01,612 - INFO - Frame 888 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 1
2025-11-24 18:24:01,815 - INFO - Frame 890 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 1
2025-11-24 18:24:02,004 - INFO - Frame 892 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 1
2025-11-24 18:24:02,271 - INFO - Frame 894 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 1
2025-11-24 18:24:02,471 - INFO - Frame 896 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 1
2025-11-24 18:24:02,661 - INFO - Frame 898 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 1
2025-11-24 18:24:02,930 - INFO - Frame 900 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 18:24:03,140 - INFO - Frame 902 | PERCLOS: 0.60 | Yaw: 3.4° | Alerts: 2
2025-11-24 18:24:03,337 - INFO - Frame 904 | PERCLOS: 0.38 | Yaw: 4.8° | Alerts: 2
2025-11-24 18:24:03,608 - INFO - Frame 906 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 18:24:03,808 - INFO - Frame 908 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 18:24:03,988 - INFO - Frame 910 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 18:24:04,263 - INFO - Frame 912 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 18:24:04,454 - INFO - Frame 914 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 1
2025-11-24 18:24:04,639 - INFO - Frame 916 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 18:24:04,916 - INFO - Frame 918 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 18:24:05,115 - INFO - Frame 920 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:24:05,309 - INFO - Frame 922 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:24:05,585 - INFO - Frame 924 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:24:05,791 - INFO - Frame 926 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 18:24:05,984 - INFO - Frame 928 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 18:24:06,254 - INFO - Frame 930 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:24:06,458 - INFO - Frame 932 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 18:24:06,650 - INFO - Frame 934 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 18:24:06,929 - INFO - Frame 936 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 18:24:07,122 - INFO - Frame 938 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:24:07,308 - INFO - Frame 940 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 18:24:07,583 - INFO - Frame 942 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 18:24:07,791 - INFO - Frame 944 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 18:24:07,990 - INFO - Frame 946 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 18:24:08,278 - INFO - Frame 948 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 18:24:08,482 - INFO - Frame 950 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 18:24:08,679 - INFO - Frame 952 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 18:24:08,962 - INFO - Frame 954 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 18:24:09,156 - INFO - Frame 956 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 18:24:09,352 - INFO - Frame 958 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 18:24:09,622 - INFO - Frame 960 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 18:24:09,814 - INFO - Frame 962 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-24 18:24:10,000 - INFO - Frame 964 | PERCLOS: 0.48 | Yaw: 4.6° | Alerts: 2
2025-11-24 18:24:10,285 - INFO - Frame 966 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 18:24:10,492 - INFO - Frame 968 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-24 18:24:10,687 - INFO - Frame 970 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 18:24:10,967 - INFO - Frame 972 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 1
2025-11-24 18:24:11,179 - INFO - Frame 974 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 1
2025-11-24 18:24:11,373 - INFO - Frame 976 | PERCLOS: 0.07 | Yaw: 3.8° | Alerts: 1
2025-11-24 18:24:11,655 - INFO - Frame 978 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 18:24:11,856 - INFO - Frame 980 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:24:12,041 - INFO - Frame 982 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 1
2025-11-24 18:24:12,307 - INFO - Frame 984 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 1
2025-11-24 18:24:12,503 - INFO - Frame 986 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 1
2025-11-24 18:24:12,687 - INFO - Frame 988 | PERCLOS: 0.00 | Yaw: -0.2° | Alerts: 1
2025-11-24 18:24:12,959 - INFO - Frame 990 | PERCLOS: 0.00 | Yaw: -0.3° | Alerts: 1
2025-11-24 18:24:13,170 - INFO - Frame 992 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 1
2025-11-24 18:24:13,362 - INFO - Frame 994 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 1
2025-11-24 18:24:13,621 - INFO - Frame 996 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 1
2025-11-24 18:24:13,810 - INFO - Frame 998 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 1
2025-11-24 18:24:13,988 - INFO - Frame 1000 | PERCLOS: 0.44 | Yaw: 1.5° | Alerts: 2
2025-11-24 18:24:14,259 - INFO - Frame 1002 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 18:24:14,441 - INFO - Frame 1004 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 18:24:14,625 - INFO - Frame 1006 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 18:24:14,904 - INFO - Frame 1008 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-24 18:24:15,103 - INFO - Frame 1010 | PERCLOS: 0.35 | Yaw: 4.0° | Alerts: 2
2025-11-24 18:24:15,291 - INFO - Frame 1012 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 18:24:15,568 - INFO - Frame 1014 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 18:24:15,777 - INFO - Frame 1016 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 1
2025-11-24 18:24:15,970 - INFO - Frame 1018 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-24 18:24:16,248 - INFO - Frame 1020 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 1
2025-11-24 18:24:16,459 - INFO - Frame 1022 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-24 18:24:16,658 - INFO - Frame 1024 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-24 18:24:16,934 - INFO - Frame 1026 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 1
2025-11-24 18:24:17,131 - INFO - Frame 1028 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 18:24:17,327 - INFO - Frame 1030 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-24 18:24:17,616 - INFO - Frame 1032 | PERCLOS: 0.53 | Yaw: 4.8° | Alerts: 2
2025-11-24 18:24:17,823 - INFO - Frame 1034 | PERCLOS: 0.17 | Yaw: 5.0° | Alerts: 1
2025-11-24 18:24:18,021 - INFO - Frame 1036 | PERCLOS: 0.00 | Yaw: 5.9° | Alerts: 1
2025-11-24 18:24:18,304 - INFO - Frame 1038 | PERCLOS: 0.06 | Yaw: 6.1° | Alerts: 1
2025-11-24 18:24:18,523 - INFO - Frame 1040 | PERCLOS: 0.04 | Yaw: 5.8° | Alerts: 1
2025-11-24 18:24:18,627 - INFO - Frame 1042 | PERCLOS: 0.00 | Yaw: 5.8° | Alerts: 1
2025-11-24 18:24:18,777 - INFO - Frame 1044 | PERCLOS: 0.00 | Yaw: 6.2° | Alerts: 1
2025-11-24 18:24:18,834 - INFO - Video thread started with source: Camera
2025-11-24 18:24:18,835 - ERROR - ❌ No camera found!
2025-11-24 18:24:18,943 - INFO - Video thread started with source: Camera
2025-11-24 18:24:18,945 - ERROR - ❌ No camera found!
2025-11-24 18:24:18,945 - INFO - Frame 1046 | PERCLOS: 0.00 | Yaw: 6.3° | Alerts: 1
2025-11-24 18:24:19,044 - INFO - Video thread started with source: Camera
2025-11-24 18:24:19,045 - ERROR - ❌ No camera found!
2025-11-24 18:24:19,138 - INFO - Video thread started with source: Camera
2025-11-24 18:24:19,139 - INFO - Frame 1048 | PERCLOS: 0.00 | Yaw: 6.4° | Alerts: 1
2025-11-24 18:24:19,139 - ERROR - ❌ No camera found!
2025-11-24 18:24:19,224 - INFO - Video thread started with source: Camera
2025-11-24 18:24:19,225 - ERROR - ❌ No camera found!
2025-11-24 18:24:19,320 - INFO - Video thread started with source: Camera
2025-11-24 18:24:19,321 - ERROR - ❌ No camera found!
2025-11-24 18:24:19,337 - INFO - Frame 1050 | PERCLOS: 0.00 | Yaw: 6.5° | Alerts: 1
2025-11-24 18:24:19,415 - INFO - Video thread started with source: Camera
2025-11-24 18:24:19,416 - ERROR - ❌ No camera found!
2025-11-24 18:24:19,517 - INFO - Video thread started with source: Camera
2025-11-24 18:24:19,518 - ERROR - ❌ No camera found!
2025-11-24 18:24:19,656 - INFO - Frame 1052 | PERCLOS: 0.00 | Yaw: 5.9° | Alerts: 1
2025-11-24 18:24:19,656 - INFO - Video thread started with source: Camera
2025-11-24 18:24:19,657 - ERROR - ❌ No camera found!
2025-11-24 18:24:19,763 - INFO - Video thread started with source: Camera
2025-11-24 18:24:19,764 - ERROR - ❌ No camera found!
2025-11-24 18:24:19,798 - INFO - Frame 1054 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 1
2025-11-24 18:24:19,862 - INFO - Video thread started with source: Camera
2025-11-24 18:24:19,864 - ERROR - ❌ No camera found!
2025-11-24 18:24:19,954 - INFO - Video thread started with source: Camera
2025-11-24 18:24:19,955 - ERROR - ❌ No camera found!
2025-11-24 18:24:20,049 - INFO - Video thread started with source: Camera
2025-11-24 18:24:20,050 - ERROR - ❌ No camera found!
2025-11-24 18:24:20,071 - INFO - Frame 1056 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-24 18:24:20,151 - INFO - Video thread started with source: Camera
2025-11-24 18:24:20,152 - ERROR - ❌ No camera found!
2025-11-24 18:24:20,256 - INFO - Video thread started with source: Camera
2025-11-24 18:24:20,263 - ERROR - ❌ No camera found!
2025-11-24 18:24:20,300 - INFO - Frame 1058 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-24 18:24:20,400 - INFO - Video thread started with source: Camera
2025-11-24 18:24:20,401 - ERROR - ❌ No camera found!
2025-11-24 18:24:20,499 - INFO - Video thread started with source: Camera
2025-11-24 18:24:20,501 - ERROR - ❌ No camera found!
2025-11-24 18:24:20,529 - INFO - Frame 1060 | PERCLOS: 0.00 | Yaw: 5.9° | Alerts: 1
2025-11-24 18:24:20,603 - INFO - Video thread started with source: Camera
2025-11-24 18:24:20,604 - ERROR - ❌ No camera found!
2025-11-24 18:24:20,700 - INFO - Video thread started with source: Camera
2025-11-24 18:24:20,701 - ERROR - ❌ No camera found!
2025-11-24 18:24:20,804 - INFO - Video thread started with source: Camera
2025-11-24 18:24:20,805 - ERROR - ❌ No camera found!
2025-11-24 18:24:20,826 - INFO - Frame 1062 | PERCLOS: 0.00 | Yaw: 6.7° | Alerts: 1
2025-11-24 18:24:20,894 - INFO - Video thread started with source: Camera
2025-11-24 18:24:20,895 - ERROR - ❌ No camera found!
2025-11-24 18:24:20,985 - INFO - Video thread started with source: Camera
2025-11-24 18:24:20,987 - ERROR - ❌ No camera found!
2025-11-24 18:24:21,016 - INFO - Frame 1064 | PERCLOS: 0.00 | Yaw: 7.2° | Alerts: 1
2025-11-24 18:24:21,077 - INFO - Video thread started with source: Camera
2025-11-24 18:24:21,078 - ERROR - ❌ No camera found!
2025-11-24 18:24:21,174 - INFO - Video thread started with source: Camera
2025-11-24 18:24:21,175 - ERROR - ❌ No camera found!
2025-11-24 18:24:21,205 - INFO - Frame 1066 | PERCLOS: 0.00 | Yaw: 7.9° | Alerts: 1
2025-11-24 18:24:21,280 - INFO - Video thread started with source: Camera
2025-11-24 18:24:21,281 - ERROR - ❌ No camera found!
2025-11-24 18:24:21,376 - INFO - Video thread started with source: Camera
2025-11-24 18:24:21,377 - ERROR - ❌ No camera found!
2025-11-24 18:24:21,478 - INFO - Video thread started with source: Camera
2025-11-24 18:24:21,479 - ERROR - ❌ No camera found!
2025-11-24 18:24:21,498 - INFO - Frame 1068 | PERCLOS: 0.00 | Yaw: 10.0° | Alerts: 1
2025-11-24 18:24:21,577 - INFO - Video thread started with source: Camera
2025-11-24 18:24:21,577 - ERROR - ❌ No camera found!
2025-11-24 18:24:21,672 - INFO - Video thread started with source: Camera
2025-11-24 18:24:21,673 - ERROR - ❌ No camera found!
2025-11-24 18:24:21,705 - INFO - Frame 1070 | PERCLOS: 0.00 | Yaw: 10.6° | Alerts: 1
2025-11-24 18:24:21,777 - INFO - Video thread started with source: Camera
2025-11-24 18:24:21,778 - ERROR - ❌ No camera found!
2025-11-24 18:24:21,878 - INFO - Video thread started with source: Camera
2025-11-24 18:24:21,879 - ERROR - ❌ No camera found!
2025-11-24 18:24:21,913 - INFO - Frame 1072 | PERCLOS: 0.00 | Yaw: 11.6° | Alerts: 1
2025-11-24 18:24:21,973 - INFO - Video thread started with source: Camera
2025-11-24 18:24:21,974 - ERROR - ❌ No camera found!
2025-11-24 18:24:22,062 - INFO - Video thread started with source: Camera
2025-11-24 18:24:22,063 - ERROR - ❌ No camera found!
2025-11-24 18:24:22,158 - INFO - Video thread started with source: Camera
2025-11-24 18:24:22,159 - ERROR - ❌ No camera found!
2025-11-24 18:24:22,179 - INFO - Frame 1074 | PERCLOS: 0.00 | Yaw: 11.7° | Alerts: 1
2025-11-24 18:24:22,253 - INFO - Video thread started with source: Camera
2025-11-24 18:24:22,254 - ERROR - ❌ No camera found!
2025-11-24 18:24:22,351 - INFO - Video thread started with source: Camera
2025-11-24 18:24:22,353 - ERROR - ❌ No camera found!
2025-11-24 18:24:22,380 - INFO - Frame 1076 | PERCLOS: 0.00 | Yaw: 12.0° | Alerts: 1
2025-11-24 18:24:22,451 - INFO - Video thread started with source: Camera
2025-11-24 18:24:22,452 - ERROR - ❌ No camera found!
2025-11-24 18:24:22,548 - INFO - Video thread started with source: Camera
2025-11-24 18:24:22,549 - ERROR - ❌ No camera found!
2025-11-24 18:24:22,580 - INFO - Frame 1078 | PERCLOS: 0.00 | Yaw: 11.9° | Alerts: 1
2025-11-24 18:24:22,640 - INFO - Video thread started with source: Camera
2025-11-24 18:24:22,641 - ERROR - ❌ No camera found!
2025-11-24 18:24:22,728 - INFO - Video thread started with source: Camera
2025-11-24 18:24:22,730 - ERROR - ❌ No camera found!
2025-11-24 18:24:22,825 - INFO - Video thread started with source: Camera
2025-11-24 18:24:22,826 - ERROR - ❌ No camera found!
2025-11-24 18:24:22,847 - INFO - Frame 1080 | PERCLOS: 0.00 | Yaw: 11.3° | Alerts: 1
2025-11-24 18:24:22,922 - INFO - Video thread started with source: Camera
2025-11-24 18:24:22,923 - ERROR - ❌ No camera found!
2025-11-24 18:24:23,018 - INFO - Video thread started with source: Camera
2025-11-24 18:24:23,019 - ERROR - ❌ No camera found!
2025-11-24 18:24:23,048 - INFO - Frame 1082 | PERCLOS: 0.00 | Yaw: 11.5° | Alerts: 1
2025-11-24 18:24:23,110 - INFO - Video thread started with source: Camera
2025-11-24 18:24:23,111 - ERROR - ❌ No camera found!
2025-11-24 18:24:23,206 - INFO - Video thread started with source: Camera
2025-11-24 18:24:23,207 - ERROR - ❌ No camera found!
2025-11-24 18:24:23,236 - INFO - Frame 1084 | PERCLOS: 0.00 | Yaw: 11.4° | Alerts: 1
2025-11-24 18:24:23,304 - INFO - Video thread started with source: Camera
2025-11-24 18:24:23,304 - ERROR - ❌ No camera found!
2025-11-24 18:24:23,399 - INFO - Video thread started with source: Camera
2025-11-24 18:24:23,400 - ERROR - ❌ No camera found!
2025-11-24 18:24:23,502 - INFO - Video thread started with source: Camera
2025-11-24 18:24:23,503 - ERROR - ❌ No camera found!
2025-11-24 18:24:23,523 - INFO - Frame 1086 | PERCLOS: 0.00 | Yaw: 11.0° | Alerts: 1
2025-11-24 18:24:23,608 - INFO - Video thread started with source: Camera
2025-11-24 18:24:23,610 - ERROR - ❌ No camera found!
2025-11-24 18:24:23,698 - INFO - Video thread started with source: Camera
2025-11-24 18:24:23,699 - ERROR - ❌ No camera found!
2025-11-24 18:24:23,729 - INFO - Frame 1088 | PERCLOS: 0.00 | Yaw: 10.9° | Alerts: 1
2025-11-24 18:24:23,796 - INFO - Video thread started with source: Camera
2025-11-24 18:24:23,797 - ERROR - ❌ No camera found!
2025-11-24 18:24:23,895 - INFO - Video thread started with source: Camera
2025-11-24 18:24:23,896 - ERROR - ❌ No camera found!
2025-11-24 18:24:23,928 - INFO - Frame 1090 | PERCLOS: 0.00 | Yaw: 10.9° | Alerts: 1
2025-11-24 18:24:23,992 - INFO - Video thread started with source: Camera
2025-11-24 18:24:23,993 - ERROR - ❌ No camera found!
2025-11-24 18:24:24,089 - INFO - Video thread started with source: Camera
2025-11-24 18:24:24,090 - ERROR - ❌ No camera found!
2025-11-24 18:24:24,195 - INFO - Video thread started with source: Camera
2025-11-24 18:24:24,196 - ERROR - ❌ No camera found!
2025-11-24 18:24:24,218 - INFO - Frame 1092 | PERCLOS: 0.00 | Yaw: 10.8° | Alerts: 1
2025-11-24 18:24:24,293 - INFO - Video thread started with source: Camera
2025-11-24 18:24:24,294 - ERROR - ❌ No camera found!
2025-11-24 18:24:24,390 - INFO - Video thread started with source: Camera
2025-11-24 18:24:24,392 - ERROR - ❌ No camera found!
2025-11-24 18:24:24,422 - INFO - Frame 1094 | PERCLOS: 0.00 | Yaw: 11.0° | Alerts: 1
2025-11-24 18:24:24,491 - INFO - Video thread started with source: Camera
2025-11-24 18:24:24,492 - ERROR - ❌ No camera found!
2025-11-24 18:24:24,587 - INFO - Video thread started with source: Camera
2025-11-24 18:24:24,588 - ERROR - ❌ No camera found!
2025-11-24 18:24:24,620 - INFO - Frame 1096 | PERCLOS: 0.00 | Yaw: 10.8° | Alerts: 1
2025-11-24 18:24:24,684 - INFO - Video thread started with source: Camera
2025-11-24 18:24:24,685 - ERROR - ❌ No camera found!
2025-11-24 18:24:24,779 - INFO - Video thread started with source: Camera
2025-11-24 18:24:24,781 - ERROR - ❌ No camera found!
2025-11-24 18:24:24,875 - INFO - Video thread started with source: Camera
2025-11-24 18:24:24,875 - ERROR - ❌ No camera found!
2025-11-24 18:24:24,895 - INFO - Frame 1098 | PERCLOS: 0.00 | Yaw: 11.0° | Alerts: 1
2025-11-24 18:24:24,973 - INFO - Video thread started with source: Camera
2025-11-24 18:24:24,974 - ERROR - ❌ No camera found!
2025-11-24 18:24:25,071 - INFO - Video thread started with source: Camera
2025-11-24 18:24:25,073 - ERROR - ❌ No camera found!
2025-11-24 18:24:25,104 - INFO - Frame 1100 | PERCLOS: 0.00 | Yaw: 10.4° | Alerts: 1
2025-11-24 18:24:25,170 - INFO - Video thread started with source: Camera
2025-11-24 18:24:25,171 - ERROR - ❌ No camera found!
2025-11-24 18:24:25,267 - INFO - Video thread started with source: Camera
2025-11-24 18:24:25,269 - ERROR - ❌ No camera found!
2025-11-24 18:24:25,296 - INFO - Frame 1102 | PERCLOS: 0.00 | Yaw: 11.4° | Alerts: 1
2025-11-24 18:24:25,365 - INFO - Video thread started with source: Camera
2025-11-24 18:24:25,366 - ERROR - ❌ No camera found!
2025-11-24 18:24:25,463 - INFO - Video thread started with source: Camera
2025-11-24 18:24:25,464 - ERROR - ❌ No camera found!
2025-11-24 18:24:25,563 - INFO - Video thread started with source: Camera
2025-11-24 18:24:25,564 - ERROR - ❌ No camera found!
2025-11-24 18:24:25,584 - INFO - Frame 1104 | PERCLOS: 0.00 | Yaw: 11.0° | Alerts: 1
2025-11-24 18:24:25,661 - INFO - Video thread started with source: Camera
2025-11-24 18:24:25,662 - ERROR - ❌ No camera found!
2025-11-24 18:24:25,755 - INFO - Video thread started with source: Camera
2025-11-24 18:24:25,757 - ERROR - ❌ No camera found!
2025-11-24 18:24:25,784 - INFO - Frame 1106 | PERCLOS: 0.00 | Yaw: 11.3° | Alerts: 1
2025-11-24 18:24:25,853 - INFO - Video thread started with source: Camera
2025-11-24 18:24:25,854 - ERROR - ❌ No camera found!
2025-11-24 18:24:25,943 - INFO - Video thread started with source: Camera
2025-11-24 18:24:25,944 - ERROR - ❌ No camera found!
2025-11-24 18:24:25,974 - INFO - Frame 1108 | PERCLOS: 0.00 | Yaw: 10.7° | Alerts: 1
2025-11-24 18:24:26,043 - INFO - Video thread started with source: Camera
2025-11-24 18:24:26,044 - ERROR - ❌ No camera found!
2025-11-24 18:24:26,138 - INFO - Video thread started with source: Camera
2025-11-24 18:24:26,139 - ERROR - ❌ No camera found!
2025-11-24 18:24:26,230 - INFO - Video thread started with source: Camera
2025-11-24 18:24:26,231 - ERROR - ❌ No camera found!
2025-11-24 18:24:26,251 - INFO - Frame 1110 | PERCLOS: 0.00 | Yaw: 10.9° | Alerts: 1
2025-11-24 18:24:26,329 - INFO - Video thread started with source: Camera
2025-11-24 18:24:26,330 - ERROR - ❌ No camera found!
2025-11-24 18:24:26,425 - INFO - Video thread started with source: Camera
2025-11-24 18:24:26,426 - ERROR - ❌ No camera found!
2025-11-24 18:24:26,457 - INFO - Frame 1112 | PERCLOS: 0.00 | Yaw: 10.6° | Alerts: 1
2025-11-24 18:24:26,526 - INFO - Video thread started with source: Camera
2025-11-24 18:24:26,527 - ERROR - ❌ No camera found!
2025-11-24 18:24:26,621 - INFO - Video thread started with source: Camera
2025-11-24 18:24:26,623 - ERROR - ❌ No camera found!
2025-11-24 18:24:26,653 - INFO - Frame 1114 | PERCLOS: 0.00 | Yaw: 10.5° | Alerts: 1
2025-11-24 18:24:26,721 - INFO - Video thread started with source: Camera
2025-11-24 18:24:26,722 - ERROR - ❌ No camera found!
2025-11-24 18:24:26,817 - INFO - Video thread started with source: Camera
2025-11-24 18:24:26,819 - ERROR - ❌ No camera found!
2025-11-24 18:24:26,917 - INFO - Video thread started with source: Camera
2025-11-24 18:24:26,918 - ERROR - ❌ No camera found!
2025-11-24 18:24:26,939 - INFO - Frame 1116 | PERCLOS: 0.00 | Yaw: 10.4° | Alerts: 1
2025-11-24 18:24:27,013 - INFO - Video thread started with source: Camera
2025-11-24 18:24:27,013 - ERROR - ❌ No camera found!
2025-11-24 18:24:27,111 - INFO - Video thread started with source: Camera
2025-11-24 18:24:27,112 - ERROR - ❌ No camera found!
2025-11-24 18:24:27,145 - INFO - Frame 1118 | PERCLOS: 0.00 | Yaw: 10.8° | Alerts: 1
2025-11-24 18:24:27,217 - INFO - Video thread started with source: Camera
2025-11-24 18:24:27,218 - ERROR - ❌ No camera found!
2025-11-24 18:24:27,321 - INFO - Video thread started with source: Camera
2025-11-24 18:24:27,323 - ERROR - ❌ No camera found!
2025-11-24 18:24:27,349 - INFO - Frame 1120 | PERCLOS: 0.00 | Yaw: 10.3° | Alerts: 1
2025-11-24 18:24:27,423 - INFO - Video thread started with source: Camera
2025-11-24 18:24:27,424 - ERROR - ❌ No camera found!
2025-11-24 18:24:27,521 - INFO - Video thread started with source: Camera
2025-11-24 18:24:27,523 - ERROR - ❌ No camera found!
2025-11-24 18:24:27,621 - INFO - Video thread started with source: Camera
2025-11-24 18:24:27,622 - ERROR - ❌ No camera found!
2025-11-24 18:24:27,641 - INFO - Frame 1122 | PERCLOS: 0.00 | Yaw: 10.4° | Alerts: 1
2025-11-24 18:24:27,722 - INFO - Video thread started with source: Camera
2025-11-24 18:24:27,724 - ERROR - ❌ No camera found!
2025-11-24 18:24:27,813 - INFO - Video thread started with source: Camera
2025-11-24 18:24:27,814 - ERROR - ❌ No camera found!
2025-11-24 18:24:27,844 - INFO - Frame 1124 | PERCLOS: 0.00 | Yaw: 10.1° | Alerts: 1
2025-11-24 18:24:27,916 - INFO - Video thread started with source: Camera
2025-11-24 18:24:27,917 - ERROR - ❌ No camera found!
2025-11-24 18:24:28,011 - INFO - Video thread started with source: Camera
2025-11-24 18:24:28,012 - ERROR - ❌ No camera found!
2025-11-24 18:24:28,044 - INFO - Frame 1126 | PERCLOS: 0.00 | Yaw: 9.8° | Alerts: 1
2025-11-24 18:24:28,108 - INFO - Video thread started with source: Camera
2025-11-24 18:24:28,109 - ERROR - ❌ No camera found!
2025-11-24 18:24:28,203 - INFO - Video thread started with source: Camera
2025-11-24 18:24:28,204 - ERROR - ❌ No camera found!
2025-11-24 18:24:28,305 - INFO - Video thread started with source: Camera
2025-11-24 18:24:28,306 - ERROR - ❌ No camera found!
2025-11-24 18:24:28,326 - INFO - Frame 1128 | PERCLOS: 0.00 | Yaw: 6.7° | Alerts: 1
2025-11-24 18:24:28,400 - INFO - Video thread started with source: Camera
2025-11-24 18:24:28,401 - ERROR - ❌ No camera found!
2025-11-24 18:24:28,500 - INFO - Video thread started with source: Camera
2025-11-24 18:24:28,501 - ERROR - ❌ No camera found!
2025-11-24 18:24:28,531 - INFO - Frame 1130 | PERCLOS: 0.00 | Yaw: 5.9° | Alerts: 1
2025-11-24 18:24:28,601 - INFO - Video thread started with source: Camera
2025-11-24 18:24:28,602 - ERROR - ❌ No camera found!
2025-11-24 18:24:28,703 - INFO - Video thread started with source: Camera
2025-11-24 18:24:28,703 - ERROR - ❌ No camera found!
2025-11-24 18:24:28,736 - INFO - Frame 1132 | PERCLOS: 0.00 | Yaw: 5.2° | Alerts: 1
2025-11-24 18:24:28,799 - INFO - Video thread started with source: Camera
2025-11-24 18:24:28,800 - ERROR - ❌ No camera found!
2025-11-24 18:24:28,903 - INFO - Video thread started with source: Camera
2025-11-24 18:24:28,904 - ERROR - ❌ No camera found!
2025-11-24 18:24:29,007 - INFO - Video thread started with source: Camera
2025-11-24 18:24:29,008 - ERROR - ❌ No camera found!
2025-11-24 18:24:29,027 - INFO - Frame 1134 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 18:24:29,102 - INFO - Video thread started with source: Camera
2025-11-24 18:24:29,102 - ERROR - ❌ No camera found!
2025-11-24 18:24:29,195 - INFO - Video thread started with source: Camera
2025-11-24 18:24:29,196 - ERROR - ❌ No camera found!
2025-11-24 18:24:29,227 - INFO - Frame 1136 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 18:24:29,297 - INFO - Video thread started with source: Camera
2025-11-24 18:24:29,298 - ERROR - ❌ No camera found!
2025-11-24 18:24:29,394 - INFO - Video thread started with source: Camera
2025-11-24 18:24:29,395 - ERROR - ❌ No camera found!
2025-11-24 18:24:29,426 - INFO - Frame 1138 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 1
2025-11-24 18:24:29,498 - INFO - Video thread started with source: Camera
2025-11-24 18:24:29,499 - ERROR - ❌ No camera found!
2025-11-24 18:24:29,599 - INFO - Video thread started with source: Camera
2025-11-24 18:24:29,600 - ERROR - ❌ No camera found!
2025-11-24 18:24:29,702 - INFO - Video thread started with source: Camera
2025-11-24 18:24:29,703 - ERROR - ❌ No camera found!
2025-11-24 18:24:29,723 - INFO - Frame 1140 | PERCLOS: 0.00 | Yaw: -4.7° | Alerts: 1
2025-11-24 18:24:29,804 - INFO - Video thread started with source: Camera
2025-11-24 18:24:29,805 - ERROR - ❌ No camera found!
2025-11-24 18:24:29,907 - INFO - Video thread started with source: Camera
2025-11-24 18:24:29,908 - ERROR - ❌ No camera found!
2025-11-24 18:24:29,939 - INFO - Frame 1142 | PERCLOS: 0.00 | Yaw: -6.6° | Alerts: 1
2025-11-24 18:24:30,015 - INFO - Video thread started with source: Camera
2025-11-24 18:24:30,016 - ERROR - ❌ No camera found!
2025-11-24 18:24:30,116 - INFO - Video thread started with source: Camera
2025-11-24 18:24:30,117 - ERROR - ❌ No camera found!
2025-11-24 18:24:30,149 - INFO - Frame 1144 | PERCLOS: 0.00 | Yaw: -7.5° | Alerts: 1
2025-11-24 18:24:30,215 - INFO - Video thread started with source: Camera
2025-11-24 18:24:30,216 - ERROR - ❌ No camera found!
2025-11-24 18:24:30,311 - INFO - Video thread started with source: Camera
2025-11-24 18:24:30,312 - ERROR - ❌ No camera found!
2025-11-24 18:24:30,411 - INFO - Video thread started with source: Camera
2025-11-24 18:24:30,412 - ERROR - ❌ No camera found!
2025-11-24 18:24:30,434 - INFO - Frame 1146 | PERCLOS: 0.00 | Yaw: -7.7° | Alerts: 1
2025-11-24 18:24:30,513 - INFO - Video thread started with source: Camera
2025-11-24 18:24:30,514 - ERROR - ❌ No camera found!
2025-11-24 18:24:30,614 - INFO - Video thread started with source: Camera
2025-11-24 18:24:30,615 - ERROR - ❌ No camera found!
2025-11-24 18:24:30,643 - INFO - Frame 1148 | PERCLOS: 0.00 | Yaw: -7.5° | Alerts: 1
2025-11-24 18:24:30,716 - INFO - Video thread started with source: Camera
2025-11-24 18:24:30,718 - ERROR - ❌ No camera found!
2025-11-24 18:24:30,820 - INFO - Video thread started with source: Camera
2025-11-24 18:24:30,821 - ERROR - ❌ No camera found!
2025-11-24 18:24:30,853 - INFO - Frame 1150 | PERCLOS: 0.00 | Yaw: -7.0° | Alerts: 1
2025-11-24 18:24:30,925 - INFO - Video thread started with source: Camera
2025-11-24 18:24:30,925 - ERROR - ❌ No camera found!
2025-11-24 18:24:31,026 - INFO - Video thread started with source: Camera
2025-11-24 18:24:31,028 - ERROR - ❌ No camera found!
2025-11-24 18:24:31,124 - INFO - Video thread started with source: Camera
2025-11-24 18:24:31,125 - ERROR - ❌ No camera found!
2025-11-24 18:24:31,145 - INFO - Frame 1152 | PERCLOS: 0.00 | Yaw: -6.6° | Alerts: 1
2025-11-24 18:24:31,224 - INFO - Video thread started with source: Camera
2025-11-24 18:24:31,225 - ERROR - ❌ No camera found!
2025-11-24 18:24:31,320 - INFO - Video thread started with source: Camera
2025-11-24 18:24:31,321 - ERROR - ❌ No camera found!
2025-11-24 18:24:31,352 - INFO - Frame 1154 | PERCLOS: 0.00 | Yaw: -7.2° | Alerts: 1
2025-11-24 18:24:31,420 - INFO - Video thread started with source: Camera
2025-11-24 18:24:31,421 - ERROR - ❌ No camera found!
2025-11-24 18:24:31,517 - INFO - Video thread started with source: Camera
2025-11-24 18:24:31,518 - ERROR - ❌ No camera found!
2025-11-24 18:24:31,547 - INFO - Frame 1156 | PERCLOS: 0.00 | Yaw: -7.1° | Alerts: 1
2025-11-24 18:24:31,614 - INFO - Video thread started with source: Camera
2025-11-24 18:24:31,614 - ERROR - ❌ No camera found!
2025-11-24 18:24:31,709 - INFO - Video thread started with source: Camera
2025-11-24 18:24:31,710 - ERROR - ❌ No camera found!
2025-11-24 18:24:31,811 - INFO - Video thread started with source: Camera
2025-11-24 18:24:31,812 - ERROR - ❌ No camera found!
2025-11-24 18:24:31,832 - INFO - Frame 1158 | PERCLOS: 0.00 | Yaw: -7.1° | Alerts: 1
2025-11-24 18:24:31,909 - INFO - Video thread started with source: Camera
2025-11-24 18:24:31,910 - ERROR - ❌ No camera found!
2025-11-24 18:24:32,010 - INFO - Video thread started with source: Camera
2025-11-24 18:24:32,011 - ERROR - ❌ No camera found!
2025-11-24 18:24:32,043 - INFO - Frame 1160 | PERCLOS: 0.00 | Yaw: -7.0° | Alerts: 1
2025-11-24 18:24:32,114 - INFO - Video thread started with source: Camera
2025-11-24 18:24:32,115 - ERROR - ❌ No camera found!
2025-11-24 18:24:32,214 - INFO - Video thread started with source: Camera
2025-11-24 18:24:32,214 - ERROR - ❌ No camera found!
2025-11-24 18:24:32,245 - INFO - Frame 1162 | PERCLOS: 0.00 | Yaw: -6.6° | Alerts: 1
2025-11-24 18:24:32,316 - INFO - Video thread started with source: Camera
2025-11-24 18:24:32,317 - ERROR - ❌ No camera found!
2025-11-24 18:24:32,417 - INFO - Video thread started with source: Camera
2025-11-24 18:24:32,418 - ERROR - ❌ No camera found!
2025-11-24 18:24:32,512 - INFO - Video thread started with source: Camera
2025-11-24 18:24:32,513 - ERROR - ❌ No camera found!
2025-11-24 18:24:32,529 - INFO - Frame 1164 | PERCLOS: 0.00 | Yaw: -2.4° | Alerts: 1
2025-11-24 18:24:32,607 - INFO - Video thread started with source: Camera
2025-11-24 18:24:32,608 - ERROR - ❌ No camera found!
2025-11-24 18:24:32,704 - INFO - Video thread started with source: Camera
2025-11-24 18:24:32,704 - ERROR - ❌ No camera found!
2025-11-24 18:24:32,735 - INFO - Frame 1166 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 1
2025-11-24 18:24:32,801 - INFO - Video thread started with source: Camera
2025-11-24 18:24:32,802 - ERROR - ❌ No camera found!
2025-11-24 18:24:32,900 - INFO - Video thread started with source: Camera
2025-11-24 18:24:32,901 - ERROR - ❌ No camera found!
2025-11-24 18:24:32,932 - INFO - Frame 1168 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 1
2025-11-24 18:24:32,997 - INFO - Video thread started with source: Camera
2025-11-24 18:24:32,998 - ERROR - ❌ No camera found!
2025-11-24 18:24:33,091 - INFO - Video thread started with source: Camera
2025-11-24 18:24:33,092 - ERROR - ❌ No camera found!
2025-11-24 18:24:33,194 - INFO - Video thread started with source: Camera
2025-11-24 18:24:33,195 - ERROR - ❌ No camera found!
2025-11-24 18:24:33,214 - INFO - Frame 1170 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 1
2025-11-24 18:24:33,293 - INFO - Video thread started with source: Camera
2025-11-24 18:24:33,294 - ERROR - ❌ No camera found!
2025-11-24 18:24:33,389 - INFO - Video thread started with source: Camera
2025-11-24 18:24:33,390 - ERROR - ❌ No camera found!
2025-11-24 18:24:33,421 - INFO - Frame 1172 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 18:24:33,489 - INFO - Video thread started with source: Camera
2025-11-24 18:24:33,490 - ERROR - ❌ No camera found!
2025-11-24 18:24:33,594 - INFO - Video thread started with source: Camera
2025-11-24 18:24:33,594 - ERROR - ❌ No camera found!
2025-11-24 18:24:33,626 - INFO - Frame 1174 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 18:24:33,754 - INFO - Video file uploaded: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:24:33,754 - INFO - Video thread started with source: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:24:33,765 - INFO - ✓ Video file opened: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-24 18:24:34,168 - INFO - Frame 1176 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 18:24:34,173 - INFO - Frame 0 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 18:24:34,270 - INFO - Frame 2 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:34,375 - INFO - Frame 4 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:34,379 - INFO - Frame 1178 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 18:24:34,476 - INFO - Frame 6 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:34,580 - INFO - Frame 8 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:34,585 - INFO - Frame 1180 | PERCLOS: 0.00 | Yaw: 4.8° | Alerts: 1
2025-11-24 18:24:34,678 - INFO - Frame 10 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:34,722 - INFO - Frame 12 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:34,813 - INFO - Frame 1182 | PERCLOS: 0.47 | Yaw: 4.5° | Alerts: 2
2025-11-24 18:24:34,819 - INFO - Frame 14 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:34,921 - INFO - Frame 16 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:35,022 - INFO - Frame 18 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:35,032 - INFO - Frame 1184 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-24 18:24:35,114 - INFO - Frame 20 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:35,215 - INFO - Frame 22 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:35,215 - INFO - Frame 1186 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:35,314 - INFO - Frame 24 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:35,358 - INFO - Frame 26 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:35,446 - INFO - Frame 1188 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 18:24:35,455 - INFO - Frame 28 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:35,556 - INFO - Frame 30 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:35,659 - INFO - Frame 32 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:35,671 - INFO - Frame 1190 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 18:24:35,759 - INFO - Frame 34 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:35,860 - INFO - Frame 36 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:35,869 - INFO - Frame 1192 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 18:24:35,960 - INFO - Frame 38 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:36,039 - INFO - Frame 40 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:36,143 - INFO - Frame 42 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:36,168 - INFO - Frame 1194 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 18:24:36,186 - INFO - Frame 44 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:36,275 - INFO - Frame 46 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:36,375 - INFO - Frame 48 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:36,378 - INFO - Frame 1196 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 18:24:36,481 - INFO - Frame 50 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:36,593 - INFO - Frame 52 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:36,606 - INFO - Frame 1198 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 1
2025-11-24 18:24:36,693 - INFO - Frame 54 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:36,795 - INFO - Frame 56 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:36,900 - INFO - Frame 58 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:36,921 - INFO - Frame 1200 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 1
2025-11-24 18:24:37,010 - INFO - Frame 60 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:37,110 - INFO - Frame 62 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:37,111 - INFO - Frame 1202 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:37,153 - INFO - Frame 64 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:37,256 - INFO - Frame 66 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:37,258 - INFO - Frame 1204 | PERCLOS: 0.26 | Yaw: 4.0° | Alerts: 0
2025-11-24 18:24:37,347 - INFO - Frame 68 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:37,450 - INFO - Frame 70 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:37,537 - INFO - Frame 72 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:37,556 - INFO - Frame 1206 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 18:24:37,627 - INFO - Frame 74 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:37,730 - INFO - Frame 1208 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:37,733 - INFO - Frame 76 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:37,828 - INFO - Frame 78 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:37,923 - INFO - Frame 80 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:37,924 - INFO - Frame 1210 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 0
2025-11-24 18:24:38,017 - INFO - Frame 82 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:38,061 - INFO - Frame 84 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:38,154 - INFO - Frame 1212 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 18:24:38,157 - INFO - Frame 86 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:38,242 - INFO - Frame 88 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:38,339 - INFO - Frame 90 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:38,368 - INFO - Frame 1214 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 18:24:38,439 - INFO - Frame 92 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:38,541 - INFO - Frame 1216 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:38,542 - INFO - Frame 94 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:38,643 - INFO - Frame 96 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:38,748 - INFO - Frame 98 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:38,791 - INFO - Frame 1218 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:24:38,853 - INFO - Frame 100 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:38,956 - INFO - Frame 102 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:39,058 - INFO - Frame 1220 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 18:24:39,059 - INFO - Frame 104 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:39,100 - INFO - Frame 106 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:39,182 - INFO - Frame 108 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:39,196 - INFO - Frame 1222 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-24 18:24:39,290 - INFO - Frame 110 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:39,395 - INFO - Frame 112 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:39,490 - INFO - Frame 114 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:39,500 - INFO - Frame 1224 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 18:24:39,586 - INFO - Frame 116 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:39,682 - INFO - Frame 118 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:39,713 - INFO - Frame 1226 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 18:24:39,781 - INFO - Frame 120 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:39,885 - INFO - Frame 1228 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:39,885 - INFO - Frame 122 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:39,927 - INFO - Frame 124 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:40,027 - INFO - Frame 126 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:40,109 - INFO - Frame 1230 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 1
2025-11-24 18:24:40,111 - INFO - Frame 128 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:40,187 - INFO - Frame 130 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:40,282 - INFO - Frame 1232 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:40,282 - INFO - Frame 132 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:40,382 - INFO - Frame 134 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:40,424 - INFO - Frame 1234 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 0
2025-11-24 18:24:40,486 - INFO - Frame 136 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:40,591 - INFO - Frame 138 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:40,591 - INFO - Frame 1236 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:40,633 - INFO - Frame 140 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:40,731 - INFO - Frame 142 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:40,733 - INFO - Frame 1238 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 0
2025-11-24 18:24:40,819 - INFO - Frame 144 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:40,923 - INFO - Frame 146 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:40,932 - INFO - Frame 1240 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 0
2025-11-24 18:24:41,012 - INFO - Frame 148 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:41,108 - INFO - Frame 150 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:41,222 - INFO - Frame 152 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:41,235 - INFO - Frame 1242 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:24:41,317 - INFO - Frame 154 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:41,412 - INFO - Frame 1244 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:41,412 - INFO - Frame 156 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:41,511 - INFO - Frame 158 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:41,553 - INFO - Frame 160 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:41,614 - INFO - Frame 1246 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 0
2025-11-24 18:24:41,639 - INFO - Frame 162 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:41,746 - INFO - Frame 164 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:41,850 - INFO - Frame 1248 | PERCLOS: 0.59 | Yaw: 3.5° | Alerts: 2
2025-11-24 18:24:41,964 - INFO - Frame 166 | PERCLOS: 0.00 | Yaw: -1.8° | Alerts: 0
2025-11-24 18:24:42,071 - INFO - Frame 168 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:42,071 - INFO - Frame 1250 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:42,171 - INFO - Frame 170 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:42,214 - INFO - Frame 1252 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 0
2025-11-24 18:24:42,280 - INFO - Frame 172 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:42,605 - INFO - Frame 174 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:24:42,605 - INFO - Frame 1254 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:24:42,713 - INFO - Frame 176 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:42,818 - INFO - Frame 178 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:42,819 - INFO - Frame 1256 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 1
2025-11-24 18:24:42,924 - INFO - Frame 180 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:42,962 - INFO - Frame 1258 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 1
2025-11-24 18:24:43,028 - INFO - Frame 182 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:43,130 - INFO - Frame 1260 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:43,131 - INFO - Frame 184 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:43,173 - INFO - Frame 186 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:43,259 - INFO - Frame 188 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:43,275 - INFO - Frame 1262 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 0
2025-11-24 18:24:43,358 - INFO - Frame 190 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:43,452 - INFO - Frame 192 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:43,529 - INFO - Frame 1264 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 0
2025-11-24 18:24:43,549 - INFO - Frame 194 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:43,651 - INFO - Frame 196 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:43,743 - INFO - Frame 198 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:43,834 - INFO - Frame 1266 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 18:24:43,844 - INFO - Frame 200 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:44,046 - INFO - Frame 1268 | PERCLOS: 0.35 | Yaw: 3.4° | Alerts: 2
2025-11-24 18:24:44,046 - INFO - Frame 202 | PERCLOS: 0.35 | Yaw: 3.4° | Alerts: 1
2025-11-24 18:24:44,137 - INFO - Frame 204 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:44,180 - INFO - Frame 206 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:44,245 - INFO - Frame 1270 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-24 18:24:44,283 - INFO - Frame 208 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:44,386 - INFO - Frame 210 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:44,543 - INFO - Frame 212 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:44,547 - INFO - Frame 1272 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-24 18:24:44,639 - INFO - Frame 214 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:44,682 - INFO - Frame 216 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:44,748 - INFO - Frame 1274 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 1
2025-11-24 18:24:44,782 - INFO - Frame 218 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:44,877 - INFO - Frame 220 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:44,894 - INFO - Frame 1276 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-24 18:24:44,977 - INFO - Frame 222 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:45,077 - INFO - Frame 224 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:45,181 - INFO - Frame 226 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:45,182 - INFO - Frame 1278 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-24 18:24:45,276 - INFO - Frame 228 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:45,377 - INFO - Frame 230 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:45,407 - INFO - Frame 1280 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 1
2025-11-24 18:24:45,481 - INFO - Frame 232 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:45,692 - INFO - Frame 1282 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-24 18:24:45,790 - INFO - Frame 234 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-24 18:24:45,903 - INFO - Frame 1284 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:45,903 - INFO - Frame 236 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:45,997 - INFO - Frame 238 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:46,089 - INFO - Frame 1286 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:46,089 - INFO - Frame 240 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:46,130 - INFO - Frame 242 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:46,217 - INFO - Frame 244 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:46,229 - INFO - Frame 1288 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 0
2025-11-24 18:24:46,321 - INFO - Frame 246 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:46,413 - INFO - Frame 248 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:46,512 - INFO - Frame 250 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:46,531 - INFO - Frame 1290 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 1
2025-11-24 18:24:46,603 - INFO - Frame 252 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:46,742 - INFO - Frame 1292 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 1
2025-11-24 18:24:46,750 - INFO - Frame 254 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 0
2025-11-24 18:24:47,029 - INFO - Frame 256 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 0
2025-11-24 18:24:47,029 - INFO - Frame 1294 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-24 18:24:47,070 - INFO - Frame 258 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:47,150 - INFO - Frame 260 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:47,245 - INFO - Frame 262 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:47,248 - INFO - Frame 1296 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 1
2025-11-24 18:24:47,329 - INFO - Frame 264 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:47,423 - INFO - Frame 266 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:47,423 - INFO - Frame 1298 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:47,511 - INFO - Frame 268 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:47,612 - INFO - Frame 270 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:47,617 - INFO - Frame 1300 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 0
2025-11-24 18:24:47,653 - INFO - Frame 272 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:47,743 - INFO - Frame 274 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:47,837 - INFO - Frame 1302 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 1
2025-11-24 18:24:47,839 - INFO - Frame 276 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:47,939 - INFO - Frame 278 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:48,021 - INFO - Frame 280 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:48,050 - INFO - Frame 1304 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 1
2025-11-24 18:24:48,061 - INFO - Frame 282 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:48,154 - INFO - Frame 284 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:48,261 - INFO - Frame 286 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:48,273 - INFO - Frame 1306 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 18:24:48,354 - INFO - Frame 288 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:48,460 - INFO - Frame 290 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:48,460 - INFO - Frame 1308 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:48,565 - INFO - Frame 292 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:48,672 - INFO - Frame 294 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:48,672 - INFO - Frame 1310 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 0
2025-11-24 18:24:48,713 - INFO - Frame 296 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:48,809 - INFO - Frame 298 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:48,892 - INFO - Frame 1312 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 0
2025-11-24 18:24:48,914 - INFO - Frame 300 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:49,117 - INFO - Frame 302 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 0
2025-11-24 18:24:49,220 - INFO - Frame 1314 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:24:49,225 - INFO - Frame 304 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:49,322 - INFO - Frame 306 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:49,364 - INFO - Frame 308 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:49,427 - INFO - Frame 1316 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 18:24:49,453 - INFO - Frame 310 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:49,555 - INFO - Frame 312 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:49,572 - INFO - Frame 1318 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 18:24:49,656 - INFO - Frame 314 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:49,745 - INFO - Frame 316 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:49,853 - INFO - Frame 318 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:49,869 - INFO - Frame 1320 | PERCLOS: 0.11 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:24:49,954 - INFO - Frame 320 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:50,056 - INFO - Frame 1322 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:50,056 - INFO - Frame 322 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:50,098 - INFO - Frame 324 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:50,187 - INFO - Frame 326 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:50,204 - INFO - Frame 1324 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 0
2025-11-24 18:24:50,228 - INFO - Frame 328 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:50,266 - INFO - Frame 330 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:50,310 - INFO - Frame 332 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:50,348 - INFO - Frame 334 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:50,364 - INFO - Frame 1326 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 1
2025-11-24 18:24:50,388 - INFO - Frame 336 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:50,427 - INFO - Frame 338 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:50,468 - INFO - Frame 340 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:50,473 - INFO - Frame 1328 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 18:24:50,509 - INFO - Frame 342 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:50,517 - INFO - Video thread started with source: Camera
2025-11-24 18:24:50,519 - ERROR - ❌ No camera found!
2025-11-24 18:24:50,616 - INFO - Frame 344 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:50,618 - INFO - Frame 1330 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:50,618 - INFO - Video thread started with source: Camera
2025-11-24 18:24:50,620 - ERROR - ❌ No camera found!
2025-11-24 18:24:50,662 - INFO - Frame 346 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:50,731 - INFO - Video thread started with source: Camera
2025-11-24 18:24:50,732 - ERROR - ❌ No camera found!
2025-11-24 18:24:50,831 - INFO - Frame 348 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:50,833 - INFO - Video thread started with source: Camera
2025-11-24 18:24:50,834 - ERROR - ❌ No camera found!
2025-11-24 18:24:50,920 - INFO - Frame 1332 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:24:50,921 - INFO - Frame 350 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:50,923 - INFO - Video thread started with source: Camera
2025-11-24 18:24:50,924 - ERROR - ❌ No camera found!
2025-11-24 18:24:51,014 - INFO - Frame 352 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:51,016 - INFO - Video thread started with source: Camera
2025-11-24 18:24:51,017 - ERROR - ❌ No camera found!
2025-11-24 18:24:51,113 - INFO - Frame 1334 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 18:24:51,114 - INFO - Video thread started with source: Camera
2025-11-24 18:24:51,115 - ERROR - ❌ No camera found!
2025-11-24 18:24:51,115 - INFO - Frame 354 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:51,210 - INFO - Frame 356 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:51,212 - INFO - Video thread started with source: Camera
2025-11-24 18:24:51,214 - ERROR - ❌ No camera found!
2025-11-24 18:24:51,248 - INFO - Frame 1336 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 18:24:51,307 - INFO - Video thread started with source: Camera
2025-11-24 18:24:51,308 - INFO - Frame 358 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:51,308 - ERROR - ❌ No camera found!
2025-11-24 18:24:51,403 - INFO - Frame 1338 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:51,403 - INFO - Frame 360 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:51,404 - INFO - Video thread started with source: Camera
2025-11-24 18:24:51,405 - ERROR - ❌ No camera found!
2025-11-24 18:24:51,502 - INFO - Frame 362 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:51,504 - INFO - Video thread started with source: Camera
2025-11-24 18:24:51,504 - ERROR - ❌ No camera found!
2025-11-24 18:24:51,609 - INFO - Frame 1340 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 0
2025-11-24 18:24:51,611 - INFO - Video thread started with source: Camera
2025-11-24 18:24:51,612 - ERROR - ❌ No camera found!
2025-11-24 18:24:51,612 - INFO - Frame 364 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:51,707 - INFO - Video thread started with source: Camera
2025-11-24 18:24:51,708 - ERROR - ❌ No camera found!
2025-11-24 18:24:51,807 - INFO - Video thread started with source: Camera
2025-11-24 18:24:51,808 - ERROR - ❌ No camera found!
2025-11-24 18:24:51,810 - INFO - Frame 1342 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 0
2025-11-24 18:24:51,904 - INFO - Frame 366 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:24:51,906 - INFO - Video thread started with source: Camera
2025-11-24 18:24:51,907 - ERROR - ❌ No camera found!
2025-11-24 18:24:52,008 - INFO - Video thread started with source: Camera
2025-11-24 18:24:52,009 - ERROR - ❌ No camera found!
2025-11-24 18:24:52,010 - INFO - Frame 368 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:52,028 - INFO - Frame 1344 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 1
2025-11-24 18:24:52,110 - INFO - Frame 370 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:52,113 - INFO - Video thread started with source: Camera
2025-11-24 18:24:52,113 - ERROR - ❌ No camera found!
2025-11-24 18:24:52,210 - INFO - Frame 372 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:52,211 - INFO - Frame 1346 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:52,212 - INFO - Video thread started with source: Camera
2025-11-24 18:24:52,213 - ERROR - ❌ No camera found!
2025-11-24 18:24:52,303 - INFO - Frame 374 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:52,304 - INFO - Video thread started with source: Camera
2025-11-24 18:24:52,304 - ERROR - ❌ No camera found!
2025-11-24 18:24:52,400 - INFO - Video thread started with source: Camera
2025-11-24 18:24:52,400 - INFO - Frame 1348 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 0
2025-11-24 18:24:52,400 - INFO - Frame 376 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:52,401 - ERROR - ❌ No camera found!
2025-11-24 18:24:52,499 - INFO - Frame 378 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:52,502 - INFO - Video thread started with source: Camera
2025-11-24 18:24:52,503 - ERROR - ❌ No camera found!
2025-11-24 18:24:52,604 - INFO - Frame 380 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:52,604 - INFO - Video thread started with source: Camera
2025-11-24 18:24:52,605 - ERROR - ❌ No camera found!
2025-11-24 18:24:52,701 - INFO - Frame 1350 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 18:24:52,702 - INFO - Video thread started with source: Camera
2025-11-24 18:24:52,702 - ERROR - ❌ No camera found!
2025-11-24 18:24:52,707 - INFO - Frame 382 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:24:52,795 - INFO - Video thread started with source: Camera
2025-11-24 18:24:52,796 - ERROR - ❌ No camera found!
2025-11-24 18:24:52,901 - INFO - Video thread started with source: Camera
2025-11-24 18:24:52,902 - INFO - Frame 1352 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 18:24:52,902 - ERROR - ❌ No camera found!
2025-11-24 18:24:52,999 - INFO - Frame 384 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 0
2025-11-24 18:24:53,063 - INFO - Video thread started with source: Camera
2025-11-24 18:24:53,064 - ERROR - ❌ No camera found!
2025-11-24 18:24:53,081 - INFO - End of video file reached
2025-11-24 18:24:53,082 - INFO - Video capture loop ended
2025-11-24 18:24:53,097 - INFO - Frame 1354 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 1
2025-11-24 18:24:53,171 - INFO - Video thread started with source: Camera
2025-11-24 18:24:53,173 - ERROR - ❌ No camera found!
2025-11-24 18:24:53,272 - INFO - Video thread started with source: Camera
2025-11-24 18:24:53,274 - ERROR - ❌ No camera found!
2025-11-24 18:24:53,374 - INFO - Video thread started with source: Camera
2025-11-24 18:24:53,375 - ERROR - ❌ No camera found!
2025-11-24 18:24:53,396 - INFO - Frame 1356 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:24:53,465 - INFO - Video thread started with source: Camera
2025-11-24 18:24:53,466 - ERROR - ❌ No camera found!
2025-11-24 18:24:53,554 - INFO - Video thread started with source: Camera
2025-11-24 18:24:53,556 - ERROR - ❌ No camera found!
2025-11-24 18:24:53,587 - INFO - Frame 1358 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 1
2025-11-24 18:24:53,648 - INFO - Video thread started with source: Camera
2025-11-24 18:24:53,649 - ERROR - ❌ No camera found!
2025-11-24 18:24:53,744 - INFO - Video thread started with source: Camera
2025-11-24 18:24:53,745 - ERROR - ❌ No camera found!
2025-11-24 18:24:53,778 - INFO - Frame 1360 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:24:53,848 - INFO - Video thread started with source: Camera
2025-11-24 18:24:53,848 - ERROR - ❌ No camera found!
2025-11-24 18:24:53,947 - INFO - Video thread started with source: Camera
2025-11-24 18:24:53,947 - ERROR - ❌ No camera found!
2025-11-24 18:24:54,044 - INFO - Video thread started with source: Camera
2025-11-24 18:24:54,045 - ERROR - ❌ No camera found!
2025-11-24 18:24:54,065 - INFO - Frame 1362 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 1
2025-11-24 18:24:54,140 - INFO - Video thread started with source: Camera
2025-11-24 18:24:54,141 - ERROR - ❌ No camera found!
2025-11-24 18:24:54,238 - INFO - Video thread started with source: Camera
2025-11-24 18:24:54,238 - ERROR - ❌ No camera found!
2025-11-24 18:24:54,268 - INFO - Frame 1364 | PERCLOS: 0.00 | Yaw: 0.2° | Alerts: 1
2025-11-24 18:24:54,335 - INFO - Video thread started with source: Camera
2025-11-24 18:24:54,336 - ERROR - ❌ No camera found!
2025-11-24 18:24:54,423 - INFO - Video thread started with source: Camera
2025-11-24 18:24:54,425 - ERROR - ❌ No camera found!
2025-11-24 18:24:54,455 - INFO - Frame 1366 | PERCLOS: 0.00 | Yaw: -0.2° | Alerts: 1
2025-11-24 18:24:54,514 - INFO - Video thread started with source: Camera
2025-11-24 18:24:54,515 - ERROR - ❌ No camera found!
2025-11-24 18:24:54,605 - INFO - Video thread started with source: Camera
2025-11-24 18:24:54,606 - ERROR - ❌ No camera found!
2025-11-24 18:24:54,705 - INFO - Video thread started with source: Camera
2025-11-24 18:24:54,706 - ERROR - ❌ No camera found!
2025-11-24 18:24:54,725 - INFO - Frame 1368 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 1
2025-11-24 18:24:54,799 - INFO - Video thread started with source: Camera
2025-11-24 18:24:54,800 - ERROR - ❌ No camera found!
2025-11-24 18:24:54,894 - INFO - Video thread started with source: Camera
2025-11-24 18:24:54,895 - ERROR - ❌ No camera found!
2025-11-24 18:24:54,925 - INFO - Frame 1370 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 1
2025-11-24 18:24:54,996 - INFO - Video thread started with source: Camera
2025-11-24 18:24:54,997 - ERROR - ❌ No camera found!
2025-11-24 18:24:55,089 - INFO - Video thread started with source: Camera
2025-11-24 18:24:55,090 - ERROR - ❌ No camera found!
2025-11-24 18:24:55,122 - INFO - Frame 1372 | PERCLOS: 0.00 | Yaw: -0.9° | Alerts: 1
2025-11-24 18:24:55,184 - INFO - Video thread started with source: Camera
2025-11-24 18:24:55,185 - ERROR - ❌ No camera found!
2025-11-24 18:24:55,275 - INFO - Video thread started with source: Camera
2025-11-24 18:24:55,276 - ERROR - ❌ No camera found!
2025-11-24 18:24:55,373 - INFO - Video thread started with source: Camera
2025-11-24 18:24:55,374 - ERROR - ❌ No camera found!
2025-11-24 18:24:55,393 - INFO - Frame 1374 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 1
2025-11-24 18:24:55,469 - INFO - Video thread started with source: Camera
2025-11-24 18:24:55,470 - ERROR - ❌ No camera found!
2025-11-24 18:24:55,569 - INFO - Video thread started with source: Camera
2025-11-24 18:24:55,570 - ERROR - ❌ No camera found!
2025-11-24 18:24:55,602 - INFO - Frame 1376 | PERCLOS: 0.35 | Yaw: -0.9° | Alerts: 2
2025-11-24 18:24:55,674 - INFO - Video thread started with source: Camera
2025-11-24 18:24:55,675 - ERROR - ❌ No camera found!
2025-11-24 18:24:55,767 - INFO - Video thread started with source: Camera
2025-11-24 18:24:55,768 - ERROR - ❌ No camera found!
2025-11-24 18:24:55,798 - INFO - Frame 1378 | PERCLOS: 0.00 | Yaw: -0.9° | Alerts: 1
2025-11-24 18:24:55,873 - INFO - Video thread started with source: Camera
2025-11-24 18:24:55,874 - ERROR - ❌ No camera found!
2025-11-24 18:24:55,973 - INFO - Video thread started with source: Camera
2025-11-24 18:24:55,974 - ERROR - ❌ No camera found!
2025-11-24 18:24:56,077 - INFO - Video thread started with source: Camera
2025-11-24 18:24:56,078 - ERROR - ❌ No camera found!
2025-11-24 18:24:56,097 - INFO - Frame 1380 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 1
2025-11-24 18:24:56,176 - INFO - Video thread started with source: Camera
2025-11-24 18:24:56,176 - ERROR - ❌ No camera found!
2025-11-24 18:24:56,277 - INFO - Video thread started with source: Camera
2025-11-24 18:24:56,278 - ERROR - ❌ No camera found!
2025-11-24 18:24:56,308 - INFO - Frame 1382 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 1
2025-11-24 18:24:56,374 - INFO - Video thread started with source: Camera
2025-11-24 18:24:56,375 - ERROR - ❌ No camera found!
2025-11-24 18:24:56,469 - INFO - Video thread started with source: Camera
2025-11-24 18:24:56,470 - ERROR - ❌ No camera found!
2025-11-24 18:24:56,501 - INFO - Frame 1384 | PERCLOS: 0.00 | Yaw: -1.1° | Alerts: 1
2025-11-24 18:24:56,569 - INFO - Video thread started with source: Camera
2025-11-24 18:24:56,570 - ERROR - ❌ No camera found!
2025-11-24 18:24:56,662 - INFO - Video thread started with source: Camera
2025-11-24 18:24:56,663 - ERROR - ❌ No camera found!
2025-11-24 18:24:56,760 - INFO - Video thread started with source: Camera
2025-11-24 18:24:56,761 - ERROR - ❌ No camera found!
2025-11-24 18:24:56,781 - INFO - Frame 1386 | PERCLOS: 0.00 | Yaw: -1.1° | Alerts: 1
2025-11-24 18:24:56,850 - INFO - Video thread started with source: Camera
2025-11-24 18:24:56,851 - ERROR - ❌ No camera found!
2025-11-24 18:24:56,952 - INFO - Video thread started with source: Camera
2025-11-24 18:24:56,953 - ERROR - ❌ No camera found!
2025-11-24 18:24:56,984 - INFO - Frame 1388 | PERCLOS: 0.00 | Yaw: -1.1° | Alerts: 1
2025-11-24 18:24:57,050 - INFO - Video thread started with source: Camera
2025-11-24 18:24:57,051 - ERROR - ❌ No camera found!
2025-11-24 18:24:57,149 - INFO - Video thread started with source: Camera
2025-11-24 18:24:57,150 - ERROR - ❌ No camera found!
2025-11-24 18:24:57,181 - INFO - Frame 1390 | PERCLOS: 0.00 | Yaw: -0.9° | Alerts: 1
2025-11-24 18:24:57,247 - INFO - Video thread started with source: Camera
2025-11-24 18:24:57,248 - ERROR - ❌ No camera found!
2025-11-24 18:24:57,376 - ERROR - ❌ No camera found!
2025-11-24 18:24:57,376 - INFO - Video thread started with source: Camera
2025-11-24 18:24:57,488 - INFO - Video thread started with source: Camera
2025-11-24 18:24:57,489 - ERROR - ❌ No camera found!
2025-11-24 18:24:57,509 - INFO - Frame 1392 | PERCLOS: 0.00 | Yaw: -0.9° | Alerts: 1
2025-11-24 18:24:57,587 - INFO - Video thread started with source: Camera
2025-11-24 18:24:57,589 - ERROR - ❌ No camera found!
2025-11-24 18:24:57,689 - INFO - Video thread started with source: Camera
2025-11-24 18:24:57,690 - ERROR - ❌ No camera found!
2025-11-24 18:24:57,720 - INFO - Frame 1394 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 1
2025-11-24 18:24:57,794 - INFO - Video thread started with source: Camera
2025-11-24 18:24:57,795 - ERROR - ❌ No camera found!
2025-11-24 18:24:57,892 - INFO - Video thread started with source: Camera
2025-11-24 18:24:57,893 - ERROR - ❌ No camera found!
2025-11-24 18:24:57,923 - INFO - Frame 1396 | PERCLOS: 0.00 | Yaw: -1.1° | Alerts: 1
2025-11-24 18:24:57,996 - INFO - Video thread started with source: Camera
2025-11-24 18:24:57,997 - ERROR - ❌ No camera found!
2025-11-24 18:24:58,097 - INFO - Video thread started with source: Camera
2025-11-24 18:24:58,098 - ERROR - ❌ No camera found!
2025-11-24 18:24:58,195 - INFO - Video thread started with source: Camera
2025-11-24 18:24:58,196 - ERROR - ❌ No camera found!
2025-11-24 18:24:58,214 - INFO - Frame 1398 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 1
2025-11-24 18:24:58,293 - INFO - Video thread started with source: Camera
2025-11-24 18:24:58,293 - ERROR - ❌ No camera found!
2025-11-24 18:24:58,388 - INFO - Video thread started with source: Camera
2025-11-24 18:24:58,389 - ERROR - ❌ No camera found!
2025-11-24 18:24:58,418 - INFO - Frame 1400 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 1
2025-11-24 18:24:58,485 - INFO - Video thread started with source: Camera
2025-11-24 18:24:58,486 - ERROR - ❌ No camera found!
2025-11-24 18:24:58,581 - INFO - Video thread started with source: Camera
2025-11-24 18:24:58,582 - ERROR - ❌ No camera found!
2025-11-24 18:24:58,613 - INFO - Frame 1402 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 1
2025-11-24 18:24:58,677 - INFO - Video thread started with source: Camera
2025-11-24 18:24:58,678 - ERROR - ❌ No camera found!
2025-11-24 18:24:58,774 - INFO - Video thread started with source: Camera
2025-11-24 18:24:58,775 - ERROR - ❌ No camera found!
2025-11-24 18:24:58,872 - INFO - Video thread started with source: Camera
2025-11-24 18:24:58,873 - ERROR - ❌ No camera found!
2025-11-24 18:24:58,890 - INFO - Frame 1404 | PERCLOS: 0.00 | Yaw: -0.8° | Alerts: 1
2025-11-24 18:24:58,967 - INFO - Video thread started with source: Camera
2025-11-24 18:24:58,968 - ERROR - ❌ No camera found!
2025-11-24 18:24:59,061 - INFO - Video thread started with source: Camera
2025-11-24 18:24:59,062 - ERROR - ❌ No camera found!
2025-11-24 18:24:59,094 - INFO - Frame 1406 | PERCLOS: 0.40 | Yaw: -0.4° | Alerts: 2
2025-11-24 18:24:59,152 - INFO - Video thread started with source: Camera
2025-11-24 18:24:59,153 - ERROR - ❌ No camera found!
2025-11-24 18:24:59,241 - INFO - Video thread started with source: Camera
2025-11-24 18:24:59,242 - ERROR - ❌ No camera found!
2025-11-24 18:24:59,272 - INFO - Frame 1408 | PERCLOS: 0.00 | Yaw: -0.2° | Alerts: 1
2025-11-24 18:24:59,334 - INFO - Video thread started with source: Camera
2025-11-24 18:24:59,334 - ERROR - ❌ No camera found!
2025-11-24 18:24:59,430 - INFO - Video thread started with source: Camera
2025-11-24 18:24:59,431 - ERROR - ❌ No camera found!
2025-11-24 18:24:59,524 - INFO - Video thread started with source: Camera
2025-11-24 18:24:59,526 - ERROR - ❌ No camera found!
2025-11-24 18:24:59,543 - INFO - Frame 1410 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 1
2025-11-24 18:24:59,622 - INFO - Video thread started with source: Camera
2025-11-24 18:24:59,623 - ERROR - ❌ No camera found!
2025-11-24 18:24:59,719 - INFO - Video thread started with source: Camera
2025-11-24 18:24:59,720 - ERROR - ❌ No camera found!
2025-11-24 18:24:59,750 - INFO - Frame 1412 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 1
2025-11-24 18:24:59,816 - INFO - Video thread started with source: Camera
2025-11-24 18:24:59,817 - ERROR - ❌ No camera found!
2025-11-24 18:24:59,910 - INFO - Video thread started with source: Camera
2025-11-24 18:24:59,912 - ERROR - ❌ No camera found!
2025-11-24 18:24:59,941 - INFO - Frame 1414 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 1
2025-11-24 18:25:00,003 - INFO - Video thread started with source: Camera
2025-11-24 18:25:00,004 - ERROR - ❌ No camera found!
2025-11-24 18:25:00,097 - INFO - Video thread started with source: Camera
2025-11-24 18:25:00,099 - ERROR - ❌ No camera found!
2025-11-24 18:25:00,200 - INFO - Video thread started with source: Camera
2025-11-24 18:25:00,200 - ERROR - ❌ No camera found!
2025-11-24 18:25:00,220 - INFO - Frame 1416 | PERCLOS: 0.00 | Yaw: -0.3° | Alerts: 1
2025-11-24 18:25:00,302 - INFO - Video thread started with source: Camera
2025-11-24 18:25:00,303 - ERROR - ❌ No camera found!
2025-11-24 18:25:00,403 - INFO - Video thread started with source: Camera
2025-11-24 18:25:00,404 - ERROR - ❌ No camera found!
2025-11-24 18:25:00,433 - INFO - Frame 1418 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 1
2025-11-24 18:25:00,501 - INFO - Video thread started with source: Camera
2025-11-24 18:25:00,502 - ERROR - ❌ No camera found!
2025-11-24 18:25:00,602 - INFO - Video thread started with source: Camera
2025-11-24 18:25:00,604 - ERROR - ❌ No camera found!
2025-11-24 18:25:00,636 - INFO - Frame 1420 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 1
2025-11-24 18:25:00,709 - INFO - Video thread started with source: Camera
2025-11-24 18:25:00,710 - ERROR - ❌ No camera found!
2025-11-24 18:25:00,806 - INFO - Video thread started with source: Camera
2025-11-24 18:25:00,807 - ERROR - ❌ No camera found!
2025-11-24 18:25:00,898 - INFO - Video thread started with source: Camera
2025-11-24 18:25:00,899 - ERROR - ❌ No camera found!
2025-11-24 18:25:00,920 - INFO - Frame 1422 | PERCLOS: 0.00 | Yaw: -0.3° | Alerts: 1
2025-11-24 18:25:00,988 - INFO - Video thread started with source: Camera
2025-11-24 18:25:00,989 - ERROR - ❌ No camera found!
2025-11-24 18:25:01,080 - INFO - Video thread started with source: Camera
2025-11-24 18:25:01,081 - ERROR - ❌ No camera found!
2025-11-24 18:25:01,111 - INFO - Frame 1424 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 1
2025-11-24 18:25:01,172 - INFO - Video thread started with source: Camera
2025-11-24 18:25:01,173 - ERROR - ❌ No camera found!
2025-11-24 18:25:01,267 - INFO - Video thread started with source: Camera
2025-11-24 18:25:01,268 - ERROR - ❌ No camera found!
2025-11-24 18:25:01,298 - INFO - Frame 1426 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 1
2025-11-24 18:25:01,373 - INFO - Video thread started with source: Camera
2025-11-24 18:25:01,374 - ERROR - ❌ No camera found!
2025-11-24 18:25:01,469 - INFO - Video thread started with source: Camera
2025-11-24 18:25:01,470 - ERROR - ❌ No camera found!
2025-11-24 18:25:01,567 - INFO - Video thread started with source: Camera
2025-11-24 18:25:01,568 - ERROR - ❌ No camera found!
2025-11-24 18:25:01,589 - INFO - Frame 1428 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 1
2025-11-24 18:25:01,662 - INFO - Video thread started with source: Camera
2025-11-24 18:25:01,663 - ERROR - ❌ No camera found!
2025-11-24 18:25:01,756 - INFO - Video thread started with source: Camera
2025-11-24 18:25:01,758 - ERROR - ❌ No camera found!
2025-11-24 18:25:01,789 - INFO - Frame 1430 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 1
2025-11-24 18:25:01,860 - INFO - Video thread started with source: Camera
2025-11-24 18:25:01,861 - ERROR - ❌ No camera found!
2025-11-24 18:25:01,957 - INFO - Video thread started with source: Camera
2025-11-24 18:25:01,958 - ERROR - ❌ No camera found!
2025-11-24 18:25:01,989 - INFO - Frame 1432 | PERCLOS: 0.00 | Yaw: -0.3° | Alerts: 1
2025-11-24 18:25:02,052 - INFO - Video thread started with source: Camera
2025-11-24 18:25:02,053 - ERROR - ❌ No camera found!
2025-11-24 18:25:02,146 - INFO - Video thread started with source: Camera
2025-11-24 18:25:02,147 - ERROR - ❌ No camera found!
2025-11-24 18:25:02,244 - INFO - Video thread started with source: Camera
2025-11-24 18:25:02,245 - ERROR - ❌ No camera found!
2025-11-24 18:25:02,264 - INFO - Frame 1434 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 1
2025-11-24 18:25:02,349 - INFO - Video thread started with source: Camera
2025-11-24 18:25:02,350 - ERROR - ❌ No camera found!
2025-11-24 18:25:02,438 - INFO - Video thread started with source: Camera
2025-11-24 18:25:02,439 - ERROR - ❌ No camera found!
2025-11-24 18:25:02,472 - INFO - Frame 1436 | PERCLOS: 0.00 | Yaw: -0.3° | Alerts: 1
2025-11-24 18:25:02,535 - INFO - Video thread started with source: Camera
2025-11-24 18:25:02,536 - ERROR - ❌ No camera found!
2025-11-24 18:25:02,622 - INFO - Video thread started with source: Camera
2025-11-24 18:25:02,624 - ERROR - ❌ No camera found!
2025-11-24 18:25:02,652 - INFO - Frame 1438 | PERCLOS: 0.00 | Yaw: -0.3° | Alerts: 1
2025-11-24 18:25:02,715 - INFO - Video thread started with source: Camera
2025-11-24 18:25:02,716 - ERROR - ❌ No camera found!
2025-11-24 18:25:02,812 - INFO - Video thread started with source: Camera
2025-11-24 18:25:02,813 - ERROR - ❌ No camera found!
2025-11-24 18:25:02,916 - INFO - Video thread started with source: Camera
2025-11-24 18:25:02,918 - ERROR - ❌ No camera found!
2025-11-24 18:25:02,938 - INFO - Frame 1440 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 1
2025-11-24 18:25:03,012 - INFO - Video thread started with source: Camera
2025-11-24 18:25:03,013 - ERROR - ❌ No camera found!
2025-11-24 18:25:03,103 - INFO - Video thread started with source: Camera
2025-11-24 18:25:03,104 - ERROR - ❌ No camera found!
2025-11-24 18:25:03,133 - INFO - Frame 1442 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 1
2025-11-24 18:25:03,194 - INFO - Video thread started with source: Camera
2025-11-24 18:25:03,195 - ERROR - ❌ No camera found!
2025-11-24 18:25:03,285 - INFO - Video thread started with source: Camera
2025-11-24 18:25:03,286 - ERROR - ❌ No camera found!
2025-11-24 18:25:03,317 - INFO - Frame 1444 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 1
2025-11-24 18:25:03,385 - INFO - Video thread started with source: Camera
2025-11-24 18:25:03,386 - ERROR - ❌ No camera found!
2025-11-24 18:25:03,484 - INFO - Video thread started with source: Camera
2025-11-24 18:25:03,485 - ERROR - ❌ No camera found!
2025-11-24 18:25:03,579 - INFO - Video thread started with source: Camera
2025-11-24 18:25:03,580 - ERROR - ❌ No camera found!
2025-11-24 18:25:03,601 - INFO - Frame 1446 | PERCLOS: 0.00 | Yaw: -0.3° | Alerts: 1
2025-11-24 18:25:03,682 - INFO - Video thread started with source: Camera
2025-11-24 18:25:03,684 - ERROR - ❌ No camera found!
2025-11-24 18:25:03,778 - INFO - Video thread started with source: Camera
2025-11-24 18:25:03,779 - ERROR - ❌ No camera found!
2025-11-24 18:25:03,811 - INFO - Frame 1448 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 1
2025-11-24 18:25:03,877 - INFO - Video thread started with source: Camera
2025-11-24 18:25:03,878 - ERROR - ❌ No camera found!
2025-11-24 18:25:03,976 - INFO - Video thread started with source: Camera
2025-11-24 18:25:03,977 - ERROR - ❌ No camera found!
2025-11-24 18:25:04,008 - INFO - Frame 1450 | PERCLOS: 0.00 | Yaw: -0.2° | Alerts: 1
2025-11-24 18:25:04,077 - INFO - Video thread started with source: Camera
2025-11-24 18:25:04,078 - ERROR - ❌ No camera found!
2025-11-24 18:25:04,173 - INFO - Video thread started with source: Camera
2025-11-24 18:25:04,174 - ERROR - ❌ No camera found!
2025-11-24 18:25:04,272 - INFO - Video thread started with source: Camera
2025-11-24 18:25:04,273 - ERROR - ❌ No camera found!
2025-11-24 18:25:04,294 - INFO - Frame 1452 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 1
2025-11-24 18:25:04,365 - INFO - Video thread started with source: Camera
2025-11-24 18:25:04,366 - ERROR - ❌ No camera found!
2025-11-24 18:25:04,459 - INFO - Video thread started with source: Camera
2025-11-24 18:25:04,460 - ERROR - ❌ No camera found!
2025-11-24 18:25:04,493 - INFO - Frame 1454 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 18:25:04,556 - INFO - Video thread started with source: Camera
2025-11-24 18:25:04,557 - ERROR - ❌ No camera found!
2025-11-24 18:25:04,651 - INFO - Video thread started with source: Camera
2025-11-24 18:25:04,653 - ERROR - ❌ No camera found!
2025-11-24 18:25:04,684 - INFO - Frame 1456 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 1
2025-11-24 18:25:04,756 - INFO - Video thread started with source: Camera
2025-11-24 18:25:04,757 - ERROR - ❌ No camera found!
2025-11-24 18:25:04,885 - INFO - Video thread started with source: Camera
2025-11-24 18:25:04,886 - ERROR - ❌ No camera found!
2025-11-24 18:25:04,999 - INFO - Video file uploaded: assets/temp_videos/Screen Recording 2025-11-24 at 6.07.31 PM.mov
2025-11-24 18:25:04,999 - INFO - Video thread started with source: assets/temp_videos/Screen Recording 2025-11-24 at 6.07.31 PM.mov
2025-11-24 18:25:05,016 - INFO - Frame 1458 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 18:25:05,028 - INFO - ✓ Video file opened: assets/temp_videos/Screen Recording 2025-11-24 at 6.07.31 PM.mov
2025-11-24 18:25:05,278 - INFO - Frame 0 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:05,280 - INFO - Frame 1460 | PERCLOS: 0.53 | Yaw: 3.7° | Alerts: 2
2025-11-24 18:25:05,444 - INFO - Frame 1462 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 18:25:05,466 - INFO - Frame 2 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:05,642 - INFO - Frame 4 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:05,693 - INFO - Frame 1464 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 1
2025-11-24 18:25:05,733 - INFO - Frame 6 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:05,877 - INFO - Frame 1466 | PERCLOS: 0.06 | Yaw: 3.9° | Alerts: 1
2025-11-24 18:25:05,898 - INFO - Frame 8 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:06,055 - INFO - Frame 1468 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 18:25:06,057 - INFO - Frame 10 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:06,183 - INFO - Frame 12 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:06,291 - INFO - Frame 1470 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 18:25:06,363 - INFO - Frame 14 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:06,403 - INFO - Frame 1472 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 18:25:06,461 - INFO - Frame 16 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:06,623 - INFO - Frame 1474 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 1
2025-11-24 18:25:06,631 - INFO - Frame 18 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:06,726 - INFO - Frame 20 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:06,857 - INFO - Frame 1476 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:25:06,912 - INFO - Frame 22 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:07,021 - INFO - Frame 1478 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 1
2025-11-24 18:25:07,080 - INFO - Frame 24 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:07,159 - INFO - Frame 1480 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 1
2025-11-24 18:25:07,183 - INFO - Frame 26 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:07,351 - INFO - Frame 28 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:07,411 - INFO - Frame 1482 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 1
2025-11-24 18:25:07,501 - INFO - Frame 30 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:07,599 - INFO - Frame 1484 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:25:07,613 - INFO - Frame 32 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:07,765 - INFO - Frame 34 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:07,774 - INFO - Frame 1486 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 18:25:07,867 - INFO - Frame 36 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:07,990 - INFO - Frame 1488 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 18:25:08,044 - INFO - Frame 38 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:08,120 - INFO - Frame 1490 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-24 18:25:08,142 - INFO - Frame 40 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:08,334 - INFO - Frame 1492 | PERCLOS: 0.00 | Yaw: 6.9° | Alerts: 1
2025-11-24 18:25:08,461 - INFO - Frame 42 | PERCLOS: 0.00 | Yaw: 6.9° | Alerts: 1
2025-11-24 18:25:08,575 - INFO - Frame 1494 | PERCLOS: 0.45 | Yaw: 9.5° | Alerts: 2
2025-11-24 18:25:08,579 - INFO - Frame 44 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:08,731 - INFO - Frame 1496 | PERCLOS: 0.00 | Yaw: 11.2° | Alerts: 1
2025-11-24 18:25:08,732 - INFO - Frame 46 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:08,848 - INFO - Frame 1498 | PERCLOS: 0.00 | Yaw: 11.4° | Alerts: 1
2025-11-24 18:25:08,850 - INFO - Frame 48 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:09,044 - INFO - Frame 50 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:09,086 - INFO - Frame 1500 | PERCLOS: 0.00 | Yaw: 11.8° | Alerts: 1
2025-11-24 18:25:09,137 - INFO - Frame 52 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:09,283 - INFO - Frame 1502 | PERCLOS: 0.00 | Yaw: 12.4° | Alerts: 1
2025-11-24 18:25:09,291 - INFO - Frame 54 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:09,377 - INFO - Frame 56 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:09,457 - INFO - Frame 1504 | PERCLOS: 0.00 | Yaw: 13.5° | Alerts: 1
2025-11-24 18:25:09,529 - INFO - Frame 58 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:09,617 - INFO - Frame 60 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:09,693 - INFO - Frame 1506 | PERCLOS: 0.00 | Yaw: 12.7° | Alerts: 1
2025-11-24 18:25:09,775 - INFO - Frame 62 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:09,836 - INFO - Frame 1508 | PERCLOS: 0.00 | Yaw: 11.9° | Alerts: 1
2025-11-24 18:25:09,934 - INFO - Frame 64 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:10,031 - INFO - Frame 1510 | PERCLOS: 0.00 | Yaw: 12.6° | Alerts: 1
2025-11-24 18:25:10,055 - INFO - Frame 66 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:10,206 - INFO - Frame 68 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:10,276 - INFO - Frame 1512 | PERCLOS: 0.00 | Yaw: 12.3° | Alerts: 1
2025-11-24 18:25:10,315 - INFO - Frame 70 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:10,440 - INFO - Frame 1514 | PERCLOS: 0.00 | Yaw: 12.1° | Alerts: 1
2025-11-24 18:25:10,503 - INFO - Frame 72 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:10,580 - INFO - Frame 1516 | PERCLOS: 0.00 | Yaw: 12.2° | Alerts: 1
2025-11-24 18:25:10,605 - INFO - Frame 74 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:10,755 - INFO - Frame 76 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:10,898 - INFO - Frame 1518 | PERCLOS: 0.00 | Yaw: 12.5° | Alerts: 1
2025-11-24 18:25:10,901 - INFO - Frame 78 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:11,021 - INFO - Frame 80 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:11,046 - INFO - Frame 1520 | PERCLOS: 0.20 | Yaw: 12.1° | Alerts: 1
2025-11-24 18:25:11,238 - INFO - Frame 1522 | PERCLOS: 0.00 | Yaw: 11.5° | Alerts: 1
2025-11-24 18:25:11,240 - INFO - Frame 82 | PERCLOS: 0.00 | Yaw: 11.5° | Alerts: 0
2025-11-24 18:25:11,388 - INFO - Frame 84 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:11,468 - INFO - Frame 1524 | PERCLOS: 0.00 | Yaw: 11.5° | Alerts: 1
2025-11-24 18:25:11,499 - INFO - Frame 86 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:11,626 - INFO - Frame 1526 | PERCLOS: 0.00 | Yaw: 11.6° | Alerts: 1
2025-11-24 18:25:11,650 - INFO - Frame 88 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:11,737 - INFO - Frame 1528 | PERCLOS: 0.00 | Yaw: 10.6° | Alerts: 1
2025-11-24 18:25:11,760 - INFO - Frame 90 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:11,901 - INFO - Frame 92 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:11,992 - INFO - Frame 1530 | PERCLOS: 0.00 | Yaw: 9.2° | Alerts: 1
2025-11-24 18:25:12,009 - INFO - Frame 94 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:12,139 - INFO - Frame 96 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:12,181 - INFO - Frame 1532 | PERCLOS: 0.03 | Yaw: 6.7° | Alerts: 1
2025-11-24 18:25:12,244 - INFO - Frame 98 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:12,361 - INFO - Frame 1534 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-24 18:25:12,422 - INFO - Frame 100 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:12,526 - INFO - Frame 102 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:12,619 - INFO - Frame 1536 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 1
2025-11-24 18:25:12,714 - INFO - Frame 104 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:12,738 - INFO - Frame 1538 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 1
2025-11-24 18:25:12,856 - INFO - Frame 106 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:12,932 - INFO - Frame 1540 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 1
2025-11-24 18:25:12,963 - INFO - Frame 108 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:13,113 - INFO - Frame 110 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:13,179 - INFO - Frame 1542 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 1
2025-11-24 18:25:13,217 - INFO - Frame 112 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:13,341 - INFO - Frame 1544 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 1
2025-11-24 18:25:13,403 - INFO - Frame 114 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:13,479 - INFO - Frame 1546 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 1
2025-11-24 18:25:13,504 - INFO - Frame 116 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:13,672 - INFO - Frame 118 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:13,735 - INFO - Frame 1548 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 1
2025-11-24 18:25:13,830 - INFO - Frame 120 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:13,947 - INFO - Frame 1550 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 1
2025-11-24 18:25:13,953 - INFO - Frame 122 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:14,105 - INFO - Frame 124 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:14,115 - INFO - Frame 1552 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 1
2025-11-24 18:25:14,260 - INFO - Frame 126 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:14,363 - INFO - Frame 1554 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 1
2025-11-24 18:25:14,422 - INFO - Frame 128 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:14,478 - INFO - Frame 1556 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 1
2025-11-24 18:25:14,580 - INFO - Frame 130 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:14,656 - INFO - Frame 1558 | PERCLOS: 0.00 | Yaw: -1.1° | Alerts: 1
2025-11-24 18:25:14,710 - INFO - Frame 132 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:14,850 - INFO - Frame 134 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:14,893 - INFO - Frame 1560 | PERCLOS: 0.00 | Yaw: -1.3° | Alerts: 1
2025-11-24 18:25:14,950 - INFO - Frame 136 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:15,063 - INFO - Frame 1562 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 1
2025-11-24 18:25:15,086 - INFO - Frame 138 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:15,191 - INFO - Frame 140 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:15,199 - INFO - Frame 1564 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 1
2025-11-24 18:25:15,360 - INFO - Frame 142 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:15,443 - INFO - Frame 1566 | PERCLOS: 0.14 | Yaw: -0.2° | Alerts: 1
2025-11-24 18:25:15,518 - INFO - Frame 144 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:15,615 - INFO - Frame 1568 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 1
2025-11-24 18:25:15,640 - INFO - Frame 146 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:15,825 - INFO - Frame 1570 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 1
2025-11-24 18:25:15,828 - INFO - Frame 148 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:15,988 - INFO - Frame 150 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:16,051 - INFO - Frame 1572 | PERCLOS: 0.47 | Yaw: -0.3° | Alerts: 2
2025-11-24 18:25:16,110 - INFO - Frame 152 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:16,218 - INFO - Frame 1574 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 1
2025-11-24 18:25:16,295 - INFO - Frame 154 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:16,368 - INFO - Frame 1576 | PERCLOS: 0.00 | Yaw: -0.3° | Alerts: 1
2025-11-24 18:25:16,450 - INFO - Frame 156 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:16,568 - INFO - Frame 158 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:16,612 - INFO - Frame 1578 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 1
2025-11-24 18:25:16,709 - INFO - Frame 160 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:16,786 - INFO - Frame 1580 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-24 18:25:16,816 - INFO - Frame 162 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:16,937 - INFO - Frame 1582 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 18:25:16,962 - INFO - Frame 164 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:17,070 - INFO - Frame 166 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:17,103 - INFO - Frame 1584 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 18:25:17,239 - INFO - Frame 168 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:17,279 - INFO - Frame 1586 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 18:25:17,342 - INFO - Frame 170 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:17,494 - INFO - Frame 1588 | PERCLOS: 0.66 | Yaw: 1.9° | Alerts: 2
2025-11-24 18:25:17,513 - INFO - Frame 172 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:17,667 - INFO - Frame 174 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:17,693 - INFO - Frame 1590 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 1
2025-11-24 18:25:17,784 - INFO - Frame 1592 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:17,786 - INFO - Frame 176 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:17,926 - INFO - Frame 178 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:17,934 - INFO - Frame 1594 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 0
2025-11-24 18:25:18,037 - INFO - Frame 180 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:18,148 - INFO - Frame 1596 | PERCLOS: 0.75 | Yaw: 3.5° | Alerts: 2
2025-11-24 18:25:18,177 - INFO - Frame 182 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:18,263 - INFO - Frame 1598 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 1
2025-11-24 18:25:18,284 - INFO - Frame 184 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:18,455 - INFO - Frame 186 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:18,455 - INFO - Frame 1600 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 18:25:18,554 - INFO - Frame 188 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:18,692 - INFO - Frame 1602 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 1
2025-11-24 18:25:18,712 - INFO - Frame 190 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:18,810 - INFO - Frame 1604 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 1
2025-11-24 18:25:18,880 - INFO - Frame 192 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:18,984 - INFO - Frame 1606 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:25:19,000 - INFO - Frame 194 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:19,151 - INFO - Frame 196 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:19,253 - INFO - Frame 1608 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:25:19,257 - INFO - Frame 198 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:19,400 - INFO - Frame 200 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:19,446 - INFO - Frame 1610 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 18:25:19,506 - INFO - Frame 202 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:19,620 - INFO - Frame 1612 | PERCLOS: 0.43 | Yaw: 3.5° | Alerts: 2
2025-11-24 18:25:19,691 - INFO - Frame 204 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:19,785 - INFO - Frame 206 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:19,858 - INFO - Frame 1614 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-24 18:25:19,957 - INFO - Frame 208 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:20,009 - INFO - Frame 1616 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 18:25:20,125 - INFO - Frame 210 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:20,228 - INFO - Frame 1618 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 18:25:20,257 - INFO - Frame 212 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:20,492 - INFO - Frame 214 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:20,541 - INFO - Frame 1620 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:25:20,595 - INFO - Frame 216 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:20,748 - INFO - Frame 1622 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 18:25:20,769 - INFO - Frame 218 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:20,921 - INFO - Frame 220 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:20,921 - INFO - Frame 1624 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-24 18:25:21,032 - INFO - Frame 222 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:21,160 - INFO - Frame 1626 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 1
2025-11-24 18:25:21,218 - INFO - Frame 224 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:21,289 - INFO - Frame 1628 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 1
2025-11-24 18:25:21,375 - INFO - Frame 226 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:21,475 - INFO - Frame 1630 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 18:25:21,496 - INFO - Frame 228 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:21,639 - INFO - Frame 230 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:21,743 - INFO - Frame 1632 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 1
2025-11-24 18:25:21,752 - INFO - Frame 232 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:21,929 - INFO - Frame 1634 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 1
2025-11-24 18:25:21,936 - INFO - Frame 234 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:22,103 - INFO - Frame 236 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:22,104 - INFO - Frame 1636 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 1
2025-11-24 18:25:22,219 - INFO - Frame 238 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:22,372 - INFO - Frame 1638 | PERCLOS: 0.55 | Yaw: 2.7° | Alerts: 2
2025-11-24 18:25:22,373 - INFO - Frame 240 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:22,481 - INFO - Frame 242 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:22,497 - INFO - Frame 1640 | PERCLOS: 0.14 | Yaw: 3.0° | Alerts: 1
2025-11-24 18:25:22,623 - INFO - Frame 244 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:22,699 - INFO - Frame 1642 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:25:22,733 - INFO - Frame 246 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:22,878 - INFO - Frame 248 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:22,924 - INFO - Frame 1644 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 18:25:22,981 - INFO - Frame 250 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:23,096 - INFO - Frame 1646 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:25:23,156 - INFO - Frame 252 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:23,233 - INFO - Frame 1648 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-24 18:25:23,251 - INFO - Frame 254 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:23,424 - INFO - Frame 256 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:23,485 - INFO - Frame 1650 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 18:25:23,516 - INFO - Frame 258 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:23,681 - INFO - Frame 1652 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:25:23,684 - INFO - Frame 260 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:23,825 - INFO - Frame 1654 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:23,829 - INFO - Frame 262 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:23,924 - INFO - Frame 1656 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:23,926 - INFO - Frame 264 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:24,076 - INFO - Frame 1658 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 0
2025-11-24 18:25:24,080 - INFO - Frame 266 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:24,187 - INFO - Frame 268 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:24,192 - INFO - Frame 1660 | PERCLOS: 0.53 | Yaw: 2.9° | Alerts: 1
2025-11-24 18:25:24,339 - INFO - Frame 1662 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:24,342 - INFO - Frame 270 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:24,422 - INFO - Frame 1664 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:24,425 - INFO - Frame 272 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:24,579 - INFO - Frame 1666 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 0
2025-11-24 18:25:24,584 - INFO - Frame 274 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:24,742 - INFO - Frame 276 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:24,841 - INFO - Frame 1668 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 1
2025-11-24 18:25:24,845 - INFO - Frame 278 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:25,001 - INFO - Frame 280 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:25,007 - INFO - Frame 1670 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 18:25:25,117 - INFO - Frame 282 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:25,123 - INFO - Frame 1672 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 1
2025-11-24 18:25:25,319 - INFO - Frame 284 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:25,340 - INFO - Frame 1674 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 18:25:25,496 - INFO - Frame 1676 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 1
2025-11-24 18:25:25,524 - INFO - Frame 286 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 0
2025-11-24 18:25:25,632 - INFO - Frame 1678 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 18:25:25,635 - INFO - Frame 288 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:25,777 - INFO - Frame 290 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:25,848 - INFO - Frame 1680 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 1
2025-11-24 18:25:25,883 - INFO - Frame 292 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:26,002 - INFO - Frame 1682 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 2
2025-11-24 18:25:26,027 - INFO - Frame 294 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:26,116 - INFO - Frame 1684 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:25:26,140 - INFO - Frame 296 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:26,326 - INFO - Frame 298 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:26,377 - INFO - Frame 1686 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 18:25:26,423 - INFO - Frame 300 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:26,581 - INFO - Frame 1688 | PERCLOS: 0.68 | Yaw: 3.8° | Alerts: 2
2025-11-24 18:25:26,603 - INFO - Frame 302 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:26,701 - INFO - Frame 1690 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 1
2025-11-24 18:25:26,768 - INFO - Frame 304 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:26,904 - INFO - Frame 306 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:26,925 - INFO - Frame 1692 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 1
2025-11-24 18:25:27,081 - INFO - Frame 308 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:27,118 - INFO - Frame 1694 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:25:27,179 - INFO - Frame 310 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:27,324 - INFO - Frame 1696 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 18:25:27,345 - INFO - Frame 312 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:27,505 - INFO - Frame 314 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:27,527 - INFO - Frame 1698 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 2
2025-11-24 18:25:27,624 - INFO - Frame 316 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:27,651 - INFO - Frame 1700 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 18:25:27,761 - INFO - Frame 318 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:27,840 - INFO - Frame 1702 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-24 18:25:27,867 - INFO - Frame 320 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:28,001 - INFO - Frame 322 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:28,072 - INFO - Frame 1704 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:25:28,108 - INFO - Frame 324 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:28,227 - INFO - Frame 1706 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 18:25:28,249 - INFO - Frame 326 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:28,358 - INFO - Frame 328 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:28,372 - INFO - Frame 1708 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:25:28,531 - INFO - Frame 330 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:28,630 - INFO - Frame 1710 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 1
2025-11-24 18:25:28,636 - INFO - Frame 332 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:28,797 - INFO - Frame 334 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:28,823 - INFO - Frame 1712 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 18:25:28,891 - INFO - Frame 336 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:29,001 - INFO - Frame 1714 | PERCLOS: 0.35 | Yaw: 2.8° | Alerts: 2
2025-11-24 18:25:29,049 - INFO - Frame 338 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:29,137 - INFO - Frame 340 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:29,214 - INFO - Frame 1716 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-24 18:25:29,288 - INFO - Frame 342 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:29,364 - INFO - Frame 1718 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 1
2025-11-24 18:25:29,373 - INFO - Frame 344 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:29,585 - INFO - Frame 1720 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 1
2025-11-24 18:25:29,588 - INFO - Frame 346 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 0
2025-11-24 18:25:29,745 - INFO - Frame 348 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:29,817 - INFO - Frame 1722 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 1
2025-11-24 18:25:29,852 - INFO - Frame 350 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:29,982 - INFO - Frame 352 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:29,988 - INFO - Frame 1724 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-24 18:25:30,097 - INFO - Frame 354 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:30,112 - INFO - Frame 1726 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-24 18:25:30,247 - INFO - Frame 356 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:30,369 - INFO - Frame 358 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:30,391 - INFO - Frame 1728 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 1
2025-11-24 18:25:30,546 - INFO - Frame 360 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:30,573 - INFO - Frame 1730 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:25:30,645 - INFO - Frame 362 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:30,729 - INFO - Frame 1732 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 18:25:30,803 - INFO - Frame 364 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:30,961 - INFO - Frame 366 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:30,987 - INFO - Frame 1734 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-24 18:25:31,075 - INFO - Frame 1736 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:31,077 - INFO - Frame 368 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:31,226 - INFO - Frame 370 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:31,233 - INFO - Frame 1738 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 0
2025-11-24 18:25:31,341 - INFO - Frame 372 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:31,440 - INFO - Frame 1740 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 18:25:31,510 - INFO - Frame 374 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:31,582 - INFO - Frame 1742 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 1
2025-11-24 18:25:31,597 - INFO - Frame 376 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:31,740 - INFO - Frame 1744 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:31,742 - INFO - Frame 378 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:31,889 - INFO - Frame 380 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:31,984 - INFO - Frame 1746 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 1
2025-11-24 18:25:32,020 - INFO - Frame 382 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:32,136 - INFO - Frame 1748 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 1
2025-11-24 18:25:32,165 - INFO - Frame 384 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:32,252 - INFO - Frame 1750 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 1
2025-11-24 18:25:32,275 - INFO - Frame 386 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:32,422 - INFO - Frame 388 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:32,491 - INFO - Frame 1752 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 18:25:32,530 - INFO - Frame 390 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:32,651 - INFO - Frame 1754 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-24 18:25:32,682 - INFO - Frame 392 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:32,761 - INFO - Frame 1756 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 1
2025-11-24 18:25:32,796 - INFO - Frame 394 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:32,956 - INFO - Frame 396 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:32,997 - INFO - Frame 1758 | PERCLOS: 0.00 | Yaw: 5.8° | Alerts: 1
2025-11-24 18:25:33,062 - INFO - Frame 398 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:33,190 - INFO - Frame 1760 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 1
2025-11-24 18:25:33,223 - INFO - Frame 400 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:33,309 - INFO - Frame 1762 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-24 18:25:33,337 - INFO - Frame 402 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:33,481 - INFO - Frame 404 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:33,550 - INFO - Frame 1764 | PERCLOS: 0.00 | Yaw: 6.2° | Alerts: 1
2025-11-24 18:25:33,591 - INFO - Frame 406 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:33,785 - INFO - Frame 1766 | PERCLOS: 0.00 | Yaw: 6.8° | Alerts: 1
2025-11-24 18:25:33,801 - INFO - Frame 408 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:33,891 - INFO - Frame 410 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:33,894 - INFO - Frame 1768 | PERCLOS: 0.46 | Yaw: 7.6° | Alerts: 2
2025-11-24 18:25:34,028 - INFO - Frame 412 | PERCLOS: 0.00 | Yaw: 7.0° | Alerts: 0
2025-11-24 18:25:34,080 - INFO - Frame 1770 | PERCLOS: 0.00 | Yaw: 7.0° | Alerts: 1
2025-11-24 18:25:34,111 - INFO - Frame 414 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:34,134 - INFO - Video thread started with source: Camera
2025-11-24 18:25:34,137 - ERROR - ❌ No camera found!
2025-11-24 18:25:34,246 - INFO - Video thread started with source: Camera
2025-11-24 18:25:34,248 - ERROR - ❌ No camera found!
2025-11-24 18:25:34,249 - INFO - Frame 1772 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 1
2025-11-24 18:25:34,266 - INFO - Frame 416 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:34,352 - INFO - Video thread started with source: Camera
2025-11-24 18:25:34,353 - ERROR - ❌ No camera found!
2025-11-24 18:25:34,446 - INFO - Video thread started with source: Camera
2025-11-24 18:25:34,448 - ERROR - ❌ No camera found!
2025-11-24 18:25:34,463 - INFO - Frame 418 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:34,483 - INFO - Frame 1774 | PERCLOS: 0.67 | Yaw: 5.7° | Alerts: 2
2025-11-24 18:25:34,547 - INFO - Video thread started with source: Camera
2025-11-24 18:25:34,549 - ERROR - ❌ No camera found!
2025-11-24 18:25:34,643 - INFO - Frame 1776 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:34,646 - INFO - Video thread started with source: Camera
2025-11-24 18:25:34,648 - ERROR - ❌ No camera found!
2025-11-24 18:25:34,651 - INFO - Frame 420 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:25:34,677 - INFO - End of video file reached
2025-11-24 18:25:34,680 - INFO - Video capture loop ended
2025-11-24 18:25:34,745 - INFO - Video thread started with source: Camera
2025-11-24 18:25:34,746 - ERROR - ❌ No camera found!
2025-11-24 18:25:34,852 - INFO - Video thread started with source: Camera
2025-11-24 18:25:34,853 - ERROR - ❌ No camera found!
2025-11-24 18:25:34,854 - INFO - Frame 1778 | PERCLOS: 0.35 | Yaw: 2.8° | Alerts: 1
2025-11-24 18:25:34,952 - INFO - Video thread started with source: Camera
2025-11-24 18:25:34,953 - ERROR - ❌ No camera found!
2025-11-24 18:25:34,989 - INFO - Frame 1780 | PERCLOS: 0.07 | Yaw: 3.4° | Alerts: 0
2025-11-24 18:25:35,053 - INFO - Video thread started with source: Camera
2025-11-24 18:25:35,054 - ERROR - ❌ No camera found!
2025-11-24 18:25:35,142 - INFO - Video thread started with source: Camera
2025-11-24 18:25:35,144 - ERROR - ❌ No camera found!
2025-11-24 18:25:35,243 - INFO - Video thread started with source: Camera
2025-11-24 18:25:35,244 - ERROR - ❌ No camera found!
2025-11-24 18:25:35,262 - INFO - Frame 1782 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 18:25:35,336 - INFO - Video thread started with source: Camera
2025-11-24 18:25:35,337 - ERROR - ❌ No camera found!
2025-11-24 18:25:35,426 - INFO - Video thread started with source: Camera
2025-11-24 18:25:35,428 - ERROR - ❌ No camera found!
2025-11-24 18:25:35,459 - INFO - Frame 1784 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 18:25:35,522 - INFO - Video thread started with source: Camera
2025-11-24 18:25:35,523 - ERROR - ❌ No camera found!
2025-11-24 18:25:35,617 - INFO - Video thread started with source: Camera
2025-11-24 18:25:35,618 - ERROR - ❌ No camera found!
2025-11-24 18:25:35,650 - INFO - Frame 1786 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:25:35,715 - INFO - Video thread started with source: Camera
2025-11-24 18:25:35,716 - ERROR - ❌ No camera found!
2025-11-24 18:25:35,810 - INFO - Video thread started with source: Camera
2025-11-24 18:25:35,811 - ERROR - ❌ No camera found!
2025-11-24 18:25:35,908 - INFO - Video thread started with source: Camera
2025-11-24 18:25:35,909 - ERROR - ❌ No camera found!
2025-11-24 18:25:35,929 - INFO - Frame 1788 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 18:25:36,010 - INFO - Video thread started with source: Camera
2025-11-24 18:25:36,011 - ERROR - ❌ No camera found!
2025-11-24 18:25:36,100 - INFO - Video thread started with source: Camera
2025-11-24 18:25:36,101 - ERROR - ❌ No camera found!
2025-11-24 18:25:36,130 - INFO - Frame 1790 | PERCLOS: 0.00 | Yaw: 4.1° | Alerts: 1
2025-11-24 18:25:36,199 - INFO - Video thread started with source: Camera
2025-11-24 18:25:36,199 - ERROR - ❌ No camera found!
2025-11-24 18:25:36,288 - INFO - Video thread started with source: Camera
2025-11-24 18:25:36,289 - ERROR - ❌ No camera found!
2025-11-24 18:25:36,321 - INFO - Frame 1792 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-24 18:25:36,385 - INFO - Video thread started with source: Camera
2025-11-24 18:25:36,386 - ERROR - ❌ No camera found!
2025-11-24 18:25:36,481 - INFO - Video thread started with source: Camera
2025-11-24 18:25:36,482 - ERROR - ❌ No camera found!
2025-11-24 18:25:36,580 - INFO - Video thread started with source: Camera
2025-11-24 18:25:36,581 - ERROR - ❌ No camera found!
2025-11-24 18:25:36,600 - INFO - Frame 1794 | PERCLOS: 0.14 | Yaw: 5.9° | Alerts: 1
2025-11-24 18:25:36,670 - INFO - Video thread started with source: Camera
2025-11-24 18:25:36,672 - ERROR - ❌ No camera found!
2025-11-24 18:25:36,759 - INFO - Video thread started with source: Camera
2025-11-24 18:25:36,760 - ERROR - ❌ No camera found!
2025-11-24 18:25:36,791 - INFO - Frame 1796 | PERCLOS: 0.39 | Yaw: 5.9° | Alerts: 2
2025-11-24 18:25:36,852 - INFO - Video thread started with source: Camera
2025-11-24 18:25:36,853 - ERROR - ❌ No camera found!
2025-11-24 18:25:36,947 - INFO - Video thread started with source: Camera
2025-11-24 18:25:36,948 - ERROR - ❌ No camera found!
2025-11-24 18:25:36,978 - INFO - Frame 1798 | PERCLOS: 0.00 | Yaw: 5.4° | Alerts: 1
2025-11-24 18:25:37,046 - INFO - Video thread started with source: Camera
2025-11-24 18:25:37,047 - ERROR - ❌ No camera found!
2025-11-24 18:25:37,141 - INFO - Video thread started with source: Camera
2025-11-24 18:25:37,142 - ERROR - ❌ No camera found!
2025-11-24 18:25:37,238 - INFO - Video thread started with source: Camera
2025-11-24 18:25:37,239 - ERROR - ❌ No camera found!
2025-11-24 18:25:37,260 - INFO - Frame 1800 | PERCLOS: 0.00 | Yaw: 4.8° | Alerts: 1
2025-11-24 18:25:37,337 - INFO - Video thread started with source: Camera
2025-11-24 18:25:37,337 - ERROR - ❌ No camera found!
2025-11-24 18:25:37,437 - INFO - Video thread started with source: Camera
2025-11-24 18:25:37,439 - ERROR - ❌ No camera found!
2025-11-24 18:25:37,469 - INFO - Frame 1802 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-24 18:25:37,529 - INFO - Video thread started with source: Camera
2025-11-24 18:25:37,530 - ERROR - ❌ No camera found!
2025-11-24 18:25:37,622 - INFO - Video thread started with source: Camera
2025-11-24 18:25:37,623 - ERROR - ❌ No camera found!
2025-11-24 18:25:37,653 - INFO - Frame 1804 | PERCLOS: 0.48 | Yaw: 4.5° | Alerts: 2
2025-11-24 18:25:37,729 - INFO - Video thread started with source: Camera
2025-11-24 18:25:37,730 - ERROR - ❌ No camera found!
2025-11-24 18:25:37,826 - INFO - Video thread started with source: Camera
2025-11-24 18:25:37,828 - ERROR - ❌ No camera found!
2025-11-24 18:25:37,929 - INFO - Video thread started with source: Camera
2025-11-24 18:25:37,930 - ERROR - ❌ No camera found!
2025-11-24 18:25:37,950 - INFO - Frame 1806 | PERCLOS: 0.06 | Yaw: 4.8° | Alerts: 1
2025-11-24 18:25:38,021 - INFO - Video thread started with source: Camera
2025-11-24 18:25:38,022 - ERROR - ❌ No camera found!
2025-11-24 18:25:38,119 - INFO - Video thread started with source: Camera
2025-11-24 18:25:38,120 - ERROR - ❌ No camera found!
2025-11-24 18:25:38,150 - INFO - Frame 1808 | PERCLOS: 0.00 | Yaw: 5.2° | Alerts: 1
2025-11-24 18:25:38,221 - INFO - Video thread started with source: Camera
2025-11-24 18:25:38,222 - ERROR - ❌ No camera found!
2025-11-24 18:25:38,321 - INFO - Video thread started with source: Camera
2025-11-24 18:25:38,322 - ERROR - ❌ No camera found!
2025-11-24 18:25:38,353 - INFO - Frame 1810 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-24 18:25:38,427 - INFO - Video thread started with source: Camera
2025-11-24 18:25:38,428 - ERROR - ❌ No camera found!
2025-11-24 18:25:38,524 - INFO - Video thread started with source: Camera
2025-11-24 18:25:38,525 - ERROR - ❌ No camera found!
2025-11-24 18:25:38,626 - INFO - Video thread started with source: Camera
2025-11-24 18:25:38,627 - ERROR - ❌ No camera found!
2025-11-24 18:25:38,647 - INFO - Frame 1812 | PERCLOS: 0.13 | Yaw: 5.3° | Alerts: 1
2025-11-24 18:25:38,723 - INFO - Video thread started with source: Camera
2025-11-24 18:25:38,724 - ERROR - ❌ No camera found!
2025-11-24 18:25:38,818 - INFO - Video thread started with source: Camera
2025-11-24 18:25:38,819 - ERROR - ❌ No camera found!
2025-11-24 18:25:38,849 - INFO - Frame 1814 | PERCLOS: 0.05 | Yaw: 5.4° | Alerts: 1
2025-11-24 18:25:38,918 - INFO - Video thread started with source: Camera
2025-11-24 18:25:38,919 - ERROR - ❌ No camera found!
2025-11-24 18:25:39,007 - INFO - Video thread started with source: Camera
2025-11-24 18:25:39,008 - ERROR - ❌ No camera found!
2025-11-24 18:25:39,036 - INFO - Frame 1816 | PERCLOS: 0.00 | Yaw: 5.2° | Alerts: 1
2025-11-24 18:25:39,104 - INFO - Video thread started with source: Camera
2025-11-24 18:25:39,105 - ERROR - ❌ No camera found!
2025-11-24 18:25:39,198 - INFO - Video thread started with source: Camera
2025-11-24 18:25:39,200 - ERROR - ❌ No camera found!
2025-11-24 18:25:39,304 - INFO - Video thread started with source: Camera
2025-11-24 18:25:39,304 - ERROR - ❌ No camera found!
2025-11-24 18:25:39,325 - INFO - Frame 1818 | PERCLOS: 0.05 | Yaw: 7.4° | Alerts: 1
2025-11-24 18:25:39,397 - INFO - Video thread started with source: Camera
2025-11-24 18:25:39,398 - ERROR - ❌ No camera found!
2025-11-24 18:25:39,495 - INFO - Video thread started with source: Camera
2025-11-24 18:25:39,496 - ERROR - ❌ No camera found!
2025-11-24 18:25:39,527 - INFO - Frame 1820 | PERCLOS: 0.18 | Yaw: 7.9° | Alerts: 1
2025-11-24 18:25:39,595 - INFO - Video thread started with source: Camera
2025-11-24 18:25:39,596 - ERROR - ❌ No camera found!
2025-11-24 18:25:39,690 - INFO - Video thread started with source: Camera
2025-11-24 18:25:39,691 - ERROR - ❌ No camera found!
2025-11-24 18:25:39,722 - INFO - Frame 1822 | PERCLOS: 0.35 | Yaw: 7.3° | Alerts: 2
2025-11-24 18:25:39,789 - INFO - Video thread started with source: Camera
2025-11-24 18:25:39,790 - ERROR - ❌ No camera found!
2025-11-24 18:25:39,879 - INFO - Video thread started with source: Camera
2025-11-24 18:25:39,880 - ERROR - ❌ No camera found!
2025-11-24 18:25:39,971 - INFO - Video thread started with source: Camera
2025-11-24 18:25:39,972 - ERROR - ❌ No camera found!
2025-11-24 18:25:39,993 - INFO - Frame 1824 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 18:25:40,060 - INFO - Video thread started with source: Camera
2025-11-24 18:25:40,061 - ERROR - ❌ No camera found!
2025-11-24 18:25:40,150 - INFO - Video thread started with source: Camera
2025-11-24 18:25:40,151 - ERROR - ❌ No camera found!
2025-11-24 18:25:40,180 - INFO - Frame 1826 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-24 18:25:40,244 - INFO - Video thread started with source: Camera
2025-11-24 18:25:40,245 - ERROR - ❌ No camera found!
2025-11-24 18:25:40,341 - INFO - Video thread started with source: Camera
2025-11-24 18:25:40,343 - ERROR - ❌ No camera found!
2025-11-24 18:25:40,371 - INFO - Frame 1828 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 18:25:40,446 - INFO - Video thread started with source: Camera
2025-11-24 18:25:40,447 - ERROR - ❌ No camera found!
2025-11-24 18:25:40,542 - INFO - Video thread started with source: Camera
2025-11-24 18:25:40,543 - ERROR - ❌ No camera found!
2025-11-24 18:25:40,641 - INFO - Video thread started with source: Camera
2025-11-24 18:25:40,641 - ERROR - ❌ No camera found!
2025-11-24 18:25:40,662 - INFO - Frame 1830 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 1
2025-11-24 18:25:40,736 - INFO - Video thread started with source: Camera
2025-11-24 18:25:40,737 - ERROR - ❌ No camera found!
2025-11-24 18:25:40,829 - INFO - Video thread started with source: Camera
2025-11-24 18:25:40,830 - ERROR - ❌ No camera found!
2025-11-24 18:25:40,861 - INFO - Frame 1832 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:25:40,923 - INFO - Video thread started with source: Camera
2025-11-24 18:25:40,924 - ERROR - ❌ No camera found!
2025-11-24 18:25:41,010 - INFO - Video thread started with source: Camera
2025-11-24 18:25:41,012 - ERROR - ❌ No camera found!
2025-11-24 18:25:41,042 - INFO - Frame 1834 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-24 18:25:41,110 - INFO - Video thread started with source: Camera
2025-11-24 18:25:41,111 - ERROR - ❌ No camera found!
2025-11-24 18:25:41,204 - INFO - Video thread started with source: Camera
2025-11-24 18:25:41,205 - ERROR - ❌ No camera found!
2025-11-24 18:25:41,300 - INFO - Video thread started with source: Camera
2025-11-24 18:25:41,301 - ERROR - ❌ No camera found!
2025-11-24 18:25:41,318 - INFO - Frame 1836 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 1
2025-11-24 18:25:41,396 - INFO - Video thread started with source: Camera
2025-11-24 18:25:41,397 - ERROR - ❌ No camera found!
2025-11-24 18:25:41,491 - INFO - Video thread started with source: Camera
2025-11-24 18:25:41,492 - ERROR - ❌ No camera found!
2025-11-24 18:25:41,522 - INFO - Frame 1838 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-24 18:25:41,591 - INFO - Video thread started with source: Camera
2025-11-24 18:25:41,592 - ERROR - ❌ No camera found!
2025-11-24 18:25:41,684 - INFO - Video thread started with source: Camera
2025-11-24 18:25:41,685 - ERROR - ❌ No camera found!
2025-11-24 18:25:41,715 - INFO - Frame 1840 | PERCLOS: 0.15 | Yaw: 4.4° | Alerts: 1
2025-11-24 18:25:41,783 - INFO - Video thread started with source: Camera
2025-11-24 18:25:41,784 - ERROR - ❌ No camera found!
2025-11-24 18:25:41,877 - INFO - Video thread started with source: Camera
2025-11-24 18:25:41,878 - ERROR - ❌ No camera found!
2025-11-24 18:25:41,972 - INFO - Video thread started with source: Camera
2025-11-24 18:25:41,973 - ERROR - ❌ No camera found!
2025-11-24 18:25:41,994 - INFO - Frame 1842 | PERCLOS: 0.00 | Yaw: 4.7° | Alerts: 1
2025-11-24 18:25:42,066 - INFO - Video thread started with source: Camera
2025-11-24 18:25:42,066 - ERROR - ❌ No camera found!
2025-11-24 18:25:42,162 - INFO - Video thread started with source: Camera
2025-11-24 18:25:42,162 - ERROR - ❌ No camera found!
2025-11-24 18:25:42,192 - INFO - Frame 1844 | PERCLOS: 0.04 | Yaw: 4.3° | Alerts: 1
2025-11-24 18:25:42,261 - INFO - Video thread started with source: Camera
2025-11-24 18:25:42,262 - ERROR - ❌ No camera found!
2025-11-24 18:25:42,356 - INFO - Video thread started with source: Camera
2025-11-24 18:25:42,357 - ERROR - ❌ No camera found!
2025-11-24 18:25:42,389 - INFO - Frame 1846 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 18:25:42,455 - INFO - Video thread started with source: Camera
2025-11-24 18:25:42,456 - ERROR - ❌ No camera found!
2025-11-24 18:43:25,842 - INFO - Loading models...
2025-11-24 18:43:25,866 - INFO - ✓ YOLO ONNX loaded
2025-11-24 18:43:25,901 - INFO - ✓ MediaPipe Face Mesh loaded
2025-11-24 18:43:25,910 - INFO - ✓ MediaPipe Pose loaded (for smoke & seatbelt)
2025-11-24 18:43:25,915 - INFO - Video thread started with source: Camera
2025-11-24 18:43:25,937 - INFO - Video thread started with source: Camera
2025-11-24 18:43:25,944 - ERROR - ❌ No camera found!
2025-11-24 18:43:26,093 - INFO - ✓ Camera 0 opened successfully
2025-11-24 18:43:26,099 - INFO - Video thread started with source: Camera
2025-11-24 18:43:26,100 - ERROR - ❌ No camera found!
2025-11-24 18:43:26,255 - INFO - Video thread started with source: Camera
2025-11-24 18:43:26,256 - ERROR - ❌ No camera found!
2025-11-24 18:43:26,407 - INFO - Video thread started with source: Camera
2025-11-24 18:43:26,408 - ERROR - ❌ No camera found!
2025-11-24 18:43:26,548 - INFO - Video thread started with source: Camera
2025-11-24 18:43:26,549 - ERROR - ❌ No camera found!
2025-11-24 18:43:26,685 - INFO - Video thread started with source: Camera
2025-11-24 18:43:26,686 - ERROR - ❌ No camera found!
2025-11-24 18:43:26,702 - INFO - Frame 0 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 1
2025-11-24 18:43:26,821 - INFO - Video thread started with source: Camera
2025-11-24 18:43:26,823 - ERROR - ❌ No camera found!
2025-11-24 18:43:26,960 - INFO - Video thread started with source: Camera
2025-11-24 18:43:26,962 - ERROR - ❌ No camera found!
2025-11-24 18:43:26,991 - INFO - Frame 2 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 1
2025-11-24 18:43:27,107 - INFO - Video thread started with source: Camera
2025-11-24 18:43:27,108 - ERROR - ❌ No camera found!
2025-11-24 18:43:27,254 - INFO - Video thread started with source: Camera
2025-11-24 18:43:27,255 - ERROR - ❌ No camera found!
2025-11-24 18:43:27,283 - INFO - Frame 4 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 1
2025-11-24 18:43:27,407 - INFO - Video thread started with source: Camera
2025-11-24 18:43:27,408 - ERROR - ❌ No camera found!
2025-11-24 18:43:27,563 - INFO - Video thread started with source: Camera
2025-11-24 18:43:27,569 - ERROR - ❌ No camera found!
2025-11-24 18:43:27,745 - INFO - Video thread started with source: Camera
2025-11-24 18:43:27,746 - ERROR - ❌ No camera found!
2025-11-24 18:43:27,762 - INFO - Frame 6 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:43:27,904 - INFO - Video thread started with source: Camera
2025-11-24 18:43:27,909 - ERROR - ❌ No camera found!
2025-11-24 18:43:28,067 - INFO - Video thread started with source: Camera
2025-11-24 18:43:28,067 - INFO - Frame 8 | PERCLOS: 0.11 | Yaw: 2.4° | Alerts: 1
2025-11-24 18:43:28,072 - ERROR - ❌ No camera found!
2025-11-24 18:43:28,221 - INFO - Video thread started with source: Camera
2025-11-24 18:43:28,222 - ERROR - ❌ No camera found!
2025-11-24 18:43:28,381 - INFO - Video thread started with source: Camera
2025-11-24 18:43:28,383 - ERROR - ❌ No camera found!
2025-11-24 18:43:28,383 - INFO - Frame 10 | PERCLOS: 0.00 | Yaw: 4.7° | Alerts: 1
2025-11-24 18:43:28,530 - INFO - Video thread started with source: Camera
2025-11-24 18:43:28,535 - ERROR - ❌ No camera found!
2025-11-24 18:43:28,679 - INFO - Video thread started with source: Camera
2025-11-24 18:43:28,682 - ERROR - ❌ No camera found!
2025-11-24 18:43:28,844 - INFO - Frame 12 | PERCLOS: 0.00 | Yaw: 5.8° | Alerts: 1
2025-11-24 18:43:28,844 - INFO - Video thread started with source: Camera
2025-11-24 18:43:28,845 - ERROR - ❌ No camera found!
2025-11-24 18:43:29,003 - INFO - Video thread started with source: Camera
2025-11-24 18:43:29,004 - ERROR - ❌ No camera found!
2025-11-24 18:43:29,146 - INFO - Video thread started with source: Camera
2025-11-24 18:43:29,150 - ERROR - ❌ No camera found!
2025-11-24 18:43:29,176 - INFO - Frame 14 | PERCLOS: 0.00 | Yaw: 6.1° | Alerts: 1
2025-11-24 18:43:29,313 - INFO - Video thread started with source: Camera
2025-11-24 18:43:29,316 - ERROR - ❌ No camera found!
2025-11-24 18:43:29,465 - INFO - Video thread started with source: Camera
2025-11-24 18:43:29,466 - ERROR - ❌ No camera found!
2025-11-24 18:43:29,492 - INFO - Frame 16 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 1
2025-11-24 18:43:29,616 - INFO - Video thread started with source: Camera
2025-11-24 18:43:29,617 - ERROR - ❌ No camera found!
2025-11-24 18:43:29,766 - INFO - Video thread started with source: Camera
2025-11-24 18:43:29,768 - ERROR - ❌ No camera found!
2025-11-24 18:43:29,931 - INFO - Video thread started with source: Camera
2025-11-24 18:43:29,932 - ERROR - ❌ No camera found!
2025-11-24 18:43:29,948 - INFO - Frame 18 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 1
2025-11-24 18:43:30,077 - INFO - Video thread started with source: Camera
2025-11-24 18:43:30,080 - ERROR - ❌ No camera found!
2025-11-24 18:43:30,232 - INFO - Video thread started with source: Camera
2025-11-24 18:43:30,233 - ERROR - ❌ No camera found!
2025-11-24 18:43:30,262 - INFO - Frame 20 | PERCLOS: 0.00 | Yaw: 6.1° | Alerts: 1
2025-11-24 18:43:30,390 - INFO - Video thread started with source: Camera
2025-11-24 18:43:30,392 - ERROR - ❌ No camera found!
2025-11-24 18:43:30,557 - INFO - Video thread started with source: Camera
2025-11-24 18:43:30,558 - ERROR - ❌ No camera found!
2025-11-24 18:43:30,558 - INFO - Frame 22 | PERCLOS: 0.00 | Yaw: 6.4° | Alerts: 1
2025-11-24 18:43:30,705 - INFO - Video thread started with source: Camera
2025-11-24 18:43:30,705 - ERROR - ❌ No camera found!
2025-11-24 18:43:30,859 - INFO - Video thread started with source: Camera
2025-11-24 18:43:30,860 - ERROR - ❌ No camera found!
2025-11-24 18:43:30,877 - INFO - Frame 24 | PERCLOS: 0.00 | Yaw: 6.1° | Alerts: 1
2025-11-24 18:43:31,004 - INFO - Video thread started with source: Camera
2025-11-24 18:43:31,005 - ERROR - ❌ No camera found!
2025-11-24 18:43:31,166 - INFO - Video thread started with source: Camera
2025-11-24 18:43:31,170 - ERROR - ❌ No camera found!
2025-11-24 18:43:31,171 - INFO - Frame 26 | PERCLOS: 0.00 | Yaw: 5.2° | Alerts: 1
2025-11-24 18:43:31,316 - INFO - Video thread started with source: Camera
2025-11-24 18:43:31,318 - ERROR - ❌ No camera found!
2025-11-24 18:43:31,478 - INFO - Video thread started with source: Camera
2025-11-24 18:43:31,482 - ERROR - ❌ No camera found!
2025-11-24 18:43:31,499 - INFO - Frame 28 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 1
2025-11-24 18:43:31,630 - INFO - Video thread started with source: Camera
2025-11-24 18:43:31,631 - ERROR - ❌ No camera found!
2025-11-24 18:43:31,784 - INFO - Video thread started with source: Camera
2025-11-24 18:43:31,788 - ERROR - ❌ No camera found!
2025-11-24 18:43:31,935 - INFO - Video thread started with source: Camera
2025-11-24 18:43:31,940 - ERROR - ❌ No camera found!
2025-11-24 18:43:31,953 - INFO - Frame 30 | PERCLOS: 0.00 | Yaw: 4.8° | Alerts: 1
2025-11-24 18:43:32,097 - INFO - Video thread started with source: Camera
2025-11-24 18:43:32,098 - ERROR - ❌ No camera found!
2025-11-24 18:43:32,256 - INFO - Video thread started with source: Camera
2025-11-24 18:43:32,257 - ERROR - ❌ No camera found!
2025-11-24 18:43:32,286 - INFO - Frame 32 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 18:43:32,416 - INFO - Video thread started with source: Camera
2025-11-24 18:43:32,422 - ERROR - ❌ No camera found!
2025-11-24 18:43:32,569 - INFO - Video thread started with source: Camera
2025-11-24 18:43:32,570 - ERROR - ❌ No camera found!
2025-11-24 18:43:32,595 - INFO - Frame 34 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 1
2025-11-24 18:43:32,722 - INFO - Video thread started with source: Camera
2025-11-24 18:43:32,723 - ERROR - ❌ No camera found!
2025-11-24 18:43:32,883 - INFO - Video thread started with source: Camera
2025-11-24 18:43:32,886 - ERROR - ❌ No camera found!
2025-11-24 18:43:33,036 - INFO - Frame 36 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 1
2025-11-24 18:43:33,041 - INFO - Video thread started with source: Camera
2025-11-24 18:43:33,042 - ERROR - ❌ No camera found!
2025-11-24 18:43:33,202 - INFO - Video thread started with source: Camera
2025-11-24 18:43:33,208 - ERROR - ❌ No camera found!
2025-11-24 18:43:33,350 - INFO - Video thread started with source: Camera
2025-11-24 18:43:33,360 - ERROR - ❌ No camera found!
2025-11-24 18:43:33,380 - INFO - Frame 38 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 1
2025-11-24 18:43:33,506 - INFO - Video thread started with source: Camera
2025-11-24 18:43:33,511 - ERROR - ❌ No camera found!
2025-11-24 18:43:33,661 - INFO - Video thread started with source: Camera
2025-11-24 18:43:33,663 - ERROR - ❌ No camera found!
2025-11-24 18:43:33,688 - INFO - Frame 40 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 1
2025-11-24 18:43:33,835 - INFO - Video thread started with source: Camera
2025-11-24 18:43:33,836 - ERROR - ❌ No camera found!
2025-11-24 18:43:33,997 - INFO - Video thread started with source: Camera
2025-11-24 18:43:34,000 - ERROR - ❌ No camera found!
2025-11-24 18:43:34,162 - INFO - Video thread started with source: Camera
2025-11-24 18:43:34,163 - ERROR - ❌ No camera found!
2025-11-24 18:43:34,179 - INFO - Frame 42 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 1
2025-11-24 18:43:34,318 - INFO - Video thread started with source: Camera
2025-11-24 18:43:34,323 - ERROR - ❌ No camera found!
2025-11-24 18:43:34,469 - INFO - Video thread started with source: Camera
2025-11-24 18:43:34,470 - ERROR - ❌ No camera found!
2025-11-24 18:43:34,494 - INFO - Frame 44 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 1
2025-11-24 18:43:34,615 - INFO - Video thread started with source: Camera
2025-11-24 18:43:34,616 - ERROR - ❌ No camera found!
2025-11-24 18:43:34,761 - INFO - Video thread started with source: Camera
2025-11-24 18:43:34,764 - ERROR - ❌ No camera found!
2025-11-24 18:43:34,789 - INFO - Frame 46 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:43:34,926 - INFO - Video thread started with source: Camera
2025-11-24 18:43:34,927 - ERROR - ❌ No camera found!
2025-11-24 18:43:35,082 - INFO - Video thread started with source: Camera
2025-11-24 18:43:35,085 - ERROR - ❌ No camera found!
2025-11-24 18:43:35,226 - INFO - Frame 48 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-24 18:43:35,230 - INFO - Video thread started with source: Camera
2025-11-24 18:43:35,231 - ERROR - ❌ No camera found!
2025-11-24 18:43:35,369 - INFO - Video thread started with source: Camera
2025-11-24 18:43:35,370 - ERROR - ❌ No camera found!
2025-11-24 18:43:35,520 - INFO - Video thread started with source: Camera
2025-11-24 18:43:35,524 - ERROR - ❌ No camera found!
2025-11-24 18:43:35,545 - INFO - Frame 50 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 1
2025-11-24 18:43:35,671 - INFO - Video thread started with source: Camera
2025-11-24 18:43:35,676 - ERROR - ❌ No camera found!
2025-11-24 18:43:35,832 - INFO - Video thread started with source: Camera
2025-11-24 18:43:35,839 - ERROR - ❌ No camera found!
2025-11-24 18:43:35,860 - INFO - Frame 52 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-24 18:43:35,999 - INFO - Video thread started with source: Camera
2025-11-24 18:43:36,004 - ERROR - ❌ No camera found!
2025-11-24 18:43:36,150 - INFO - Video thread started with source: Camera
2025-11-24 18:43:36,153 - ERROR - ❌ No camera found!
2025-11-24 18:43:36,302 - INFO - Video thread started with source: Camera
2025-11-24 18:43:36,303 - ERROR - ❌ No camera found!
2025-11-24 18:43:36,318 - INFO - Frame 54 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 1
2025-11-24 18:43:36,461 - INFO - Video thread started with source: Camera
2025-11-24 18:43:36,463 - ERROR - ❌ No camera found!
2025-11-24 18:43:36,618 - INFO - Video thread started with source: Camera
2025-11-24 18:43:36,620 - ERROR - ❌ No camera found!
2025-11-24 18:43:36,651 - INFO - Frame 56 | PERCLOS: 0.00 | Yaw: 0.2° | Alerts: 1
2025-11-24 18:43:36,821 - INFO - Video thread started with source: Camera
2025-11-24 18:43:36,826 - ERROR - ❌ No camera found!
2025-11-24 18:43:36,981 - INFO - Video thread started with source: Camera
2025-11-24 18:43:36,984 - ERROR - ❌ No camera found!
2025-11-24 18:43:37,003 - INFO - Frame 58 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 1
2025-11-24 18:43:37,118 - INFO - Video thread started with source: Camera
2025-11-24 18:43:37,121 - ERROR - ❌ No camera found!
2025-11-24 18:43:37,267 - INFO - Video thread started with source: Camera
2025-11-24 18:43:37,270 - ERROR - ❌ No camera found!
2025-11-24 18:43:37,433 - INFO - Video thread started with source: Camera
2025-11-24 18:43:37,438 - ERROR - ❌ No camera found!
2025-11-24 18:43:37,452 - INFO - Frame 60 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 1
2025-11-24 18:43:37,591 - INFO - Video thread started with source: Camera
2025-11-24 18:43:37,594 - ERROR - ❌ No camera found!
2025-11-24 18:43:37,738 - INFO - Video thread started with source: Camera
2025-11-24 18:43:37,740 - ERROR - ❌ No camera found!
2025-11-24 18:43:37,767 - INFO - Frame 62 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 18:43:37,908 - INFO - Video thread started with source: Camera
2025-11-24 18:43:37,909 - ERROR - ❌ No camera found!
2025-11-24 18:43:38,066 - INFO - Video thread started with source: Camera
2025-11-24 18:43:38,067 - ERROR - ❌ No camera found!
2025-11-24 18:43:38,091 - INFO - Frame 64 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 18:43:38,235 - INFO - Video thread started with source: Camera
2025-11-24 18:43:38,239 - ERROR - ❌ No camera found!
2025-11-24 18:43:38,383 - INFO - Video thread started with source: Camera
2025-11-24 18:43:38,390 - ERROR - ❌ No camera found!
2025-11-24 18:43:38,537 - INFO - Video thread started with source: Camera
2025-11-24 18:43:38,538 - ERROR - ❌ No camera found!
2025-11-24 18:43:38,555 - INFO - Frame 66 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 1
2025-11-24 18:43:38,687 - INFO - Video thread started with source: Camera
2025-11-24 18:43:38,688 - ERROR - ❌ No camera found!
2025-11-24 18:43:38,839 - INFO - Video thread started with source: Camera
2025-11-24 18:43:38,842 - ERROR - ❌ No camera found!
2025-11-24 18:43:38,869 - INFO - Frame 68 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 18:43:39,000 - INFO - Video thread started with source: Camera
2025-11-24 18:43:39,003 - ERROR - ❌ No camera found!
2025-11-24 18:43:39,154 - INFO - Video thread started with source: Camera
2025-11-24 18:43:39,155 - ERROR - ❌ No camera found!
2025-11-24 18:43:39,180 - INFO - Frame 70 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-24 18:43:39,315 - INFO - Video thread started with source: Camera
2025-11-24 18:43:39,320 - ERROR - ❌ No camera found!
2025-11-24 18:43:39,478 - INFO - Video thread started with source: Camera
2025-11-24 18:43:39,488 - ERROR - ❌ No camera found!
2025-11-24 18:43:39,645 - INFO - Video thread started with source: Camera
2025-11-24 18:43:39,646 - ERROR - ❌ No camera found!
2025-11-24 18:43:39,662 - INFO - Frame 72 | PERCLOS: 0.00 | Yaw: 6.1° | Alerts: 1
2025-11-24 18:43:39,802 - INFO - Video thread started with source: Camera
2025-11-24 18:43:39,803 - ERROR - ❌ No camera found!
2025-11-24 18:43:39,947 - INFO - Video thread started with source: Camera
2025-11-24 18:43:39,948 - ERROR - ❌ No camera found!
2025-11-24 18:43:39,972 - INFO - Frame 74 | PERCLOS: 0.00 | Yaw: 6.8° | Alerts: 1
2025-11-24 18:43:40,100 - INFO - Video thread started with source: Camera
2025-11-24 18:43:40,102 - ERROR - ❌ No camera found!
2025-11-24 18:43:40,260 - INFO - Video thread started with source: Camera
2025-11-24 18:43:40,264 - ERROR - ❌ No camera found!
2025-11-24 18:43:40,281 - INFO - Frame 76 | PERCLOS: 0.00 | Yaw: 7.2° | Alerts: 1
2025-11-24 18:43:40,409 - INFO - Video thread started with source: Camera
2025-11-24 18:43:40,410 - ERROR - ❌ No camera found!
2025-11-24 18:43:40,554 - INFO - Video thread started with source: Camera
2025-11-24 18:43:40,555 - ERROR - ❌ No camera found!
2025-11-24 18:43:40,710 - INFO - Video thread started with source: Camera
2025-11-24 18:43:40,710 - ERROR - ❌ No camera found!
2025-11-24 18:43:40,727 - INFO - Frame 78 | PERCLOS: 0.00 | Yaw: 7.5° | Alerts: 1
2025-11-24 18:43:40,865 - INFO - Video thread started with source: Camera
2025-11-24 18:43:40,866 - ERROR - ❌ No camera found!
2025-11-24 18:43:41,020 - INFO - Video thread started with source: Camera
2025-11-24 18:43:41,024 - ERROR - ❌ No camera found!
2025-11-24 18:43:41,046 - INFO - Frame 80 | PERCLOS: 0.00 | Yaw: 7.6° | Alerts: 1
2025-11-24 18:43:41,184 - INFO - Video thread started with source: Camera
2025-11-24 18:43:41,187 - ERROR - ❌ No camera found!
2025-11-24 18:43:41,330 - INFO - Video thread started with source: Camera
2025-11-24 18:43:41,331 - ERROR - ❌ No camera found!
2025-11-24 18:43:41,363 - INFO - Frame 82 | PERCLOS: 0.00 | Yaw: 7.5° | Alerts: 1
2025-11-24 18:43:41,479 - INFO - Video thread started with source: Camera
2025-11-24 18:43:41,480 - ERROR - ❌ No camera found!
2025-11-24 18:43:41,637 - INFO - Video thread started with source: Camera
2025-11-24 18:43:41,640 - ERROR - ❌ No camera found!
2025-11-24 18:43:41,797 - INFO - Frame 84 | PERCLOS: 0.00 | Yaw: 7.6° | Alerts: 1
2025-11-24 18:43:41,804 - INFO - Video thread started with source: Camera
2025-11-24 18:43:41,805 - ERROR - ❌ No camera found!
2025-11-24 18:43:41,963 - INFO - Video thread started with source: Camera
2025-11-24 18:43:41,964 - ERROR - ❌ No camera found!
2025-11-24 18:43:42,069 - INFO - Video thread started with source: Camera
2025-11-24 18:43:42,071 - ERROR - ❌ No camera found!
2025-11-24 18:43:42,103 - INFO - Frame 86 | PERCLOS: 0.00 | Yaw: 7.6° | Alerts: 1
2025-11-24 18:43:42,175 - INFO - Video thread started with source: Camera
2025-11-24 18:43:42,176 - ERROR - ❌ No camera found!
2025-11-24 18:43:42,208 - INFO - Video thread started with source: Camera
2025-11-24 18:43:42,210 - ERROR - ❌ No camera found!
2025-11-24 18:43:42,337 - INFO - Video thread started with source: Camera
2025-11-24 18:43:42,338 - INFO - Video thread started with source: Camera
2025-11-24 18:43:42,339 - ERROR - ❌ No camera found!
2025-11-24 18:43:42,339 - ERROR - ❌ No camera found!
2025-11-24 18:43:42,369 - INFO - Frame 88 | PERCLOS: 0.00 | Yaw: 7.4° | Alerts: 1
2025-11-24 18:43:42,490 - INFO - Video thread started with source: Camera
2025-11-24 18:43:42,491 - ERROR - ❌ No camera found!
2025-11-24 18:43:42,491 - INFO - Video thread started with source: Camera
2025-11-24 18:43:42,492 - ERROR - ❌ No camera found!
2025-11-24 18:43:42,634 - INFO - Video thread started with source: Camera
2025-11-24 18:43:42,636 - ERROR - ❌ No camera found!
2025-11-24 18:43:42,636 - INFO - Video thread started with source: Camera
2025-11-24 18:43:42,637 - ERROR - ❌ No camera found!
2025-11-24 18:43:42,787 - INFO - Video thread started with source: Camera
2025-11-24 18:43:42,789 - INFO - Video thread started with source: Camera
2025-11-24 18:43:42,790 - ERROR - ❌ No camera found!
2025-11-24 18:43:42,790 - ERROR - ❌ No camera found!
2025-11-24 18:43:42,803 - INFO - Frame 90 | PERCLOS: 0.00 | Yaw: 7.3° | Alerts: 1
2025-11-24 18:43:42,939 - INFO - Video thread started with source: Camera
2025-11-24 18:43:42,940 - INFO - Video thread started with source: Camera
2025-11-24 18:43:42,941 - ERROR - ❌ No camera found!
2025-11-24 18:43:42,941 - ERROR - ❌ No camera found!
2025-11-24 18:43:43,097 - INFO - Video thread started with source: Camera
2025-11-24 18:43:43,098 - ERROR - ❌ No camera found!
2025-11-24 18:43:43,099 - INFO - Video thread started with source: Camera
2025-11-24 18:43:43,100 - ERROR - ❌ No camera found!
2025-11-24 18:43:43,287 - INFO - Video thread started with source: Camera
2025-11-24 18:43:43,288 - ERROR - ❌ No camera found!
2025-11-24 18:43:43,289 - INFO - Frame 92 | PERCLOS: 0.00 | Yaw: 7.6° | Alerts: 1
2025-11-24 18:43:43,290 - INFO - Video thread started with source: Camera
2025-11-24 18:43:43,292 - ERROR - ❌ No camera found!
2025-11-24 18:43:43,447 - INFO - Video thread started with source: Camera
2025-11-24 18:43:43,450 - ERROR - ❌ No camera found!
2025-11-24 18:43:43,450 - INFO - Video thread started with source: Camera
2025-11-24 18:43:43,452 - ERROR - ❌ No camera found!
2025-11-24 18:43:43,606 - INFO - Video thread started with source: Camera
2025-11-24 18:43:43,607 - INFO - Video thread started with source: Camera
2025-11-24 18:43:43,609 - ERROR - ❌ No camera found!
2025-11-24 18:43:43,609 - ERROR - ❌ No camera found!
2025-11-24 18:43:43,609 - INFO - Frame 94 | PERCLOS: 0.00 | Yaw: 7.6° | Alerts: 1
2025-11-24 18:43:43,755 - INFO - Video thread started with source: Camera
2025-11-24 18:43:43,755 - INFO - Video thread started with source: Camera
2025-11-24 18:43:43,756 - ERROR - ❌ No camera found!
2025-11-24 18:43:43,756 - ERROR - ❌ No camera found!
2025-11-24 18:43:43,902 - INFO - Video thread started with source: Camera
2025-11-24 18:43:43,902 - ERROR - ❌ No camera found!
2025-11-24 18:43:43,903 - ERROR - ❌ No camera found!
2025-11-24 18:43:43,903 - INFO - Video thread started with source: Camera
2025-11-24 18:43:44,051 - INFO - Video thread started with source: Camera
2025-11-24 18:43:44,051 - INFO - Frame 96 | PERCLOS: 0.00 | Yaw: 7.4° | Alerts: 1
2025-11-24 18:43:44,053 - ERROR - ❌ No camera found!
2025-11-24 18:43:44,054 - INFO - Video thread started with source: Camera
2025-11-24 18:43:44,055 - ERROR - ❌ No camera found!
2025-11-24 18:43:44,196 - INFO - Video thread started with source: Camera
2025-11-24 18:43:44,199 - ERROR - ❌ No camera found!
2025-11-24 18:43:44,199 - INFO - Video thread started with source: Camera
2025-11-24 18:43:44,200 - ERROR - ❌ No camera found!
2025-11-24 18:43:44,234 - INFO - Frame 98 | PERCLOS: 0.00 | Yaw: 7.3° | Alerts: 1
2025-11-24 18:43:44,349 - INFO - Video thread started with source: Camera
2025-11-24 18:43:44,351 - ERROR - ❌ No camera found!
2025-11-24 18:43:44,352 - INFO - Video thread started with source: Camera
2025-11-24 18:43:44,356 - ERROR - ❌ No camera found!
2025-11-24 18:43:44,504 - INFO - Video thread started with source: Camera
2025-11-24 18:43:44,505 - INFO - Video thread started with source: Camera
2025-11-24 18:43:44,505 - ERROR - ❌ No camera found!
2025-11-24 18:43:44,507 - ERROR - ❌ No camera found!
2025-11-24 18:43:44,533 - INFO - Frame 100 | PERCLOS: 0.00 | Yaw: 6.6° | Alerts: 1
2025-11-24 18:43:44,654 - INFO - Video thread started with source: Camera
2025-11-24 18:43:44,656 - INFO - Video thread started with source: Camera
2025-11-24 18:43:44,657 - ERROR - ❌ No camera found!
2025-11-24 18:43:44,657 - ERROR - ❌ No camera found!
2025-11-24 18:43:44,808 - INFO - Video thread started with source: Camera
2025-11-24 18:43:44,809 - INFO - Video thread started with source: Camera
2025-11-24 18:43:44,810 - ERROR - ❌ No camera found!
2025-11-24 18:43:44,810 - ERROR - ❌ No camera found!
2025-11-24 18:43:44,969 - INFO - Video thread started with source: Camera
2025-11-24 18:43:44,970 - INFO - Video thread started with source: Camera
2025-11-24 18:43:44,970 - ERROR - ❌ No camera found!
2025-11-24 18:43:44,971 - ERROR - ❌ No camera found!
2025-11-24 18:43:44,985 - INFO - Frame 102 | PERCLOS: 0.00 | Yaw: 6.7° | Alerts: 1
2025-11-24 18:43:45,125 - INFO - Video thread started with source: Camera
2025-11-24 18:43:45,126 - INFO - Video thread started with source: Camera
2025-11-24 18:43:45,127 - ERROR - ❌ No camera found!
2025-11-24 18:43:45,127 - ERROR - ❌ No camera found!
2025-11-24 18:43:45,290 - INFO - Video thread started with source: Camera
2025-11-24 18:43:45,290 - INFO - Frame 104 | PERCLOS: 0.00 | Yaw: 7.0° | Alerts: 1
2025-11-24 18:43:45,291 - INFO - Video thread started with source: Camera
2025-11-24 18:43:45,292 - ERROR - ❌ No camera found!
2025-11-24 18:43:45,292 - ERROR - ❌ No camera found!
2025-11-24 18:43:45,452 - INFO - Video thread started with source: Camera
2025-11-24 18:43:45,452 - INFO - Video thread started with source: Camera
2025-11-24 18:43:45,454 - ERROR - ❌ No camera found!
2025-11-24 18:43:45,454 - ERROR - ❌ No camera found!
2025-11-24 18:43:45,491 - INFO - Frame 106 | PERCLOS: 0.00 | Yaw: 7.0° | Alerts: 1
2025-11-24 18:43:45,610 - INFO - Video thread started with source: Camera
2025-11-24 18:43:45,610 - INFO - Video thread started with source: Camera
2025-11-24 18:43:45,611 - ERROR - ❌ No camera found!
2025-11-24 18:43:45,611 - ERROR - ❌ No camera found!
2025-11-24 18:43:45,758 - INFO - Video thread started with source: Camera
2025-11-24 18:43:45,758 - INFO - Video thread started with source: Camera
2025-11-24 18:43:45,760 - ERROR - ❌ No camera found!
2025-11-24 18:43:45,761 - ERROR - ❌ No camera found!
2025-11-24 18:43:45,919 - INFO - Frame 108 | PERCLOS: 0.00 | Yaw: 7.1° | Alerts: 1
2025-11-24 18:43:45,920 - INFO - Video thread started with source: Camera
2025-11-24 18:43:45,921 - ERROR - ❌ No camera found!
2025-11-24 18:43:45,922 - INFO - Video thread started with source: Camera
2025-11-24 18:43:45,927 - ERROR - ❌ No camera found!
2025-11-24 18:43:46,087 - INFO - Video thread started with source: Camera
2025-11-24 18:43:46,089 - INFO - Video thread started with source: Camera
2025-11-24 18:43:46,091 - ERROR - ❌ No camera found!
2025-11-24 18:43:46,091 - ERROR - ❌ No camera found!
2025-11-24 18:43:46,130 - INFO - Frame 110 | PERCLOS: 0.00 | Yaw: 7.0° | Alerts: 1
2025-11-24 18:43:46,249 - INFO - Video thread started with source: Camera
2025-11-24 18:43:46,249 - INFO - Video thread started with source: Camera
2025-11-24 18:43:46,250 - ERROR - ❌ No camera found!
2025-11-24 18:43:46,250 - ERROR - ❌ No camera found!
2025-11-24 18:43:46,400 - INFO - Video thread started with source: Camera
2025-11-24 18:43:46,403 - INFO - Video thread started with source: Camera
2025-11-24 18:43:46,403 - ERROR - ❌ No camera found!
2025-11-24 18:43:46,404 - ERROR - ❌ No camera found!
2025-11-24 18:43:46,562 - INFO - Frame 112 | PERCLOS: 0.00 | Yaw: 6.9° | Alerts: 1
2025-11-24 18:43:46,565 - INFO - Video thread started with source: Camera
2025-11-24 18:43:46,566 - INFO - Video thread started with source: Camera
2025-11-24 18:43:46,567 - ERROR - ❌ No camera found!
2025-11-24 18:43:46,569 - ERROR - ❌ No camera found!
2025-11-24 18:43:46,726 - INFO - Video thread started with source: Camera
2025-11-24 18:43:46,728 - ERROR - ❌ No camera found!
2025-11-24 18:43:46,728 - INFO - Video thread started with source: Camera
2025-11-24 18:43:46,729 - ERROR - ❌ No camera found!
2025-11-24 18:43:46,896 - INFO - Video thread started with source: Camera
2025-11-24 18:43:46,896 - INFO - Video thread started with source: Camera
2025-11-24 18:43:46,897 - ERROR - ❌ No camera found!
2025-11-24 18:43:46,897 - ERROR - ❌ No camera found!
2025-11-24 18:43:46,916 - INFO - Frame 114 | PERCLOS: 0.00 | Yaw: 6.6° | Alerts: 1
2025-11-24 18:43:47,039 - INFO - Video thread started with source: Camera
2025-11-24 18:43:47,041 - INFO - Video thread started with source: Camera
2025-11-24 18:43:47,041 - ERROR - ❌ No camera found!
2025-11-24 18:43:47,043 - ERROR - ❌ No camera found!
2025-11-24 18:43:47,196 - INFO - Video thread started with source: Camera
2025-11-24 18:43:47,197 - INFO - Video thread started with source: Camera
2025-11-24 18:43:47,197 - ERROR - ❌ No camera found!
2025-11-24 18:43:47,198 - ERROR - ❌ No camera found!
2025-11-24 18:43:47,229 - INFO - Frame 116 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 1
2025-11-24 18:43:47,354 - INFO - Video thread started with source: Camera
2025-11-24 18:43:47,354 - INFO - Video thread started with source: Camera
2025-11-24 18:43:47,355 - ERROR - ❌ No camera found!
2025-11-24 18:43:47,356 - ERROR - ❌ No camera found!
2025-11-24 18:43:47,511 - INFO - Video thread started with source: Camera
2025-11-24 18:43:47,512 - ERROR - ❌ No camera found!
2025-11-24 18:43:47,514 - INFO - Video thread started with source: Camera
2025-11-24 18:43:47,517 - ERROR - ❌ No camera found!
2025-11-24 18:43:47,542 - INFO - Frame 118 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 1
2025-11-24 18:43:47,670 - INFO - Video thread started with source: Camera
2025-11-24 18:43:47,673 - INFO - Video thread started with source: Camera
2025-11-24 18:43:47,673 - ERROR - ❌ No camera found!
2025-11-24 18:43:47,674 - ERROR - ❌ No camera found!
2025-11-24 18:43:47,833 - INFO - Video thread started with source: Camera
2025-11-24 18:43:47,835 - ERROR - ❌ No camera found!
2025-11-24 18:43:47,837 - INFO - Video thread started with source: Camera
2025-11-24 18:43:47,838 - ERROR - ❌ No camera found!
2025-11-24 18:43:47,978 - INFO - Video thread started with source: Camera
2025-11-24 18:43:47,979 - ERROR - ❌ No camera found!
2025-11-24 18:43:47,979 - INFO - Video thread started with source: Camera
2025-11-24 18:43:47,979 - ERROR - ❌ No camera found!
2025-11-24 18:43:47,997 - INFO - Frame 120 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 1
2025-11-24 18:43:48,131 - INFO - Video thread started with source: Camera
2025-11-24 18:43:48,133 - INFO - Video thread started with source: Camera
2025-11-24 18:43:48,134 - ERROR - ❌ No camera found!
2025-11-24 18:43:48,134 - ERROR - ❌ No camera found!
2025-11-24 18:43:48,285 - INFO - Video thread started with source: Camera
2025-11-24 18:43:48,288 - ERROR - ❌ No camera found!
2025-11-24 18:43:48,289 - INFO - Video thread started with source: Camera
2025-11-24 18:43:48,290 - ERROR - ❌ No camera found!
2025-11-24 18:43:48,314 - INFO - Frame 122 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 1
2025-11-24 18:43:48,446 - INFO - Video thread started with source: Camera
2025-11-24 18:43:48,446 - INFO - Video thread started with source: Camera
2025-11-24 18:43:48,448 - ERROR - ❌ No camera found!
2025-11-24 18:43:48,448 - ERROR - ❌ No camera found!
2025-11-24 18:43:48,594 - INFO - Video thread started with source: Camera
2025-11-24 18:43:48,597 - INFO - Video thread started with source: Camera
2025-11-24 18:43:48,597 - ERROR - ❌ No camera found!
2025-11-24 18:43:48,598 - ERROR - ❌ No camera found!
2025-11-24 18:43:48,621 - INFO - Frame 124 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 1
2025-11-24 18:43:48,747 - INFO - Video thread started with source: Camera
2025-11-24 18:43:48,749 - INFO - Video thread started with source: Camera
2025-11-24 18:43:48,749 - ERROR - ❌ No camera found!
2025-11-24 18:43:48,749 - ERROR - ❌ No camera found!
2025-11-24 18:43:48,903 - INFO - Video thread started with source: Camera
2025-11-24 18:43:48,905 - INFO - Video thread started with source: Camera
2025-11-24 18:43:48,905 - ERROR - ❌ No camera found!
2025-11-24 18:43:48,907 - ERROR - ❌ No camera found!
2025-11-24 18:43:49,061 - INFO - Frame 126 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 1
2025-11-24 18:43:49,063 - INFO - Video thread started with source: Camera
2025-11-24 18:43:49,066 - INFO - Video thread started with source: Camera
2025-11-24 18:43:49,066 - ERROR - ❌ No camera found!
2025-11-24 18:43:49,067 - ERROR - ❌ No camera found!
2025-11-24 18:43:49,208 - INFO - Video thread started with source: Camera
2025-11-24 18:43:49,208 - INFO - Video thread started with source: Camera
2025-11-24 18:43:49,209 - ERROR - ❌ No camera found!
2025-11-24 18:43:49,209 - ERROR - ❌ No camera found!
2025-11-24 18:43:49,244 - INFO - Frame 128 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 1
2025-11-24 18:43:49,379 - INFO - Video thread started with source: Camera
2025-11-24 18:43:49,380 - INFO - Video thread started with source: Camera
2025-11-24 18:43:49,380 - ERROR - ❌ No camera found!
2025-11-24 18:43:49,382 - ERROR - ❌ No camera found!
2025-11-24 18:43:49,540 - INFO - Video thread started with source: Camera
2025-11-24 18:43:49,540 - INFO - Video thread started with source: Camera
2025-11-24 18:43:49,540 - ERROR - ❌ No camera found!
2025-11-24 18:43:49,541 - ERROR - ❌ No camera found!
2025-11-24 18:43:49,562 - INFO - Frame 130 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 1
2025-11-24 18:43:49,690 - INFO - Video thread started with source: Camera
2025-11-24 18:43:49,692 - ERROR - ❌ No camera found!
2025-11-24 18:43:49,692 - INFO - Video thread started with source: Camera
2025-11-24 18:43:49,693 - ERROR - ❌ No camera found!
2025-11-24 18:43:49,845 - INFO - Video thread started with source: Camera
2025-11-24 18:43:49,847 - INFO - Video thread started with source: Camera
2025-11-24 18:43:49,847 - ERROR - ❌ No camera found!
2025-11-24 18:43:49,849 - ERROR - ❌ No camera found!
2025-11-24 18:43:50,007 - INFO - Video thread started with source: Camera
2025-11-24 18:43:50,008 - ERROR - ❌ No camera found!
2025-11-24 18:43:50,009 - INFO - Video thread started with source: Camera
2025-11-24 18:43:50,011 - ERROR - ❌ No camera found!
2025-11-24 18:43:50,027 - INFO - Frame 132 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 1
2025-11-24 18:43:50,165 - INFO - Video thread started with source: Camera
2025-11-24 18:43:50,167 - INFO - Video thread started with source: Camera
2025-11-24 18:43:50,167 - ERROR - ❌ No camera found!
2025-11-24 18:43:50,168 - ERROR - ❌ No camera found!
2025-11-24 18:43:50,313 - INFO - Video thread started with source: Camera
2025-11-24 18:43:50,315 - INFO - Video thread started with source: Camera
2025-11-24 18:43:50,316 - ERROR - ❌ No camera found!
2025-11-24 18:43:50,317 - ERROR - ❌ No camera found!
2025-11-24 18:43:50,346 - INFO - Frame 134 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 1
2025-11-24 18:43:50,478 - INFO - Video thread started with source: Camera
2025-11-24 18:43:50,480 - ERROR - ❌ No camera found!
2025-11-24 18:43:50,480 - INFO - Video thread started with source: Camera
2025-11-24 18:43:50,481 - ERROR - ❌ No camera found!
2025-11-24 18:43:50,628 - INFO - Video thread started with source: Camera
2025-11-24 18:43:50,631 - ERROR - ❌ No camera found!
2025-11-24 18:43:50,631 - INFO - Video thread started with source: Camera
2025-11-24 18:43:50,632 - ERROR - ❌ No camera found!
2025-11-24 18:43:50,657 - INFO - Frame 136 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 1
2025-11-24 18:43:50,777 - INFO - Video thread started with source: Camera
2025-11-24 18:43:50,777 - INFO - Video thread started with source: Camera
2025-11-24 18:43:50,778 - ERROR - ❌ No camera found!
2025-11-24 18:43:50,779 - ERROR - ❌ No camera found!
2025-11-24 18:43:50,944 - INFO - Video thread started with source: Camera
2025-11-24 18:43:50,944 - INFO - Video thread started with source: Camera
2025-11-24 18:43:50,945 - ERROR - ❌ No camera found!
2025-11-24 18:43:50,945 - ERROR - ❌ No camera found!
2025-11-24 18:43:51,090 - INFO - Video thread started with source: Camera
2025-11-24 18:43:51,091 - INFO - Video thread started with source: Camera
2025-11-24 18:43:51,091 - ERROR - ❌ No camera found!
2025-11-24 18:43:51,092 - ERROR - ❌ No camera found!
2025-11-24 18:43:51,109 - INFO - Frame 138 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 1
2025-11-24 18:43:51,240 - INFO - Video thread started with source: Camera
2025-11-24 18:43:51,242 - ERROR - ❌ No camera found!
2025-11-24 18:43:51,243 - INFO - Video thread started with source: Camera
2025-11-24 18:43:51,246 - ERROR - ❌ No camera found!
2025-11-24 18:43:51,390 - INFO - Video thread started with source: Camera
2025-11-24 18:43:51,392 - ERROR - ❌ No camera found!
2025-11-24 18:43:51,394 - INFO - Video thread started with source: Camera
2025-11-24 18:43:51,396 - ERROR - ❌ No camera found!
2025-11-24 18:43:51,417 - INFO - Frame 140 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 1
2025-11-24 18:43:51,544 - INFO - Video thread started with source: Camera
2025-11-24 18:43:51,544 - INFO - Video thread started with source: Camera
2025-11-24 18:43:51,545 - ERROR - ❌ No camera found!
2025-11-24 18:43:51,545 - ERROR - ❌ No camera found!
2025-11-24 18:43:51,698 - INFO - Video thread started with source: Camera
2025-11-24 18:43:51,700 - INFO - Video thread started with source: Camera
2025-11-24 18:43:51,701 - ERROR - ❌ No camera found!
2025-11-24 18:43:51,702 - ERROR - ❌ No camera found!
2025-11-24 18:43:51,702 - INFO - Frame 142 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 1
2025-11-24 18:43:51,851 - INFO - Video thread started with source: Camera
2025-11-24 18:43:51,851 - INFO - Video thread started with source: Camera
2025-11-24 18:43:51,852 - ERROR - ❌ No camera found!
2025-11-24 18:43:51,852 - ERROR - ❌ No camera found!
2025-11-24 18:43:52,018 - INFO - Video thread started with source: Camera
2025-11-24 18:43:52,019 - INFO - Video thread started with source: Camera
2025-11-24 18:43:52,020 - ERROR - ❌ No camera found!
2025-11-24 18:43:52,021 - ERROR - ❌ No camera found!
2025-11-24 18:43:52,045 - INFO - Frame 144 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 1
2025-11-24 18:43:52,168 - INFO - Video thread started with source: Camera
2025-11-24 18:43:52,168 - INFO - Video thread started with source: Camera
2025-11-24 18:43:52,169 - ERROR - ❌ No camera found!
2025-11-24 18:43:52,170 - ERROR - ❌ No camera found!
2025-11-24 18:43:52,321 - INFO - Video thread started with source: Camera
2025-11-24 18:43:52,324 - ERROR - ❌ No camera found!
2025-11-24 18:43:52,326 - INFO - Video thread started with source: Camera
2025-11-24 18:43:52,330 - ERROR - ❌ No camera found!
2025-11-24 18:43:52,354 - INFO - Frame 146 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 1
2025-11-24 18:43:52,471 - INFO - Video thread started with source: Camera
2025-11-24 18:43:52,473 - ERROR - ❌ No camera found!
2025-11-24 18:43:52,474 - INFO - Video thread started with source: Camera
2025-11-24 18:43:52,477 - ERROR - ❌ No camera found!
2025-11-24 18:43:52,638 - INFO - Video thread started with source: Camera
2025-11-24 18:43:52,640 - INFO - Video thread started with source: Camera
2025-11-24 18:43:52,641 - ERROR - ❌ No camera found!
2025-11-24 18:43:52,643 - ERROR - ❌ No camera found!
2025-11-24 18:43:52,667 - INFO - Frame 148 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 1
2025-11-24 18:43:52,792 - INFO - Video thread started with source: Camera
2025-11-24 18:43:52,792 - INFO - Video thread started with source: Camera
2025-11-24 18:43:52,793 - ERROR - ❌ No camera found!
2025-11-24 18:43:52,793 - ERROR - ❌ No camera found!
2025-11-24 18:43:52,944 - INFO - Video thread started with source: Camera
2025-11-24 18:43:52,946 - INFO - Video thread started with source: Camera
2025-11-24 18:43:52,946 - ERROR - ❌ No camera found!
2025-11-24 18:43:52,947 - ERROR - ❌ No camera found!
2025-11-24 18:43:53,096 - INFO - Frame 150 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 1
2025-11-24 18:43:53,097 - INFO - Video thread started with source: Camera
2025-11-24 18:43:53,098 - INFO - Video thread started with source: Camera
2025-11-24 18:43:53,099 - ERROR - ❌ No camera found!
2025-11-24 18:43:53,099 - ERROR - ❌ No camera found!
2025-11-24 18:43:53,248 - INFO - Video thread started with source: Camera
2025-11-24 18:43:53,249 - INFO - Video thread started with source: Camera
2025-11-24 18:43:53,249 - ERROR - ❌ No camera found!
2025-11-24 18:43:53,250 - ERROR - ❌ No camera found!
2025-11-24 18:43:53,404 - INFO - Frame 152 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-24 18:43:53,404 - INFO - Video thread started with source: Camera
2025-11-24 18:43:53,404 - INFO - Video thread started with source: Camera
2025-11-24 18:43:53,405 - ERROR - ❌ No camera found!
2025-11-24 18:43:53,405 - ERROR - ❌ No camera found!
2025-11-24 18:43:53,568 - INFO - Video thread started with source: Camera
2025-11-24 18:43:53,569 - ERROR - ❌ No camera found!
2025-11-24 18:43:53,571 - INFO - Video thread started with source: Camera
2025-11-24 18:43:53,574 - ERROR - ❌ No camera found!
2025-11-24 18:43:53,723 - INFO - Frame 154 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 1
2025-11-24 18:43:53,726 - INFO - Video thread started with source: Camera
2025-11-24 18:43:53,727 - ERROR - ❌ No camera found!
2025-11-24 18:43:53,728 - INFO - Video thread started with source: Camera
2025-11-24 18:43:53,729 - ERROR - ❌ No camera found!
2025-11-24 18:43:53,878 - INFO - Video thread started with source: Camera
2025-11-24 18:43:53,879 - ERROR - ❌ No camera found!
2025-11-24 18:43:53,880 - INFO - Video thread started with source: Camera
2025-11-24 18:43:53,881 - ERROR - ❌ No camera found!
2025-11-24 18:43:54,047 - INFO - Video thread started with source: Camera
2025-11-24 18:43:54,047 - INFO - Video thread started with source: Camera
2025-11-24 18:43:54,047 - ERROR - ❌ No camera found!
2025-11-24 18:43:54,048 - ERROR - ❌ No camera found!
2025-11-24 18:43:54,221 - INFO - Frame 156 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-24 18:43:54,221 - INFO - Video thread started with source: Camera
2025-11-24 18:43:54,224 - ERROR - ❌ No camera found!
2025-11-24 18:43:54,224 - INFO - Video thread started with source: Camera
2025-11-24 18:43:54,225 - ERROR - ❌ No camera found!
2025-11-24 18:43:54,391 - INFO - Video thread started with source: Camera
2025-11-24 18:43:54,392 - ERROR - ❌ No camera found!
2025-11-24 18:43:54,427 - INFO - Frame 158 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 1
2025-11-24 18:43:54,503 - INFO - Video thread started with source: Camera
2025-11-24 18:43:54,504 - ERROR - ❌ No camera found!
2025-11-24 18:43:54,536 - INFO - Video thread started with source: Camera
2025-11-24 18:43:54,539 - ERROR - ❌ No camera found!
2025-11-24 18:43:54,651 - INFO - Video thread started with source: Camera
2025-11-24 18:43:54,653 - ERROR - ❌ No camera found!
2025-11-24 18:43:54,654 - INFO - Video thread started with source: Camera
2025-11-24 18:43:54,657 - ERROR - ❌ No camera found!
2025-11-24 18:43:54,683 - INFO - Frame 160 | PERCLOS: 0.00 | Yaw: 6.3° | Alerts: 1
2025-11-24 18:43:54,814 - INFO - Video thread started with source: Camera
2025-11-24 18:43:54,815 - INFO - Video thread started with source: Camera
2025-11-24 18:43:54,815 - ERROR - ❌ No camera found!
2025-11-24 18:43:54,816 - ERROR - ❌ No camera found!
2025-11-24 18:43:54,972 - INFO - Video thread started with source: Camera
2025-11-24 18:43:54,972 - INFO - Video thread started with source: Camera
2025-11-24 18:43:54,973 - ERROR - ❌ No camera found!
2025-11-24 18:43:54,973 - ERROR - ❌ No camera found!
2025-11-24 18:43:55,138 - INFO - Frame 162 | PERCLOS: 0.00 | Yaw: 6.8° | Alerts: 1
2025-11-24 18:43:55,142 - INFO - Video thread started with source: Camera
2025-11-24 18:43:55,142 - INFO - Video thread started with source: Camera
2025-11-24 18:43:55,143 - ERROR - ❌ No camera found!
2025-11-24 18:43:55,144 - ERROR - ❌ No camera found!
2025-11-24 18:43:55,290 - INFO - Video thread started with source: Camera
2025-11-24 18:43:55,290 - INFO - Video thread started with source: Camera
2025-11-24 18:43:55,291 - ERROR - ❌ No camera found!
2025-11-24 18:43:55,291 - ERROR - ❌ No camera found!
2025-11-24 18:43:55,465 - INFO - Frame 164 | PERCLOS: 0.05 | Yaw: 6.7° | Alerts: 1
2025-11-24 18:43:55,469 - INFO - Video thread started with source: Camera
2025-11-24 18:43:55,469 - INFO - Video thread started with source: Camera
2025-11-24 18:43:55,471 - ERROR - ❌ No camera found!
2025-11-24 18:43:55,471 - ERROR - ❌ No camera found!
2025-11-24 18:43:55,654 - INFO - Video thread started with source: Camera
2025-11-24 18:43:55,654 - INFO - Video thread started with source: Camera
2025-11-24 18:43:55,654 - ERROR - ❌ No camera found!
2025-11-24 18:43:55,654 - ERROR - ❌ No camera found!
2025-11-24 18:43:55,691 - INFO - Frame 166 | PERCLOS: 0.00 | Yaw: 6.7° | Alerts: 1
2025-11-24 18:43:55,821 - INFO - Video thread started with source: Camera
2025-11-24 18:43:55,823 - INFO - Video thread started with source: Camera
2025-11-24 18:43:55,823 - ERROR - ❌ No camera found!
2025-11-24 18:43:55,824 - ERROR - ❌ No camera found!
2025-11-24 18:43:55,973 - INFO - Video thread started with source: Camera
2025-11-24 18:43:55,974 - ERROR - ❌ No camera found!
2025-11-24 18:43:55,976 - INFO - Video thread started with source: Camera
2025-11-24 18:43:55,977 - ERROR - ❌ No camera found!
2025-11-24 18:43:56,141 - INFO - Video thread started with source: Camera
2025-11-24 18:43:56,143 - ERROR - ❌ No camera found!
2025-11-24 18:43:56,144 - INFO - Video thread started with source: Camera
2025-11-24 18:43:56,145 - ERROR - ❌ No camera found!
2025-11-24 18:43:56,162 - INFO - Frame 168 | PERCLOS: 0.00 | Yaw: 6.7° | Alerts: 1
2025-11-24 18:43:56,308 - INFO - Video thread started with source: Camera
2025-11-24 18:43:56,311 - INFO - Video thread started with source: Camera
2025-11-24 18:43:56,312 - ERROR - ❌ No camera found!
2025-11-24 18:43:56,312 - ERROR - ❌ No camera found!
2025-11-24 18:43:56,464 - INFO - Video thread started with source: Camera
2025-11-24 18:43:56,464 - INFO - Video thread started with source: Camera
2025-11-24 18:43:56,465 - ERROR - ❌ No camera found!
2025-11-24 18:43:56,467 - ERROR - ❌ No camera found!
2025-11-24 18:43:56,494 - INFO - Frame 170 | PERCLOS: 0.00 | Yaw: 6.4° | Alerts: 1
2025-11-24 18:43:56,622 - INFO - Video thread started with source: Camera
2025-11-24 18:43:56,622 - INFO - Video thread started with source: Camera
2025-11-24 18:43:56,623 - ERROR - ❌ No camera found!
2025-11-24 18:43:56,623 - ERROR - ❌ No camera found!
2025-11-24 18:43:56,766 - INFO - Video thread started with source: Camera
2025-11-24 18:43:56,768 - INFO - Video thread started with source: Camera
2025-11-24 18:43:56,769 - ERROR - ❌ No camera found!
2025-11-24 18:43:56,769 - ERROR - ❌ No camera found!
2025-11-24 18:43:56,796 - INFO - Frame 172 | PERCLOS: 0.00 | Yaw: 6.4° | Alerts: 1
2025-11-24 18:43:56,921 - INFO - Video thread started with source: Camera
2025-11-24 18:43:56,923 - ERROR - ❌ No camera found!
2025-11-24 18:43:56,923 - INFO - Video thread started with source: Camera
2025-11-24 18:43:56,924 - ERROR - ❌ No camera found!
2025-11-24 18:43:57,082 - INFO - Video thread started with source: Camera
2025-11-24 18:43:57,084 - ERROR - ❌ No camera found!
2025-11-24 18:43:57,084 - INFO - Video thread started with source: Camera
2025-11-24 18:43:57,086 - ERROR - ❌ No camera found!
2025-11-24 18:43:57,258 - INFO - Video thread started with source: Camera
2025-11-24 18:43:57,259 - INFO - Video thread started with source: Camera
2025-11-24 18:43:57,260 - ERROR - ❌ No camera found!
2025-11-24 18:43:57,261 - ERROR - ❌ No camera found!
2025-11-24 18:43:57,279 - INFO - Frame 174 | PERCLOS: 0.00 | Yaw: 5.9° | Alerts: 1
2025-11-24 18:43:57,423 - INFO - Video thread started with source: Camera
2025-11-24 18:43:57,424 - ERROR - ❌ No camera found!
2025-11-24 18:43:57,429 - INFO - Video thread started with source: Camera
2025-11-24 18:43:57,430 - ERROR - ❌ No camera found!
2025-11-24 18:43:57,579 - INFO - Video thread started with source: Camera
2025-11-24 18:43:57,579 - INFO - Video thread started with source: Camera
2025-11-24 18:43:57,580 - ERROR - ❌ No camera found!
2025-11-24 18:43:57,581 - ERROR - ❌ No camera found!
2025-11-24 18:43:57,607 - INFO - Frame 176 | PERCLOS: 0.00 | Yaw: 6.0° | Alerts: 1
2025-11-24 18:43:57,736 - INFO - Video thread started with source: Camera
2025-11-24 18:43:57,737 - INFO - Video thread started with source: Camera
2025-11-24 18:43:57,738 - ERROR - ❌ No camera found!
2025-11-24 18:43:57,738 - ERROR - ❌ No camera found!
2025-11-24 18:43:57,916 - INFO - Video thread started with source: Camera
2025-11-24 18:43:57,916 - INFO - Video thread started with source: Camera
2025-11-24 18:43:57,918 - ERROR - ❌ No camera found!
2025-11-24 18:43:57,918 - ERROR - ❌ No camera found!
2025-11-24 18:43:57,949 - INFO - Frame 178 | PERCLOS: 0.00 | Yaw: 5.4° | Alerts: 1
2025-11-24 18:43:58,073 - INFO - Video thread started with source: Camera
2025-11-24 18:43:58,073 - INFO - Video thread started with source: Camera
2025-11-24 18:43:58,073 - ERROR - ❌ No camera found!
2025-11-24 18:43:58,074 - ERROR - ❌ No camera found!
2025-11-24 18:43:58,242 - INFO - Video thread started with source: Camera
2025-11-24 18:43:58,242 - INFO - Video thread started with source: Camera
2025-11-24 18:43:58,243 - ERROR - ❌ No camera found!
2025-11-24 18:43:58,243 - ERROR - ❌ No camera found!
2025-11-24 18:43:58,390 - INFO - Frame 180 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:43:58,391 - INFO - Video thread started with source: Camera
2025-11-24 18:43:58,392 - INFO - Video thread started with source: Camera
2025-11-24 18:43:58,392 - ERROR - ❌ No camera found!
2025-11-24 18:43:58,393 - ERROR - ❌ No camera found!
2025-11-24 18:43:58,536 - INFO - Video thread started with source: Camera
2025-11-24 18:43:58,536 - INFO - Video thread started with source: Camera
2025-11-24 18:43:58,536 - ERROR - ❌ No camera found!
2025-11-24 18:43:58,537 - ERROR - ❌ No camera found!
2025-11-24 18:43:58,575 - INFO - Frame 182 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 1
2025-11-24 18:43:58,685 - INFO - Video thread started with source: Camera
2025-11-24 18:43:58,687 - ERROR - ❌ No camera found!
2025-11-24 18:43:58,688 - INFO - Video thread started with source: Camera
2025-11-24 18:43:58,690 - ERROR - ❌ No camera found!
2025-11-24 18:43:58,837 - INFO - Video thread started with source: Camera
2025-11-24 18:43:58,840 - ERROR - ❌ No camera found!
2025-11-24 18:43:58,840 - INFO - Video thread started with source: Camera
2025-11-24 18:43:58,843 - ERROR - ❌ No camera found!
2025-11-24 18:43:58,863 - INFO - Frame 184 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 18:43:58,987 - INFO - Video thread started with source: Camera
2025-11-24 18:43:58,987 - INFO - Video thread started with source: Camera
2025-11-24 18:43:58,988 - ERROR - ❌ No camera found!
2025-11-24 18:43:58,989 - ERROR - ❌ No camera found!
2025-11-24 18:50:54,485 - INFO - Loading models...
2025-11-24 18:50:54,507 - INFO - ✓ YOLO ONNX loaded
2025-11-24 18:50:54,538 - INFO - ✓ MediaPipe Face Mesh loaded
2025-11-24 18:50:54,545 - INFO - ✓ MediaPipe Pose loaded (for smoke & seatbelt)
2025-11-24 18:50:54,548 - INFO - Video thread started with source: Camera
2025-11-24 18:50:54,552 - INFO - Video thread started with source: Camera
2025-11-24 18:50:54,555 - ERROR - ❌ No camera found!
2025-11-24 18:50:54,713 - INFO - ✓ Camera 0 opened successfully
2025-11-24 18:50:54,719 - INFO - Video thread started with source: Camera
2025-11-24 18:50:54,722 - ERROR - ❌ No camera found!
2025-11-24 18:50:54,863 - INFO - Video thread started with source: Camera
2025-11-24 18:50:54,864 - ERROR - ❌ No camera found!
2025-11-24 18:50:55,007 - INFO - Video thread started with source: Camera
2025-11-24 18:50:55,008 - ERROR - ❌ No camera found!
2025-11-24 18:50:55,131 - INFO - Video thread started with source: Camera
2025-11-24 18:50:55,132 - ERROR - ❌ No camera found!
2025-11-24 18:50:55,274 - INFO - Video thread started with source: Camera
2025-11-24 18:50:55,275 - ERROR - ❌ No camera found!
2025-11-24 18:50:55,432 - INFO - Video thread started with source: Camera
2025-11-24 18:50:55,433 - ERROR - ❌ No camera found!
2025-11-24 18:50:55,449 - INFO - Frame 0 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 1
2025-11-24 18:50:55,573 - INFO - Video thread started with source: Camera
2025-11-24 18:50:55,574 - ERROR - ❌ No camera found!
2025-11-24 18:50:55,723 - INFO - Video thread started with source: Camera
2025-11-24 18:50:55,723 - ERROR - ❌ No camera found!
2025-11-24 18:50:55,724 - INFO - Frame 2 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 1
2025-11-24 18:50:55,865 - INFO - Video thread started with source: Camera
2025-11-24 18:50:55,866 - ERROR - ❌ No camera found!
2025-11-24 18:50:56,014 - INFO - Video thread started with source: Camera
2025-11-24 18:50:56,015 - ERROR - ❌ No camera found!
2025-11-24 18:50:56,036 - INFO - Frame 4 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 1
2025-11-24 18:50:56,166 - INFO - Video thread started with source: Camera
2025-11-24 18:50:56,171 - ERROR - ❌ No camera found!
2025-11-24 18:50:56,190 - INFO - Video thread started with source: Camera
2025-11-24 18:50:56,191 - ERROR - ❌ No camera found!
2025-11-24 18:50:56,417 - INFO - Video thread started with source: Camera
2025-11-24 18:50:56,423 - INFO - Video thread started with source: Camera
2025-11-24 18:50:56,424 - ERROR - ❌ No camera found!
2025-11-24 18:50:56,426 - ERROR - ❌ No camera found!
2025-11-24 18:50:56,611 - INFO - Video thread started with source: Camera
2025-11-24 18:50:56,612 - INFO - Video thread started with source: Camera
2025-11-24 18:50:56,613 - ERROR - ❌ No camera found!
2025-11-24 18:50:56,613 - ERROR - ❌ No camera found!
2025-11-24 18:50:56,623 - INFO - Frame 6 | PERCLOS: 0.00 | Yaw: -0.8° | Alerts: 1
2025-11-24 18:50:56,799 - INFO - Video thread started with source: Camera
2025-11-24 18:50:56,800 - ERROR - ❌ No camera found!
2025-11-24 18:50:56,801 - INFO - Video thread started with source: Camera
2025-11-24 18:50:56,808 - ERROR - ❌ No camera found!
2025-11-24 18:50:56,985 - INFO - Video thread started with source: Camera
2025-11-24 18:50:56,987 - INFO - Video thread started with source: Camera
2025-11-24 18:50:56,988 - ERROR - ❌ No camera found!
2025-11-24 18:50:56,991 - ERROR - ❌ No camera found!
2025-11-24 18:50:57,013 - INFO - Frame 8 | PERCLOS: 0.00 | Yaw: -0.3° | Alerts: 1
2025-11-24 18:50:57,182 - INFO - Video thread started with source: Camera
2025-11-24 18:50:57,186 - INFO - Video thread started with source: Camera
2025-11-24 18:50:57,186 - ERROR - ❌ No camera found!
2025-11-24 18:50:57,187 - ERROR - ❌ No camera found!
2025-11-24 18:50:57,389 - INFO - Video thread started with source: Camera
2025-11-24 18:50:57,393 - INFO - Video thread started with source: Camera
2025-11-24 18:50:57,394 - ERROR - ❌ No camera found!
2025-11-24 18:50:57,395 - ERROR - ❌ No camera found!
2025-11-24 18:50:57,415 - INFO - Frame 10 | PERCLOS: 0.00 | Yaw: -0.3° | Alerts: 1
2025-11-24 18:50:57,589 - INFO - Video thread started with source: Camera
2025-11-24 18:50:57,589 - INFO - Video thread started with source: Camera
2025-11-24 18:50:57,591 - ERROR - ❌ No camera found!
2025-11-24 18:50:57,591 - ERROR - ❌ No camera found!
2025-11-24 18:50:57,845 - INFO - Video thread started with source: Camera
2025-11-24 18:50:57,847 - ERROR - ❌ No camera found!
2025-11-24 18:50:57,852 - INFO - Video thread started with source: Camera
2025-11-24 18:50:57,854 - ERROR - ❌ No camera found!
2025-11-24 18:50:58,074 - INFO - Frame 12 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 1
2025-11-24 18:50:58,078 - INFO - Video thread started with source: Camera
2025-11-24 18:50:58,080 - INFO - Video thread started with source: Camera
2025-11-24 18:50:58,082 - ERROR - ❌ No camera found!
2025-11-24 18:50:58,082 - ERROR - ❌ No camera found!
2025-11-24 18:50:58,284 - INFO - Video thread started with source: Camera
2025-11-24 18:50:58,285 - INFO - Video thread started with source: Camera
2025-11-24 18:50:58,286 - ERROR - ❌ No camera found!
2025-11-24 18:50:58,288 - ERROR - ❌ No camera found!
2025-11-24 18:50:58,482 - INFO - Video thread started with source: Camera
2025-11-24 18:50:58,484 - ERROR - ❌ No camera found!
2025-11-24 18:50:58,484 - INFO - Video thread started with source: Camera
2025-11-24 18:50:58,486 - ERROR - ❌ No camera found!
2025-11-24 18:50:58,488 - INFO - Frame 14 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 1
2025-11-24 18:50:58,685 - INFO - Video thread started with source: Camera
2025-11-24 18:50:58,685 - INFO - Video thread started with source: Camera
2025-11-24 18:50:58,686 - ERROR - ❌ No camera found!
2025-11-24 18:50:58,688 - ERROR - ❌ No camera found!
2025-11-24 18:50:58,880 - INFO - Video thread started with source: Camera
2025-11-24 18:50:58,880 - INFO - Video thread started with source: Camera
2025-11-24 18:50:58,884 - ERROR - ❌ No camera found!
2025-11-24 18:50:58,887 - ERROR - ❌ No camera found!
2025-11-24 18:50:58,914 - INFO - Frame 16 | PERCLOS: 0.00 | Yaw: -0.3° | Alerts: 1
2025-11-24 18:50:59,104 - INFO - Video thread started with source: Camera
2025-11-24 18:50:59,109 - INFO - Video thread started with source: Camera
2025-11-24 18:50:59,109 - ERROR - ❌ No camera found!
2025-11-24 18:50:59,109 - ERROR - ❌ No camera found!
2025-11-24 18:50:59,340 - INFO - Video thread started with source: Camera
2025-11-24 18:50:59,341 - ERROR - ❌ No camera found!
2025-11-24 18:50:59,341 - INFO - Video thread started with source: Camera
2025-11-24 18:50:59,341 - ERROR - ❌ No camera found!
2025-11-24 18:50:59,535 - INFO - Frame 18 | PERCLOS: 0.00 | Yaw: -0.2° | Alerts: 1
2025-11-24 18:50:59,540 - INFO - Video thread started with source: Camera
2025-11-24 18:50:59,542 - INFO - Video thread started with source: Camera
2025-11-24 18:50:59,544 - ERROR - ❌ No camera found!
2025-11-24 18:50:59,545 - ERROR - ❌ No camera found!
2025-11-24 18:50:59,766 - INFO - Video thread started with source: Camera
2025-11-24 18:50:59,768 - INFO - Video thread started with source: Camera
2025-11-24 18:50:59,768 - ERROR - ❌ No camera found!
2025-11-24 18:50:59,771 - ERROR - ❌ No camera found!
2025-11-24 18:50:59,972 - INFO - Video thread started with source: Camera
2025-11-24 18:50:59,974 - ERROR - ❌ No camera found!
2025-11-24 18:50:59,974 - INFO - Video thread started with source: Camera
2025-11-24 18:50:59,976 - INFO - Frame 20 | PERCLOS: 0.00 | Yaw: -0.0° | Alerts: 1
2025-11-24 18:50:59,976 - ERROR - ❌ No camera found!
2025-11-24 18:51:00,198 - ERROR - ❌ No camera found!
2025-11-24 18:51:00,261 - INFO - Video thread started with source: Camera
2025-11-24 18:51:00,417 - INFO - Video thread started with source: Camera
2025-11-24 18:51:00,418 - ERROR - ❌ No camera found!
2025-11-24 18:51:00,420 - INFO - Frame 22 | PERCLOS: 0.00 | Yaw: -0.1° | Alerts: 1
2025-11-24 18:51:00,573 - INFO - Video thread started with source: Camera
2025-11-24 18:51:00,575 - ERROR - ❌ No camera found!
2025-11-24 18:51:00,719 - INFO - Video thread started with source: Camera
2025-11-24 18:51:00,720 - ERROR - ❌ No camera found!
2025-11-24 18:51:00,867 - INFO - Frame 24 | PERCLOS: 0.00 | Yaw: -0.2° | Alerts: 1
2025-11-24 18:51:00,874 - INFO - Video thread started with source: Camera
2025-11-24 18:51:00,875 - ERROR - ❌ No camera found!
2025-11-24 18:51:01,007 - INFO - Video thread started with source: Camera
2025-11-24 18:51:01,007 - ERROR - ❌ No camera found!
2025-11-24 18:51:01,043 - INFO - Frame 26 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 1
2025-11-24 18:51:01,154 - INFO - Video thread started with source: Camera
2025-11-24 18:51:01,157 - ERROR - ❌ No camera found!
2025-11-24 18:51:01,319 - INFO - Video thread started with source: Camera
2025-11-24 18:51:01,321 - ERROR - ❌ No camera found!
2025-11-24 18:51:01,321 - INFO - Frame 28 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 1
2025-11-24 18:51:01,474 - INFO - Video thread started with source: Camera
2025-11-24 18:51:01,475 - ERROR - ❌ No camera found!
2025-11-24 18:51:01,627 - INFO - Video thread started with source: Camera
2025-11-24 18:51:01,628 - ERROR - ❌ No camera found!
2025-11-24 18:51:01,644 - INFO - Frame 30 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 1
2025-11-24 18:51:01,777 - INFO - Video thread started with source: Camera
2025-11-24 18:51:01,778 - ERROR - ❌ No camera found!
2025-11-24 18:51:01,932 - INFO - Video thread started with source: Camera
2025-11-24 18:51:01,937 - INFO - Frame 32 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 1
2025-11-24 18:51:01,937 - ERROR - ❌ No camera found!
2025-11-24 18:51:02,078 - INFO - Video thread started with source: Camera
2025-11-24 18:51:02,079 - ERROR - ❌ No camera found!
2025-11-24 18:51:02,229 - INFO - Video thread started with source: Camera
2025-11-24 18:51:02,234 - ERROR - ❌ No camera found!
2025-11-24 18:51:02,252 - INFO - Frame 34 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 1
2025-11-24 18:51:02,382 - INFO - Video thread started with source: Camera
2025-11-24 18:51:02,385 - ERROR - ❌ No camera found!
2025-11-24 18:51:02,534 - INFO - Video thread started with source: Camera
2025-11-24 18:51:02,536 - ERROR - ❌ No camera found!
2025-11-24 18:51:02,682 - INFO - Video thread started with source: Camera
2025-11-24 18:51:02,682 - ERROR - ❌ No camera found!
2025-11-24 18:51:02,700 - INFO - Frame 36 | PERCLOS: 0.11 | Yaw: 0.1° | Alerts: 1
2025-11-24 18:51:02,825 - INFO - Video thread started with source: Camera
2025-11-24 18:51:02,826 - ERROR - ❌ No camera found!
2025-11-24 18:51:02,983 - INFO - Video thread started with source: Camera
2025-11-24 18:51:02,986 - ERROR - ❌ No camera found!
2025-11-24 18:51:03,010 - INFO - Frame 38 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 1
2025-11-24 18:51:03,144 - INFO - Video thread started with source: Camera
2025-11-24 18:51:03,145 - ERROR - ❌ No camera found!
2025-11-24 18:51:03,314 - INFO - Video thread started with source: Camera
2025-11-24 18:51:03,318 - ERROR - ❌ No camera found!
2025-11-24 18:51:03,341 - INFO - Frame 40 | PERCLOS: 0.00 | Yaw: -0.9° | Alerts: 1
2025-11-24 18:51:03,470 - INFO - Video thread started with source: Camera
2025-11-24 18:51:03,475 - ERROR - ❌ No camera found!
2025-11-24 18:51:03,638 - INFO - Video thread started with source: Camera
2025-11-24 18:51:03,640 - ERROR - ❌ No camera found!
2025-11-24 18:51:03,794 - INFO - Frame 42 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 1
2025-11-24 18:51:03,797 - INFO - Video thread started with source: Camera
2025-11-24 18:51:03,802 - ERROR - ❌ No camera found!
2025-11-24 18:51:03,959 - INFO - Video thread started with source: Camera
2025-11-24 18:51:03,960 - ERROR - ❌ No camera found!
2025-11-24 18:51:04,116 - INFO - Video thread started with source: Camera
2025-11-24 18:51:04,117 - ERROR - ❌ No camera found!
2025-11-24 18:51:04,140 - INFO - Frame 44 | PERCLOS: 0.00 | Yaw: -0.8° | Alerts: 1
2025-11-24 18:51:04,267 - INFO - Video thread started with source: Camera
2025-11-24 18:51:04,271 - ERROR - ❌ No camera found!
2025-11-24 18:51:04,423 - INFO - Video thread started with source: Camera
2025-11-24 18:51:04,424 - ERROR - ❌ No camera found!
2025-11-24 18:51:04,446 - INFO - Frame 46 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 1
2025-11-24 18:51:04,577 - INFO - Video thread started with source: Camera
2025-11-24 18:51:04,578 - ERROR - ❌ No camera found!
2025-11-24 18:51:04,729 - INFO - Video thread started with source: Camera
2025-11-24 18:51:04,733 - ERROR - ❌ No camera found!
2025-11-24 18:51:04,900 - INFO - Video thread started with source: Camera
2025-11-24 18:51:04,901 - ERROR - ❌ No camera found!
2025-11-24 18:51:04,917 - INFO - Frame 48 | PERCLOS: 0.00 | Yaw: 8.2° | Alerts: 1
2025-11-24 18:51:05,200 - INFO - Frame 50 | PERCLOS: 0.00 | Yaw: 8.2° | Alerts: 1
2025-11-24 18:51:05,313 - INFO - Video thread started with source: Camera
2025-11-24 18:51:05,315 - ERROR - ❌ No camera found!
2025-11-24 18:51:05,436 - INFO - Video thread started with source: Camera
2025-11-24 18:51:05,439 - ERROR - ❌ No camera found!
2025-11-24 18:51:05,467 - INFO - Frame 52 | PERCLOS: 0.00 | Yaw: 9.2° | Alerts: 1
2025-11-24 18:51:05,596 - INFO - Video thread started with source: Camera
2025-11-24 18:51:05,596 - ERROR - ❌ No camera found!
2025-11-24 18:51:05,744 - INFO - Video thread started with source: Camera
2025-11-24 18:51:05,744 - ERROR - ❌ No camera found!
2025-11-24 18:51:05,894 - INFO - Frame 54 | PERCLOS: 0.00 | Yaw: 8.5° | Alerts: 1
2025-11-24 18:51:05,899 - INFO - Video thread started with source: Camera
2025-11-24 18:51:05,900 - ERROR - ❌ No camera found!
2025-11-24 18:51:06,028 - INFO - Video thread started with source: Camera
2025-11-24 18:51:06,030 - ERROR - ❌ No camera found!
2025-11-24 18:51:06,178 - INFO - Video thread started with source: Camera
2025-11-24 18:51:06,179 - ERROR - ❌ No camera found!
2025-11-24 18:51:06,209 - INFO - Frame 56 | PERCLOS: 0.00 | Yaw: 8.3° | Alerts: 1
2025-11-24 18:51:06,352 - INFO - Video thread started with source: Camera
2025-11-24 18:51:06,356 - ERROR - ❌ No camera found!
2025-11-24 18:51:06,502 - INFO - Video thread started with source: Camera
2025-11-24 18:51:06,507 - ERROR - ❌ No camera found!
2025-11-24 18:51:06,528 - INFO - Frame 58 | PERCLOS: 0.00 | Yaw: 9.1° | Alerts: 1
2025-11-24 18:51:06,654 - INFO - Video thread started with source: Camera
2025-11-24 18:51:06,656 - ERROR - ❌ No camera found!
2025-11-24 18:51:06,809 - INFO - Video thread started with source: Camera
2025-11-24 18:51:06,813 - ERROR - ❌ No camera found!
2025-11-24 18:51:06,965 - INFO - Video thread started with source: Camera
2025-11-24 18:51:06,966 - ERROR - ❌ No camera found!
2025-11-24 18:51:06,982 - INFO - Frame 60 | PERCLOS: 0.00 | Yaw: 9.6° | Alerts: 1
2025-11-24 18:51:07,120 - INFO - Video thread started with source: Camera
2025-11-24 18:51:07,123 - ERROR - ❌ No camera found!
2025-11-24 18:51:07,264 - INFO - Video thread started with source: Camera
2025-11-24 18:51:07,265 - ERROR - ❌ No camera found!
2025-11-24 18:51:07,296 - INFO - Frame 62 | PERCLOS: 0.00 | Yaw: 8.7° | Alerts: 1
2025-11-24 18:51:07,417 - INFO - Video thread started with source: Camera
2025-11-24 18:51:07,419 - ERROR - ❌ No camera found!
2025-11-24 18:51:07,562 - INFO - Video thread started with source: Camera
2025-11-24 18:51:07,568 - ERROR - ❌ No camera found!
2025-11-24 18:51:07,585 - INFO - Frame 64 | PERCLOS: 0.00 | Yaw: 8.4° | Alerts: 1
2025-11-24 18:51:07,716 - INFO - Video thread started with source: Camera
2025-11-24 18:51:07,721 - ERROR - ❌ No camera found!
2025-11-24 18:51:07,874 - INFO - Video thread started with source: Camera
2025-11-24 18:51:07,876 - ERROR - ❌ No camera found!
2025-11-24 18:51:08,034 - INFO - Video thread started with source: Camera
2025-11-24 18:51:08,035 - ERROR - ❌ No camera found!
2025-11-24 18:51:08,053 - INFO - Frame 66 | PERCLOS: 0.00 | Yaw: 8.1° | Alerts: 1
2025-11-24 18:51:08,178 - INFO - Video thread started with source: Camera
2025-11-24 18:51:08,180 - ERROR - ❌ No camera found!
2025-11-24 18:51:08,336 - INFO - Video thread started with source: Camera
2025-11-24 18:51:08,343 - ERROR - ❌ No camera found!
2025-11-24 18:51:08,365 - INFO - Frame 68 | PERCLOS: 0.00 | Yaw: 7.6° | Alerts: 1
2025-11-24 18:51:08,499 - INFO - Video thread started with source: Camera
2025-11-24 18:51:08,501 - ERROR - ❌ No camera found!
2025-11-24 18:51:08,657 - INFO - Video thread started with source: Camera
2025-11-24 18:51:08,658 - ERROR - ❌ No camera found!
2025-11-24 18:51:08,686 - INFO - Frame 70 | PERCLOS: 0.00 | Yaw: 7.7° | Alerts: 1
2025-11-24 18:51:08,825 - INFO - Video thread started with source: Camera
2025-11-24 18:51:08,829 - ERROR - ❌ No camera found!
2025-11-24 18:51:08,986 - INFO - Video thread started with source: Camera
2025-11-24 18:51:08,992 - ERROR - ❌ No camera found!
2025-11-24 18:51:09,147 - INFO - Video thread started with source: Camera
2025-11-24 18:51:09,148 - ERROR - ❌ No camera found!
2025-11-24 18:51:09,164 - INFO - Frame 72 | PERCLOS: 0.00 | Yaw: 7.3° | Alerts: 1
2025-11-24 18:51:09,302 - INFO - Video thread started with source: Camera
2025-11-24 18:51:09,304 - ERROR - ❌ No camera found!
2025-11-24 18:51:09,459 - INFO - Video thread started with source: Camera
2025-11-24 18:51:09,461 - ERROR - ❌ No camera found!
2025-11-24 18:51:09,486 - INFO - Frame 74 | PERCLOS: 0.00 | Yaw: 7.2° | Alerts: 1
2025-11-24 18:51:09,617 - INFO - Video thread started with source: Camera
2025-11-24 18:51:09,619 - ERROR - ❌ No camera found!
2025-11-24 18:51:09,779 - INFO - Video thread started with source: Camera
2025-11-24 18:51:09,781 - ERROR - ❌ No camera found!
2025-11-24 18:51:09,814 - INFO - Frame 76 | PERCLOS: 0.00 | Yaw: 7.8° | Alerts: 1
2025-11-24 18:51:10,175 - INFO - Video thread started with source: Camera
2025-11-24 18:51:10,177 - ERROR - ❌ No camera found!
2025-11-24 18:51:10,190 - INFO - Frame 78 | PERCLOS: 0.00 | Yaw: 8.6° | Alerts: 1
2025-11-24 18:51:10,339 - INFO - Video thread started with source: Camera
2025-11-24 18:51:10,340 - ERROR - ❌ No camera found!
2025-11-24 18:51:10,498 - INFO - Video thread started with source: Camera
2025-11-24 18:51:10,498 - INFO - Frame 80 | PERCLOS: 0.00 | Yaw: 8.5° | Alerts: 1
2025-11-24 18:51:10,500 - ERROR - ❌ No camera found!
2025-11-24 18:51:10,636 - INFO - Video thread started with source: Camera
2025-11-24 18:51:10,640 - ERROR - ❌ No camera found!
2025-11-24 18:51:10,672 - INFO - Frame 82 | PERCLOS: 0.00 | Yaw: 6.7° | Alerts: 1
2025-11-24 18:51:10,786 - INFO - Video thread started with source: Camera
2025-11-24 18:51:10,790 - ERROR - ❌ No camera found!
2025-11-24 18:51:10,940 - INFO - Video thread started with source: Camera
2025-11-24 18:51:10,941 - ERROR - ❌ No camera found!
2025-11-24 18:51:11,095 - INFO - Video thread started with source: Camera
2025-11-24 18:51:11,097 - ERROR - ❌ No camera found!
2025-11-24 18:51:11,114 - INFO - Frame 84 | PERCLOS: 0.00 | Yaw: 4.7° | Alerts: 1
2025-11-24 18:51:11,266 - INFO - Video thread started with source: Camera
2025-11-24 18:51:11,268 - ERROR - ❌ No camera found!
2025-11-24 18:51:11,435 - INFO - Video thread started with source: Camera
2025-11-24 18:51:11,439 - ERROR - ❌ No camera found!
2025-11-24 18:51:11,458 - INFO - Frame 86 | PERCLOS: 0.00 | Yaw: 4.1° | Alerts: 1
2025-11-24 18:51:11,601 - INFO - Video thread started with source: Camera
2025-11-24 18:51:11,606 - ERROR - ❌ No camera found!
2025-11-24 18:51:11,756 - INFO - Video thread started with source: Camera
2025-11-24 18:51:11,757 - ERROR - ❌ No camera found!
2025-11-24 18:51:11,781 - INFO - Frame 88 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 18:51:11,910 - INFO - Video thread started with source: Camera
2025-11-24 18:51:11,911 - ERROR - ❌ No camera found!
2025-11-24 18:51:12,075 - INFO - Video thread started with source: Camera
2025-11-24 18:51:12,078 - ERROR - ❌ No camera found!
2025-11-24 18:51:12,226 - INFO - Video thread started with source: Camera
2025-11-24 18:51:12,228 - ERROR - ❌ No camera found!
2025-11-24 18:51:12,246 - INFO - Frame 90 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 1
2025-11-24 18:51:12,422 - INFO - Video thread started with source: Camera
2025-11-24 18:51:12,425 - ERROR - ❌ No camera found!
2025-11-24 18:51:12,570 - INFO - Video thread started with source: Camera
2025-11-24 18:51:12,574 - ERROR - ❌ No camera found!
2025-11-24 18:51:12,595 - INFO - Frame 92 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:51:12,729 - INFO - Video thread started with source: Camera
2025-11-24 18:51:12,730 - ERROR - ❌ No camera found!
2025-11-24 18:51:12,876 - INFO - Video thread started with source: Camera
2025-11-24 18:51:12,877 - ERROR - ❌ No camera found!
2025-11-24 18:51:12,903 - INFO - Frame 94 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-24 18:51:13,036 - INFO - Video thread started with source: Camera
2025-11-24 18:51:13,038 - ERROR - ❌ No camera found!
2025-11-24 18:51:13,190 - INFO - Video thread started with source: Camera
2025-11-24 18:51:13,193 - ERROR - ❌ No camera found!
2025-11-24 18:51:13,345 - INFO - Video thread started with source: Camera
2025-11-24 18:51:13,345 - ERROR - ❌ No camera found!
2025-11-24 18:51:13,360 - INFO - Frame 96 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 1
2025-11-24 18:51:13,501 - INFO - Video thread started with source: Camera
2025-11-24 18:51:13,502 - ERROR - ❌ No camera found!
2025-11-24 18:51:13,662 - INFO - Video thread started with source: Camera
2025-11-24 18:51:13,663 - INFO - Frame 98 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 1
2025-11-24 18:51:13,663 - ERROR - ❌ No camera found!
2025-11-24 18:51:13,816 - INFO - Video thread started with source: Camera
2025-11-24 18:51:13,818 - ERROR - ❌ No camera found!
2025-11-24 18:51:13,963 - INFO - Frame 100 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 1
2025-11-24 18:51:13,963 - INFO - Video thread started with source: Camera
2025-11-24 18:51:13,964 - ERROR - ❌ No camera found!
2025-11-24 18:51:14,112 - INFO - Video thread started with source: Camera
2025-11-24 18:51:14,113 - ERROR - ❌ No camera found!
2025-11-24 18:51:14,277 - INFO - Video thread started with source: Camera
2025-11-24 18:51:14,278 - ERROR - ❌ No camera found!
2025-11-24 18:51:14,293 - INFO - Frame 102 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 1
2025-11-24 18:51:14,428 - INFO - Video thread started with source: Camera
2025-11-24 18:51:14,431 - ERROR - ❌ No camera found!
2025-11-24 18:51:14,570 - INFO - Video thread started with source: Camera
2025-11-24 18:51:14,571 - INFO - Frame 104 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 1
2025-11-24 18:51:14,572 - ERROR - ❌ No camera found!
2025-11-24 18:51:14,723 - INFO - Video thread started with source: Camera
2025-11-24 18:51:14,728 - ERROR - ❌ No camera found!
2025-11-24 18:51:14,758 - INFO - Frame 106 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 1
2025-11-24 18:51:14,874 - INFO - Video thread started with source: Camera
2025-11-24 18:51:14,875 - ERROR - ❌ No camera found!
2025-11-24 18:51:15,023 - INFO - Video thread started with source: Camera
2025-11-24 18:51:15,027 - ERROR - ❌ No camera found!
2025-11-24 18:51:15,173 - INFO - Video thread started with source: Camera
2025-11-24 18:51:15,178 - ERROR - ❌ No camera found!
2025-11-24 18:51:15,199 - INFO - Frame 108 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 1
2025-11-24 18:51:15,323 - INFO - Video thread started with source: Camera
2025-11-24 18:51:15,324 - ERROR - ❌ No camera found!
2025-11-24 18:51:15,475 - INFO - Video thread started with source: Camera
2025-11-24 18:51:15,476 - ERROR - ❌ No camera found!
2025-11-24 18:51:15,502 - INFO - Frame 110 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 1
2025-11-24 18:51:15,631 - INFO - Video thread started with source: Camera
2025-11-24 18:51:15,632 - ERROR - ❌ No camera found!
2025-11-24 18:51:15,796 - INFO - Video thread started with source: Camera
2025-11-24 18:51:15,797 - ERROR - ❌ No camera found!
2025-11-24 18:51:15,815 - INFO - Frame 112 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 1
2025-11-24 18:51:15,946 - INFO - Video thread started with source: Camera
2025-11-24 18:51:15,948 - ERROR - ❌ No camera found!
2025-11-24 18:51:16,100 - INFO - Video thread started with source: Camera
2025-11-24 18:51:16,104 - ERROR - ❌ No camera found!
2025-11-24 18:51:16,254 - INFO - Video thread started with source: Camera
2025-11-24 18:51:16,258 - ERROR - ❌ No camera found!
2025-11-24 18:51:16,274 - INFO - Frame 114 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 1
2025-11-24 18:51:16,412 - INFO - Video thread started with source: Camera
2025-11-24 18:51:16,415 - ERROR - ❌ No camera found!
2025-11-24 18:51:16,619 - INFO - Frame 116 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 1
2025-11-24 18:51:16,823 - INFO - Frame 118 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 1
2025-11-24 18:51:17,111 - INFO - Frame 120 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 1
2025-11-24 18:51:17,322 - INFO - Frame 122 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 1
2025-11-24 18:51:17,518 - INFO - Frame 124 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 1
2025-11-24 18:51:17,821 - INFO - Frame 126 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 1
2025-11-24 18:51:18,026 - INFO - Frame 128 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-24 18:51:18,232 - INFO - Frame 130 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-24 18:51:18,515 - INFO - Frame 132 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 1
2025-11-24 18:51:18,713 - INFO - Frame 134 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-24 18:51:18,902 - INFO - Frame 136 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 1
2025-11-24 18:51:19,192 - INFO - Frame 138 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 1
2025-11-24 18:51:19,390 - INFO - Frame 140 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 1
2025-11-24 18:51:19,585 - INFO - Frame 142 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 1
2025-11-24 18:51:19,855 - INFO - Frame 144 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 1
2025-11-24 18:51:20,058 - INFO - Frame 146 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-24 18:51:20,261 - INFO - Frame 148 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-24 18:51:20,576 - INFO - Frame 150 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-24 18:51:20,768 - INFO - Frame 152 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 1
2025-11-24 18:51:20,959 - INFO - Frame 154 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 1
2025-11-24 18:51:21,223 - INFO - Frame 156 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 18:51:21,408 - INFO - Frame 158 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 1
2025-11-24 18:51:21,605 - INFO - Frame 160 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 1
2025-11-24 18:51:21,870 - INFO - Frame 162 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 1
2025-11-24 18:51:22,079 - INFO - Frame 164 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 18:51:22,282 - INFO - Frame 166 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:51:22,625 - INFO - Frame 168 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 18:51:22,853 - INFO - Frame 170 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 18:51:23,041 - INFO - Frame 172 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 18:51:23,349 - INFO - Frame 174 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 1
2025-11-24 18:51:23,557 - INFO - Frame 176 | PERCLOS: 0.00 | Yaw: 2.4° | Alerts: 1
2025-11-24 18:51:23,776 - INFO - Frame 178 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:51:24,068 - INFO - Frame 180 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-24 18:51:24,326 - INFO - Frame 182 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:51:24,542 - INFO - Frame 184 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 1
2025-11-24 18:51:24,878 - INFO - Frame 186 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 1
2025-11-24 18:51:25,125 - INFO - Frame 188 | PERCLOS: 0.00 | Yaw: 2.6° | Alerts: 1
2025-11-24 18:51:25,346 - INFO - Frame 190 | PERCLOS: 0.14 | Yaw: 3.2° | Alerts: 1
2025-11-24 18:51:25,675 - INFO - Frame 192 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-24 18:51:25,914 - INFO - Frame 194 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-24 18:51:26,159 - INFO - Frame 196 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-24 18:51:26,477 - INFO - Frame 198 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 1
2025-11-24 18:51:26,700 - INFO - Frame 200 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-24 18:51:26,914 - INFO - Frame 202 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 1
2025-11-24 18:51:27,237 - INFO - Frame 204 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 1
2025-11-24 18:51:27,448 - INFO - Frame 206 | PERCLOS: 0.00 | Yaw: 4.9° | Alerts: 1
2025-11-24 18:51:27,655 - INFO - Frame 208 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 1
2025-11-24 18:51:27,941 - INFO - Frame 210 | PERCLOS: 0.00 | Yaw: 5.2° | Alerts: 1
2025-11-24 18:51:28,153 - INFO - Frame 212 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-24 18:51:28,346 - INFO - Frame 214 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-24 18:51:28,623 - INFO - Frame 216 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-24 18:51:28,818 - INFO - Frame 218 | PERCLOS: 0.00 | Yaw: 5.4° | Alerts: 1
2025-11-24 18:51:29,000 - INFO - Frame 220 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-24 18:51:29,274 - INFO - Frame 222 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 1
2025-11-24 18:51:29,460 - INFO - Frame 224 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 1
2025-11-24 18:51:29,644 - INFO - Frame 226 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-24 18:51:29,906 - INFO - Frame 228 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 1
2025-11-24 18:51:30,099 - INFO - Frame 230 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-24 18:51:30,279 - INFO - Frame 232 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 1
2025-11-24 18:51:30,558 - INFO - Frame 234 | PERCLOS: 0.00 | Yaw: 5.8° | Alerts: 1
2025-11-24 18:51:30,761 - INFO - Frame 236 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-24 18:51:30,953 - INFO - Frame 238 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-24 18:51:31,235 - INFO - Frame 240 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 1
2025-11-24 18:51:31,433 - INFO - Frame 242 | PERCLOS: 0.47 | Yaw: 6.6° | Alerts: 2
2025-11-24 18:51:31,634 - INFO - Frame 244 | PERCLOS: 0.56 | Yaw: 7.4° | Alerts: 2
2025-11-24 18:51:31,924 - INFO - Frame 246 | PERCLOS: 0.60 | Yaw: 6.8° | Alerts: 2
2025-11-24 18:51:32,124 - INFO - Frame 248 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-24 18:51:32,314 - INFO - Frame 250 | PERCLOS: 0.00 | Yaw: 2.5° | Alerts: 1
2025-11-24 18:51:32,584 - INFO - Frame 252 | PERCLOS: 0.00 | Yaw: 0.5° | Alerts: 1
2025-11-24 18:51:32,788 - INFO - Frame 254 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 1
2025-11-24 18:51:32,982 - INFO - Frame 256 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 1
2025-11-24 18:51:33,265 - INFO - Frame 258 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 1
2025-11-24 18:51:33,476 - INFO - Frame 260 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 1
2025-11-24 18:51:33,665 - INFO - Frame 262 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 1
2025-11-24 18:51:33,947 - INFO - Frame 264 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 1
2025-11-24 18:51:34,139 - INFO - Frame 266 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 1
2025-11-24 18:51:34,335 - INFO - Frame 268 | PERCLOS: 0.74 | Yaw: 2.4° | Alerts: 2
2025-11-25 09:42:56,772 - INFO - Loading models...
2025-11-25 09:42:56,794 - INFO - ✓ YOLO ONNX loaded
2025-11-25 09:42:56,834 - INFO - ✓ MediaPipe Face Mesh loaded
2025-11-25 09:42:56,840 - INFO - ✓ MediaPipe Pose loaded (for smoke & seatbelt)
2025-11-25 09:42:56,844 - INFO - Video thread started with source: Camera
2025-11-25 09:42:56,851 - INFO - Video thread started with source: Camera
2025-11-25 09:42:56,859 - ERROR - ❌ No camera found!
2025-11-25 09:42:56,965 - INFO - ✓ Camera 0 opened successfully
2025-11-25 09:42:57,033 - INFO - Video thread started with source: Camera
2025-11-25 09:42:57,034 - ERROR - ❌ No camera found!
2025-11-25 09:42:57,184 - INFO - Video thread started with source: Camera
2025-11-25 09:42:57,184 - ERROR - ❌ No camera found!
2025-11-25 09:42:57,320 - INFO - Video thread started with source: Camera
2025-11-25 09:42:57,320 - INFO - Frame 0 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:42:57,321 - ERROR - ❌ No camera found!
2025-11-25 09:42:57,444 - INFO - Video thread started with source: Camera
2025-11-25 09:42:57,446 - ERROR - ❌ No camera found!
2025-11-25 09:42:57,574 - INFO - Frame 2 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:42:57,579 - INFO - Video thread started with source: Camera
2025-11-25 09:42:57,582 - ERROR - ❌ No camera found!
2025-11-25 09:42:57,708 - INFO - Video thread started with source: Camera
2025-11-25 09:42:57,711 - INFO - Frame 4 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:42:57,711 - ERROR - ❌ No camera found!
2025-11-25 09:42:57,835 - INFO - Video thread started with source: Camera
2025-11-25 09:42:57,838 - ERROR - ❌ No camera found!
2025-11-25 09:42:57,871 - INFO - Frame 6 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:42:57,970 - INFO - Video thread started with source: Camera
2025-11-25 09:42:57,973 - ERROR - ❌ No camera found!
2025-11-25 09:42:58,105 - INFO - Frame 8 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:42:58,106 - INFO - Video thread started with source: Camera
2025-11-25 09:42:58,106 - ERROR - ❌ No camera found!
2025-11-25 09:42:58,262 - INFO - Video thread started with source: Camera
2025-11-25 09:42:58,263 - ERROR - ❌ No camera found!
2025-11-25 09:42:58,299 - INFO - Frame 10 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:42:58,414 - INFO - Video thread started with source: Camera
2025-11-25 09:42:58,416 - ERROR - ❌ No camera found!
2025-11-25 09:42:58,556 - INFO - Video thread started with source: Camera
2025-11-25 09:42:58,559 - INFO - Frame 12 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:42:58,559 - ERROR - ❌ No camera found!
2025-11-25 09:42:58,705 - INFO - Frame 14 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:42:58,709 - INFO - Video thread started with source: Camera
2025-11-25 09:42:58,710 - ERROR - ❌ No camera found!
2025-11-25 09:42:58,843 - INFO - Video thread started with source: Camera
2025-11-25 09:42:58,846 - ERROR - ❌ No camera found!
2025-11-25 09:42:58,988 - INFO - Video thread started with source: Camera
2025-11-25 09:42:58,990 - INFO - Frame 16 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:42:58,991 - ERROR - ❌ No camera found!
2025-11-25 09:42:59,129 - INFO - Video thread started with source: Camera
2025-11-25 09:42:59,132 - ERROR - ❌ No camera found!
2025-11-25 09:42:59,277 - INFO - Video thread started with source: Camera
2025-11-25 09:42:59,278 - INFO - Frame 18 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:42:59,279 - ERROR - ❌ No camera found!
2025-11-25 09:42:59,406 - INFO - Video thread started with source: Camera
2025-11-25 09:42:59,409 - ERROR - ❌ No camera found!
2025-11-25 09:42:59,544 - INFO - Video thread started with source: Camera
2025-11-25 09:42:59,545 - ERROR - ❌ No camera found!
2025-11-25 09:42:59,687 - INFO - Video thread started with source: Camera
2025-11-25 09:42:59,688 - ERROR - ❌ No camera found!
2025-11-25 09:42:59,688 - INFO - Frame 20 | PERCLOS: 0.00 | Yaw: 6.2° | Alerts: 0
2025-11-25 09:42:59,828 - INFO - Video thread started with source: Camera
2025-11-25 09:42:59,829 - ERROR - ❌ No camera found!
2025-11-25 09:43:00,004 - INFO - Video thread started with source: Camera
2025-11-25 09:43:00,005 - INFO - Frame 22 | PERCLOS: 0.01 | Yaw: 6.8° | Alerts: 0
2025-11-25 09:43:00,006 - ERROR - ❌ No camera found!
2025-11-25 09:43:00,170 - INFO - Video thread started with source: Camera
2025-11-25 09:43:00,174 - ERROR - ❌ No camera found!
2025-11-25 09:43:00,313 - INFO - Video thread started with source: Camera
2025-11-25 09:43:00,318 - ERROR - ❌ No camera found!
2025-11-25 09:43:00,462 - INFO - Video thread started with source: Camera
2025-11-25 09:43:00,463 - ERROR - ❌ No camera found!
2025-11-25 09:43:00,479 - INFO - Frame 24 | PERCLOS: 0.00 | Yaw: 7.0° | Alerts: 1
2025-11-25 09:43:00,603 - INFO - Video thread started with source: Camera
2025-11-25 09:43:00,604 - ERROR - ❌ No camera found!
2025-11-25 09:43:00,764 - INFO - Video thread started with source: Camera
2025-11-25 09:43:00,765 - ERROR - ❌ No camera found!
2025-11-25 09:43:00,766 - INFO - Frame 26 | PERCLOS: 0.00 | Yaw: 6.7° | Alerts: 1
2025-11-25 09:43:00,898 - INFO - Video thread started with source: Camera
2025-11-25 09:43:00,899 - ERROR - ❌ No camera found!
2025-11-25 09:43:00,935 - INFO - Frame 28 | PERCLOS: 0.00 | Yaw: 5.9° | Alerts: 1
2025-11-25 09:43:01,051 - INFO - Video thread started with source: Camera
2025-11-25 09:43:01,053 - ERROR - ❌ No camera found!
2025-11-25 09:43:01,200 - INFO - Video thread started with source: Camera
2025-11-25 09:43:01,203 - ERROR - ❌ No camera found!
2025-11-25 09:43:01,345 - INFO - Frame 30 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-25 09:43:01,350 - INFO - Video thread started with source: Camera
2025-11-25 09:43:01,351 - ERROR - ❌ No camera found!
2025-11-25 09:43:01,486 - INFO - Video thread started with source: Camera
2025-11-25 09:43:01,489 - ERROR - ❌ No camera found!
2025-11-25 09:43:01,655 - INFO - Video thread started with source: Camera
2025-11-25 09:43:01,657 - ERROR - ❌ No camera found!
2025-11-25 09:43:01,676 - INFO - Frame 32 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-25 09:43:01,803 - INFO - Video thread started with source: Camera
2025-11-25 09:43:01,804 - ERROR - ❌ No camera found!
2025-11-25 09:43:01,967 - INFO - Video thread started with source: Camera
2025-11-25 09:43:01,967 - INFO - Frame 34 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 1
2025-11-25 09:43:01,969 - ERROR - ❌ No camera found!
2025-11-25 09:43:02,116 - INFO - Video thread started with source: Camera
2025-11-25 09:43:02,118 - ERROR - ❌ No camera found!
2025-11-25 09:43:02,269 - INFO - Video thread started with source: Camera
2025-11-25 09:43:02,270 - ERROR - ❌ No camera found!
2025-11-25 09:43:02,424 - INFO - Frame 36 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-25 09:43:02,428 - INFO - Video thread started with source: Camera
2025-11-25 09:43:02,429 - ERROR - ❌ No camera found!
2025-11-25 09:43:02,575 - INFO - Video thread started with source: Camera
2025-11-25 09:43:02,580 - ERROR - ❌ No camera found!
2025-11-25 09:43:02,611 - INFO - Frame 38 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-25 09:43:02,741 - INFO - Video thread started with source: Camera
2025-11-25 09:43:02,742 - ERROR - ❌ No camera found!
2025-11-25 09:43:02,919 - INFO - Frame 40 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-25 09:43:02,920 - INFO - Video thread started with source: Camera
2025-11-25 09:43:02,924 - ERROR - ❌ No camera found!
2025-11-25 09:43:03,072 - INFO - Video thread started with source: Camera
2025-11-25 09:43:03,075 - ERROR - ❌ No camera found!
2025-11-25 09:43:03,236 - INFO - Video thread started with source: Camera
2025-11-25 09:43:03,237 - ERROR - ❌ No camera found!
2025-11-25 09:43:03,258 - INFO - Frame 42 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-25 09:43:03,398 - INFO - Video thread started with source: Camera
2025-11-25 09:43:03,399 - ERROR - ❌ No camera found!
2025-11-25 09:43:03,548 - INFO - Video thread started with source: Camera
2025-11-25 09:43:03,550 - INFO - Frame 44 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-25 09:43:03,552 - ERROR - ❌ No camera found!
2025-11-25 09:43:03,692 - INFO - Video thread started with source: Camera
2025-11-25 09:43:03,693 - ERROR - ❌ No camera found!
2025-11-25 09:43:03,842 - INFO - Video thread started with source: Camera
2025-11-25 09:43:03,844 - ERROR - ❌ No camera found!
2025-11-25 09:43:03,864 - INFO - Frame 46 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-25 09:43:04,008 - INFO - Video thread started with source: Camera
2025-11-25 09:43:04,013 - ERROR - ❌ No camera found!
2025-11-25 09:43:04,163 - INFO - Video thread started with source: Camera
2025-11-25 09:43:04,166 - ERROR - ❌ No camera found!
2025-11-25 09:43:04,327 - INFO - Frame 48 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-25 09:43:04,331 - INFO - Video thread started with source: Camera
2025-11-25 09:43:04,332 - ERROR - ❌ No camera found!
2025-11-25 09:43:04,603 - INFO - Frame 50 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-25 09:43:04,730 - INFO - Video thread started with source: Camera
2025-11-25 09:43:04,732 - ERROR - ❌ No camera found!
2025-11-25 09:43:04,890 - INFO - Video thread started with source: Camera
2025-11-25 09:43:04,891 - ERROR - ❌ No camera found!
2025-11-25 09:43:04,918 - INFO - Frame 52 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-25 09:43:05,056 - INFO - Video thread started with source: Camera
2025-11-25 09:43:05,059 - ERROR - ❌ No camera found!
2025-11-25 09:43:05,211 - INFO - Video thread started with source: Camera
2025-11-25 09:43:05,213 - ERROR - ❌ No camera found!
2025-11-25 09:43:05,360 - INFO - Frame 54 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-25 09:43:05,367 - INFO - Video thread started with source: Camera
2025-11-25 09:43:05,367 - ERROR - ❌ No camera found!
2025-11-25 09:43:05,517 - INFO - Video thread started with source: Camera
2025-11-25 09:43:05,520 - ERROR - ❌ No camera found!
2025-11-25 09:43:05,683 - INFO - Video thread started with source: Camera
2025-11-25 09:43:05,686 - ERROR - ❌ No camera found!
2025-11-25 09:43:05,701 - INFO - Frame 56 | PERCLOS: 0.00 | Yaw: 4.1° | Alerts: 1
2025-11-25 09:43:05,852 - INFO - Video thread started with source: Camera
2025-11-25 09:43:05,852 - ERROR - ❌ No camera found!
2025-11-25 09:43:06,012 - INFO - Video thread started with source: Camera
2025-11-25 09:43:06,017 - ERROR - ❌ No camera found!
2025-11-25 09:43:06,040 - INFO - Frame 58 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-25 09:43:06,176 - INFO - Video thread started with source: Camera
2025-11-25 09:43:06,178 - ERROR - ❌ No camera found!
2025-11-25 09:43:06,336 - INFO - Video thread started with source: Camera
2025-11-25 09:43:06,336 - ERROR - ❌ No camera found!
2025-11-25 09:43:06,491 - INFO - Frame 60 | PERCLOS: 0.00 | Yaw: 4.1° | Alerts: 1
2025-11-25 09:43:06,498 - INFO - Video thread started with source: Camera
2025-11-25 09:43:06,499 - ERROR - ❌ No camera found!
2025-11-25 09:43:06,649 - INFO - Video thread started with source: Camera
2025-11-25 09:43:06,650 - ERROR - ❌ No camera found!
2025-11-25 09:43:06,812 - INFO - Frame 62 | PERCLOS: 0.00 | Yaw: 4.1° | Alerts: 1
2025-11-25 09:43:06,814 - INFO - Video thread started with source: Camera
2025-11-25 09:43:06,815 - ERROR - ❌ No camera found!
2025-11-25 09:43:06,960 - INFO - Video thread started with source: Camera
2025-11-25 09:43:06,963 - ERROR - ❌ No camera found!
2025-11-25 09:43:06,999 - INFO - Frame 64 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-25 09:43:07,120 - INFO - Video thread started with source: Camera
2025-11-25 09:43:07,122 - ERROR - ❌ No camera found!
2025-11-25 09:43:07,286 - INFO - Video thread started with source: Camera
2025-11-25 09:43:07,287 - ERROR - ❌ No camera found!
2025-11-25 09:43:07,439 - INFO - Video thread started with source: Camera
2025-11-25 09:43:07,442 - ERROR - ❌ No camera found!
2025-11-25 09:43:07,456 - INFO - Frame 66 | PERCLOS: 0.00 | Yaw: 4.8° | Alerts: 1
2025-11-25 09:43:07,604 - INFO - Video thread started with source: Camera
2025-11-25 09:43:07,605 - ERROR - ❌ No camera found!
2025-11-25 09:43:07,764 - INFO - Video thread started with source: Camera
2025-11-25 09:43:07,770 - ERROR - ❌ No camera found!
2025-11-25 09:43:07,786 - INFO - Frame 68 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-25 09:43:07,928 - INFO - Video thread started with source: Camera
2025-11-25 09:43:07,933 - ERROR - ❌ No camera found!
2025-11-25 09:43:08,092 - INFO - Video thread started with source: Camera
2025-11-25 09:43:08,093 - INFO - Frame 70 | PERCLOS: 0.00 | Yaw: 4.1° | Alerts: 1
2025-11-25 09:43:08,093 - ERROR - ❌ No camera found!
2025-11-25 09:43:08,256 - INFO - Video thread started with source: Camera
2025-11-25 09:43:08,258 - ERROR - ❌ No camera found!
2025-11-25 09:43:08,417 - INFO - Video thread started with source: Camera
2025-11-25 09:43:08,422 - ERROR - ❌ No camera found!
2025-11-25 09:43:08,578 - INFO - Frame 72 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-25 09:43:08,584 - INFO - Video thread started with source: Camera
2025-11-25 09:43:08,585 - ERROR - ❌ No camera found!
2025-11-25 09:43:08,823 - INFO - Video thread started with source: Camera
2025-11-25 09:43:08,823 - ERROR - ❌ No camera found!
2025-11-25 09:43:08,976 - INFO - Video thread started with source: Camera
2025-11-25 09:43:08,977 - ERROR - ❌ No camera found!
2025-11-25 09:43:08,978 - INFO - Frame 74 | PERCLOS: 0.00 | Yaw: 3.5° | Alerts: 1
2025-11-25 09:43:09,123 - INFO - Video thread started with source: Camera
2025-11-25 09:43:09,124 - ERROR - ❌ No camera found!
2025-11-25 09:43:09,294 - INFO - Frame 76 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 1
2025-11-25 09:43:09,294 - INFO - Video thread started with source: Camera
2025-11-25 09:43:09,294 - ERROR - ❌ No camera found!
2025-11-25 09:43:09,451 - ERROR - ❌ No camera found!
2025-11-25 09:43:09,451 - INFO - Video thread started with source: Camera
2025-11-25 09:43:09,609 - INFO - Video thread started with source: Camera
2025-11-25 09:43:09,614 - ERROR - ❌ No camera found!
2025-11-25 09:43:09,628 - INFO - Frame 78 | PERCLOS: 0.00 | Yaw: 5.9° | Alerts: 1
2025-11-25 09:43:09,759 - INFO - Video thread started with source: Camera
2025-11-25 09:43:09,761 - ERROR - ❌ No camera found!
2025-11-25 09:43:09,797 - INFO - Frame 80 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:43:09,930 - INFO - Video thread started with source: Camera
2025-11-25 09:43:09,931 - ERROR - ❌ No camera found!
2025-11-25 09:43:10,093 - INFO - Video thread started with source: Camera
2025-11-25 09:43:10,096 - ERROR - ❌ No camera found!
2025-11-25 09:43:10,099 - INFO - Frame 82 | PERCLOS: 0.00 | Yaw: 8.7° | Alerts: 0
2025-11-25 09:43:10,247 - INFO - Video thread started with source: Camera
2025-11-25 09:43:10,249 - ERROR - ❌ No camera found!
2025-11-25 09:43:10,404 - INFO - Video thread started with source: Camera
2025-11-25 09:43:10,407 - ERROR - ❌ No camera found!
2025-11-25 09:43:10,565 - INFO - Frame 84 | PERCLOS: 0.00 | Yaw: 9.5° | Alerts: 1
2025-11-25 09:43:10,571 - INFO - Video thread started with source: Camera
2025-11-25 09:43:10,572 - ERROR - ❌ No camera found!
2025-11-25 09:43:10,717 - INFO - Video thread started with source: Camera
2025-11-25 09:43:10,717 - ERROR - ❌ No camera found!
2025-11-25 09:43:10,940 - INFO - Camera disabled
2025-11-25 09:43:10,941 - INFO - Frame 86 | PERCLOS: 0.00 | Yaw: 9.8° | Alerts: 1
2025-11-25 09:43:11,377 - INFO - Frame 88 | PERCLOS: 0.00 | Yaw: 10.3° | Alerts: 1
2025-11-25 09:43:11,821 - INFO - Frame 90 | PERCLOS: 0.00 | Yaw: 10.2° | Alerts: 1
2025-11-25 09:43:12,263 - INFO - Frame 92 | PERCLOS: 0.00 | Yaw: 9.8° | Alerts: 1
2025-11-25 09:43:12,406 - INFO - Camera enabled
2025-11-25 09:43:12,464 - INFO - Video thread started with source: Camera
2025-11-25 09:43:12,467 - ERROR - ❌ No camera found!
2025-11-25 09:43:12,627 - INFO - Video thread started with source: Camera
2025-11-25 09:43:12,632 - ERROR - ❌ No camera found!
2025-11-25 09:43:12,650 - INFO - Frame 94 | PERCLOS: 0.00 | Yaw: 8.8° | Alerts: 1
2025-11-25 09:43:12,775 - INFO - Video thread started with source: Camera
2025-11-25 09:43:12,780 - ERROR - ❌ No camera found!
2025-11-25 09:43:12,946 - INFO - Video thread started with source: Camera
2025-11-25 09:43:12,948 - ERROR - ❌ No camera found!
2025-11-25 09:43:13,104 - INFO - Frame 96 | PERCLOS: 0.00 | Yaw: 9.0° | Alerts: 1
2025-11-25 09:43:13,105 - INFO - Video thread started with source: Camera
2025-11-25 09:43:13,106 - ERROR - ❌ No camera found!
2025-11-25 09:43:13,253 - INFO - Video thread started with source: Camera
2025-11-25 09:43:13,257 - ERROR - ❌ No camera found!
2025-11-25 09:43:13,400 - INFO - Video thread started with source: Camera
2025-11-25 09:43:13,401 - ERROR - ❌ No camera found!
2025-11-25 09:43:13,427 - INFO - Frame 98 | PERCLOS: 0.00 | Yaw: 9.2° | Alerts: 1
2025-11-25 09:43:13,561 - INFO - Video thread started with source: Camera
2025-11-25 09:43:13,565 - ERROR - ❌ No camera found!
2025-11-25 09:43:13,727 - INFO - Video thread started with source: Camera
2025-11-25 09:43:13,728 - ERROR - ❌ No camera found!
2025-11-25 09:43:13,746 - INFO - Frame 100 | PERCLOS: 0.00 | Yaw: 11.1° | Alerts: 1
2025-11-25 09:43:13,883 - INFO - Video thread started with source: Camera
2025-11-25 09:43:13,885 - ERROR - ❌ No camera found!
2025-11-25 09:43:13,923 - INFO - Frame 102 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:43:14,044 - INFO - Video thread started with source: Camera
2025-11-25 09:43:14,046 - ERROR - ❌ No camera found!
2025-11-25 09:43:14,080 - INFO - Frame 104 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:43:14,200 - INFO - Video thread started with source: Camera
2025-11-25 09:43:14,201 - ERROR - ❌ No camera found!
2025-11-25 09:43:14,233 - INFO - Frame 106 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:43:14,366 - INFO - Video thread started with source: Camera
2025-11-25 09:43:14,367 - ERROR - ❌ No camera found!
2025-11-25 09:43:14,509 - INFO - Video thread started with source: Camera
2025-11-25 09:43:14,513 - ERROR - ❌ No camera found!
2025-11-25 09:43:14,675 - INFO - Video thread started with source: Camera
2025-11-25 09:43:14,679 - ERROR - ❌ No camera found!
2025-11-25 09:43:14,693 - INFO - Frame 108 | PERCLOS: 0.01 | Yaw: 1.1° | Alerts: 1
2025-11-25 09:43:14,831 - INFO - Video thread started with source: Camera
2025-11-25 09:43:14,836 - ERROR - ❌ No camera found!
2025-11-25 09:43:14,992 - INFO - Video thread started with source: Camera
2025-11-25 09:43:14,993 - INFO - Frame 110 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 1
2025-11-25 09:43:14,996 - ERROR - ❌ No camera found!
2025-11-25 09:43:15,167 - INFO - Video thread started with source: Camera
2025-11-25 09:43:15,167 - ERROR - ❌ No camera found!
2025-11-25 09:43:15,320 - INFO - Video thread started with source: Camera
2025-11-25 09:43:15,322 - INFO - Frame 112 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 1
2025-11-25 09:43:15,323 - ERROR - ❌ No camera found!
2025-11-25 09:43:15,482 - INFO - Video thread started with source: Camera
2025-11-25 09:43:15,483 - ERROR - ❌ No camera found!
2025-11-25 09:43:15,640 - INFO - Video thread started with source: Camera
2025-11-25 09:43:15,641 - ERROR - ❌ No camera found!
2025-11-25 09:43:15,785 - INFO - Frame 114 | PERCLOS: 0.29 | Yaw: 4.4° | Alerts: 1
2025-11-25 09:43:15,792 - INFO - Video thread started with source: Camera
2025-11-25 09:43:15,793 - ERROR - ❌ No camera found!
2025-11-25 09:43:15,954 - INFO - Video thread started with source: Camera
2025-11-25 09:43:15,957 - ERROR - ❌ No camera found!
2025-11-25 09:43:16,135 - INFO - Frame 116 | PERCLOS: 0.00 | Yaw: 5.2° | Alerts: 1
2025-11-25 09:43:16,320 - INFO - Video thread started with source: Camera
2025-11-25 09:43:16,322 - ERROR - ❌ No camera found!
2025-11-25 09:43:16,345 - INFO - Frame 118 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-25 09:43:16,491 - INFO - Video thread started with source: Camera
2025-11-25 09:43:16,497 - ERROR - ❌ No camera found!
2025-11-25 09:43:16,654 - INFO - Video thread started with source: Camera
2025-11-25 09:43:16,655 - ERROR - ❌ No camera found!
2025-11-25 09:43:16,796 - INFO - Video thread started with source: Camera
2025-11-25 09:43:16,800 - ERROR - ❌ No camera found!
2025-11-25 09:43:16,815 - INFO - Frame 120 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 1
2025-11-25 09:43:16,936 - INFO - Video thread started with source: Camera
2025-11-25 09:43:16,941 - ERROR - ❌ No camera found!
2025-11-25 09:43:17,083 - INFO - Video thread started with source: Camera
2025-11-25 09:43:17,084 - ERROR - ❌ No camera found!
2025-11-25 09:43:17,114 - INFO - Frame 122 | PERCLOS: 0.00 | Yaw: 4.8° | Alerts: 1
2025-11-25 09:43:17,252 - INFO - Video thread started with source: Camera
2025-11-25 09:43:17,256 - ERROR - ❌ No camera found!
2025-11-25 09:43:17,402 - INFO - Video thread started with source: Camera
2025-11-25 09:43:17,402 - ERROR - ❌ No camera found!
2025-11-25 09:43:17,431 - INFO - Frame 124 | PERCLOS: 0.00 | Yaw: 5.2° | Alerts: 1
2025-11-25 09:43:17,562 - INFO - Video thread started with source: Camera
2025-11-25 09:43:17,565 - ERROR - ❌ No camera found!
2025-11-25 09:43:17,728 - INFO - Video thread started with source: Camera
2025-11-25 09:43:17,729 - ERROR - ❌ No camera found!
2025-11-25 09:43:17,879 - INFO - Frame 126 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-25 09:43:17,886 - INFO - Video thread started with source: Camera
2025-11-25 09:43:17,887 - ERROR - ❌ No camera found!
2025-11-25 09:43:18,037 - INFO - Video thread started with source: Camera
2025-11-25 09:43:18,039 - ERROR - ❌ No camera found!
2025-11-25 09:43:18,209 - INFO - Video thread started with source: Camera
2025-11-25 09:43:18,210 - ERROR - ❌ No camera found!
2025-11-25 09:43:18,215 - INFO - Frame 128 | PERCLOS: 0.00 | Yaw: 6.8° | Alerts: 1
2025-11-25 09:43:18,372 - INFO - Video thread started with source: Camera
2025-11-25 09:43:18,375 - ERROR - ❌ No camera found!
2025-11-25 09:43:18,528 - INFO - Video thread started with source: Camera
2025-11-25 09:43:18,531 - ERROR - ❌ No camera found!
2025-11-25 09:43:18,557 - INFO - Frame 130 | PERCLOS: 0.00 | Yaw: 6.9° | Alerts: 1
2025-11-25 09:43:18,700 - INFO - Video thread started with source: Camera
2025-11-25 09:43:18,704 - ERROR - ❌ No camera found!
2025-11-25 09:43:18,841 - INFO - Video thread started with source: Camera
2025-11-25 09:43:18,846 - ERROR - ❌ No camera found!
2025-11-25 09:43:19,006 - INFO - Video thread started with source: Camera
2025-11-25 09:43:19,011 - ERROR - ❌ No camera found!
2025-11-25 09:43:19,026 - INFO - Frame 132 | PERCLOS: 0.00 | Yaw: 6.2° | Alerts: 1
2025-11-25 09:43:19,167 - INFO - Video thread started with source: Camera
2025-11-25 09:43:19,170 - ERROR - ❌ No camera found!
2025-11-25 09:43:19,342 - INFO - Video thread started with source: Camera
2025-11-25 09:43:19,343 - ERROR - ❌ No camera found!
2025-11-25 09:43:19,367 - INFO - Frame 134 | PERCLOS: 0.00 | Yaw: 5.6° | Alerts: 1
2025-11-25 09:43:19,489 - INFO - Video thread started with source: Camera
2025-11-25 09:43:19,492 - ERROR - ❌ No camera found!
2025-11-25 09:43:19,646 - INFO - Frame 136 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 1
2025-11-25 09:43:19,646 - INFO - Video thread started with source: Camera
2025-11-25 09:43:19,649 - ERROR - ❌ No camera found!
2025-11-25 09:43:19,809 - INFO - Video thread started with source: Camera
2025-11-25 09:43:19,810 - ERROR - ❌ No camera found!
2025-11-25 09:43:19,967 - INFO - Video thread started with source: Camera
2025-11-25 09:43:19,970 - ERROR - ❌ No camera found!
2025-11-25 09:43:19,988 - INFO - Frame 138 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 1
2025-11-25 09:43:20,131 - INFO - Video thread started with source: Camera
2025-11-25 09:43:20,133 - ERROR - ❌ No camera found!
2025-11-25 09:43:20,289 - INFO - Video thread started with source: Camera
2025-11-25 09:43:20,296 - ERROR - ❌ No camera found!
2025-11-25 09:43:20,313 - INFO - Frame 140 | PERCLOS: 0.39 | Yaw: 5.2° | Alerts: 2
2025-11-25 09:43:20,439 - INFO - Video thread started with source: Camera
2025-11-25 09:43:20,441 - ERROR - ❌ No camera found!
2025-11-25 09:43:20,593 - INFO - Video thread started with source: Camera
2025-11-25 09:43:20,599 - ERROR - ❌ No camera found!
2025-11-25 09:43:20,619 - INFO - Frame 142 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 1
2025-11-25 09:43:20,756 - INFO - Video thread started with source: Camera
2025-11-25 09:43:20,759 - ERROR - ❌ No camera found!
2025-11-25 09:43:20,936 - INFO - Video thread started with source: Camera
2025-11-25 09:43:20,939 - ERROR - ❌ No camera found!
2025-11-25 09:43:21,092 - INFO - Frame 144 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 1
2025-11-25 09:43:21,096 - INFO - Video thread started with source: Camera
2025-11-25 09:43:21,097 - ERROR - ❌ No camera found!
2025-11-25 09:43:21,248 - INFO - Video thread started with source: Camera
2025-11-25 09:43:21,251 - ERROR - ❌ No camera found!
2025-11-25 09:43:21,285 - INFO - Frame 146 | PERCLOS: 0.11 | Yaw: 1.9° | Alerts: 1
2025-11-25 09:43:21,410 - INFO - Video thread started with source: Camera
2025-11-25 09:43:21,412 - ERROR - ❌ No camera found!
2025-11-25 09:43:21,606 - INFO - Frame 148 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:43:21,606 - INFO - Video thread started with source: Camera
2025-11-25 09:43:21,607 - ERROR - ❌ No camera found!
2025-11-25 09:43:21,782 - INFO - Video thread started with source: Camera
2025-11-25 09:43:21,783 - ERROR - ❌ No camera found!
2025-11-25 09:43:21,950 - INFO - Video thread started with source: Camera
2025-11-25 09:43:21,952 - ERROR - ❌ No camera found!
2025-11-25 09:43:21,968 - INFO - Frame 150 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 1
2025-11-25 09:43:22,116 - INFO - Video thread started with source: Camera
2025-11-25 09:43:22,117 - ERROR - ❌ No camera found!
2025-11-25 09:43:22,284 - INFO - Video thread started with source: Camera
2025-11-25 09:43:22,286 - ERROR - ❌ No camera found!
2025-11-25 09:43:22,306 - INFO - Frame 152 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 1
2025-11-25 09:43:22,452 - INFO - Video thread started with source: Camera
2025-11-25 09:43:22,453 - ERROR - ❌ No camera found!
2025-11-25 09:43:22,620 - INFO - Video thread started with source: Camera
2025-11-25 09:43:22,622 - ERROR - ❌ No camera found!
2025-11-25 09:43:22,643 - INFO - Frame 154 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-25 09:43:22,778 - INFO - Video thread started with source: Camera
2025-11-25 09:43:22,781 - ERROR - ❌ No camera found!
2025-11-25 09:43:22,930 - INFO - Video thread started with source: Camera
2025-11-25 09:43:22,931 - ERROR - ❌ No camera found!
2025-11-25 09:43:23,081 - INFO - Video thread started with source: Camera
2025-11-25 09:43:23,082 - ERROR - ❌ No camera found!
2025-11-25 09:43:23,097 - INFO - Frame 156 | PERCLOS: 0.00 | Yaw: 4.2° | Alerts: 1
2025-11-25 09:43:23,231 - INFO - Video thread started with source: Camera
2025-11-25 09:43:23,236 - ERROR - ❌ No camera found!
2025-11-25 09:43:23,389 - INFO - Video thread started with source: Camera
2025-11-25 09:43:23,392 - ERROR - ❌ No camera found!
2025-11-25 09:43:23,422 - INFO - Frame 158 | PERCLOS: 0.00 | Yaw: 4.1° | Alerts: 1
2025-11-25 09:43:23,543 - INFO - Video thread started with source: Camera
2025-11-25 09:43:23,544 - ERROR - ❌ No camera found!
2025-11-25 09:43:23,697 - INFO - Video thread started with source: Camera
2025-11-25 09:43:23,699 - ERROR - ❌ No camera found!
2025-11-25 09:43:23,719 - INFO - Frame 160 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 1
2025-11-25 09:43:23,846 - INFO - Video thread started with source: Camera
2025-11-25 09:43:23,848 - ERROR - ❌ No camera found!
2025-11-25 09:43:24,011 - INFO - Video thread started with source: Camera
2025-11-25 09:43:24,012 - ERROR - ❌ No camera found!
2025-11-25 09:43:24,156 - INFO - Video thread started with source: Camera
2025-11-25 09:43:24,160 - ERROR - ❌ No camera found!
2025-11-25 09:43:24,176 - INFO - Frame 162 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 1
2025-11-25 09:43:24,310 - INFO - Video thread started with source: Camera
2025-11-25 09:43:24,313 - ERROR - ❌ No camera found!
2025-11-25 09:44:29,026 - INFO - Loading models...
2025-11-25 09:44:29,047 - INFO - ✓ YOLO ONNX loaded
2025-11-25 09:44:29,083 - INFO - ✓ MediaPipe Face Mesh loaded
2025-11-25 09:44:29,091 - INFO - ✓ MediaPipe Pose loaded (for smoke & seatbelt)
2025-11-25 09:44:29,097 - INFO - Video thread started with source: Camera
2025-11-25 09:44:29,097 - INFO - Video thread started with source: Camera
2025-11-25 09:44:29,105 - INFO - Video thread started with source: Camera
2025-11-25 09:44:29,111 - ERROR - ❌ No camera found!
2025-11-25 09:44:29,112 - ERROR - ❌ No camera found!
2025-11-25 09:44:29,255 - INFO - ✓ Camera 0 opened successfully
2025-11-25 09:44:29,320 - INFO - Video thread started with source: Camera
2025-11-25 09:44:29,320 - INFO - Video thread started with source: Camera
2025-11-25 09:44:29,322 - ERROR - ❌ No camera found!
2025-11-25 09:44:29,329 - ERROR - ❌ No camera found!
2025-11-25 09:44:29,529 - INFO - Video thread started with source: Camera
2025-11-25 09:44:29,530 - INFO - Video thread started with source: Camera
2025-11-25 09:44:29,531 - ERROR - ❌ No camera found!
2025-11-25 09:44:29,531 - ERROR - ❌ No camera found!
2025-11-25 09:44:29,715 - INFO - Video thread started with source: Camera
2025-11-25 09:44:29,715 - INFO - Video thread started with source: Camera
2025-11-25 09:44:29,716 - ERROR - ❌ No camera found!
2025-11-25 09:44:29,716 - ERROR - ❌ No camera found!
2025-11-25 09:44:29,925 - INFO - Video thread started with source: Camera
2025-11-25 09:44:29,926 - INFO - Video thread started with source: Camera
2025-11-25 09:44:29,927 - ERROR - ❌ No camera found!
2025-11-25 09:44:29,928 - ERROR - ❌ No camera found!
2025-11-25 09:44:30,122 - INFO - Video thread started with source: Camera
2025-11-25 09:44:30,122 - INFO - Video thread started with source: Camera
2025-11-25 09:44:30,123 - ERROR - ❌ No camera found!
2025-11-25 09:44:30,124 - ERROR - ❌ No camera found!
2025-11-25 09:44:30,144 - INFO - Frame 0 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 1
2025-11-25 09:44:30,321 - INFO - Video thread started with source: Camera
2025-11-25 09:44:30,324 - INFO - Video thread started with source: Camera
2025-11-25 09:44:30,325 - ERROR - ❌ No camera found!
2025-11-25 09:44:30,329 - ERROR - ❌ No camera found!
2025-11-25 09:44:30,526 - INFO - Video thread started with source: Camera
2025-11-25 09:44:30,530 - ERROR - ❌ No camera found!
2025-11-25 09:44:30,530 - INFO - Video thread started with source: Camera
2025-11-25 09:44:30,531 - ERROR - ❌ No camera found!
2025-11-25 09:44:30,549 - INFO - Frame 2 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-25 09:44:30,740 - INFO - Video thread started with source: Camera
2025-11-25 09:44:30,741 - INFO - Video thread started with source: Camera
2025-11-25 09:44:30,744 - ERROR - ❌ No camera found!
2025-11-25 09:44:30,746 - ERROR - ❌ No camera found!
2025-11-25 09:44:30,957 - INFO - Video thread started with source: Camera
2025-11-25 09:44:30,957 - INFO - Frame 4 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 1
2025-11-25 09:44:30,960 - ERROR - ❌ No camera found!
2025-11-25 09:44:30,960 - INFO - Video thread started with source: Camera
2025-11-25 09:44:30,963 - ERROR - ❌ No camera found!
2025-11-25 09:44:31,169 - INFO - Video thread started with source: Camera
2025-11-25 09:44:31,170 - INFO - Video thread started with source: Camera
2025-11-25 09:44:31,172 - ERROR - ❌ No camera found!
2025-11-25 09:44:31,172 - ERROR - ❌ No camera found!
2025-11-25 09:44:31,383 - INFO - Video thread started with source: Camera
2025-11-25 09:44:31,383 - INFO - Video thread started with source: Camera
2025-11-25 09:44:31,384 - ERROR - ❌ No camera found!
2025-11-25 09:44:31,386 - ERROR - ❌ No camera found!
2025-11-25 09:44:31,398 - INFO - Frame 6 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 1
2025-11-25 09:44:31,605 - INFO - Video thread started with source: Camera
2025-11-25 09:44:31,606 - INFO - Video thread started with source: Camera
2025-11-25 09:44:31,610 - ERROR - ❌ No camera found!
2025-11-25 09:44:31,610 - ERROR - ❌ No camera found!
2025-11-25 09:44:31,810 - INFO - Video thread started with source: Camera
2025-11-25 09:44:31,811 - ERROR - ❌ No camera found!
2025-11-25 09:44:31,812 - INFO - Video thread started with source: Camera
2025-11-25 09:44:31,814 - ERROR - ❌ No camera found!
2025-11-25 09:44:31,845 - INFO - Frame 8 | PERCLOS: 0.00 | Yaw: 4.7° | Alerts: 1
2025-11-25 09:44:32,031 - INFO - Video thread started with source: Camera
2025-11-25 09:44:32,033 - INFO - Video thread started with source: Camera
2025-11-25 09:44:32,034 - ERROR - ❌ No camera found!
2025-11-25 09:44:32,035 - ERROR - ❌ No camera found!
2025-11-25 09:44:32,246 - INFO - Video thread started with source: Camera
2025-11-25 09:44:32,249 - INFO - Video thread started with source: Camera
2025-11-25 09:44:32,252 - ERROR - ❌ No camera found!
2025-11-25 09:44:32,252 - ERROR - ❌ No camera found!
2025-11-25 09:44:32,253 - INFO - Frame 10 | PERCLOS: 0.00 | Yaw: 5.2° | Alerts: 1
2025-11-25 09:44:32,466 - INFO - Video thread started with source: Camera
2025-11-25 09:44:32,468 - INFO - Video thread started with source: Camera
2025-11-25 09:44:32,469 - ERROR - ❌ No camera found!
2025-11-25 09:44:32,472 - ERROR - ❌ No camera found!
2025-11-25 09:44:32,673 - INFO - Video thread started with source: Camera
2025-11-25 09:44:32,677 - INFO - Video thread started with source: Camera
2025-11-25 09:44:32,679 - ERROR - ❌ No camera found!
2025-11-25 09:44:32,679 - ERROR - ❌ No camera found!
2025-11-25 09:44:32,907 - INFO - Video thread started with source: Camera
2025-11-25 09:44:32,914 - INFO - Video thread started with source: Camera
2025-11-25 09:44:32,914 - ERROR - ❌ No camera found!
2025-11-25 09:44:32,919 - ERROR - ❌ No camera found!
2025-11-25 09:44:33,162 - INFO - Frame 12 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-25 09:44:33,169 - INFO - Video thread started with source: Camera
2025-11-25 09:44:33,169 - INFO - Video thread started with source: Camera
2025-11-25 09:44:33,171 - ERROR - ❌ No camera found!
2025-11-25 09:44:33,171 - ERROR - ❌ No camera found!
2025-11-25 09:44:33,376 - INFO - Video thread started with source: Camera
2025-11-25 09:44:33,379 - ERROR - ❌ No camera found!
2025-11-25 09:44:33,382 - INFO - Video thread started with source: Camera
2025-11-25 09:44:33,387 - ERROR - ❌ No camera found!
2025-11-25 09:44:33,569 - INFO - Video thread started with source: Camera
2025-11-25 09:44:33,570 - INFO - Video thread started with source: Camera
2025-11-25 09:44:33,571 - ERROR - ❌ No camera found!
2025-11-25 09:44:33,574 - ERROR - ❌ No camera found!
2025-11-25 09:44:33,596 - INFO - Frame 14 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-25 09:44:33,792 - INFO - Video thread started with source: Camera
2025-11-25 09:44:33,797 - INFO - Video thread started with source: Camera
2025-11-25 09:44:33,797 - ERROR - ❌ No camera found!
2025-11-25 09:44:33,798 - ERROR - ❌ No camera found!
2025-11-25 09:44:33,991 - INFO - Video thread started with source: Camera
2025-11-25 09:44:33,993 - INFO - Video thread started with source: Camera
2025-11-25 09:44:33,994 - ERROR - ❌ No camera found!
2025-11-25 09:44:33,996 - ERROR - ❌ No camera found!
2025-11-25 09:44:34,006 - INFO - Frame 16 | PERCLOS: 0.00 | Yaw: 5.3° | Alerts: 1
2025-11-25 09:44:34,208 - INFO - Video thread started with source: Camera
2025-11-25 09:44:34,210 - INFO - Video thread started with source: Camera
2025-11-25 09:44:34,210 - ERROR - ❌ No camera found!
2025-11-25 09:44:34,212 - ERROR - ❌ No camera found!
2025-11-25 09:44:34,435 - INFO - Video thread started with source: Camera
2025-11-25 09:44:34,435 - INFO - Video thread started with source: Camera
2025-11-25 09:44:34,437 - ERROR - ❌ No camera found!
2025-11-25 09:44:34,439 - ERROR - ❌ No camera found!
2025-11-25 09:44:34,651 - INFO - Video thread started with source: Camera
2025-11-25 09:44:34,658 - INFO - Video thread started with source: Camera
2025-11-25 09:44:34,658 - ERROR - ❌ No camera found!
2025-11-25 09:44:34,662 - ERROR - ❌ No camera found!
2025-11-25 09:44:34,674 - INFO - Frame 18 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-25 09:44:34,882 - INFO - Video thread started with source: Camera
2025-11-25 09:44:34,884 - ERROR - ❌ No camera found!
2025-11-25 09:44:34,884 - INFO - Video thread started with source: Camera
2025-11-25 09:44:34,888 - ERROR - ❌ No camera found!
2025-11-25 09:44:35,074 - INFO - Video thread started with source: Camera
2025-11-25 09:44:35,078 - ERROR - ❌ No camera found!
2025-11-25 09:44:35,087 - INFO - Video thread started with source: Camera
2025-11-25 09:44:35,090 - ERROR - ❌ No camera found!
2025-11-25 09:44:35,102 - INFO - Frame 20 | PERCLOS: 0.00 | Yaw: 4.8° | Alerts: 1
2025-11-25 09:44:35,275 - INFO - Video thread started with source: Camera
2025-11-25 09:44:35,276 - INFO - Video thread started with source: Camera
2025-11-25 09:44:35,278 - ERROR - ❌ No camera found!
2025-11-25 09:44:35,280 - ERROR - ❌ No camera found!
2025-11-25 09:44:35,473 - INFO - Video thread started with source: Camera
2025-11-25 09:44:35,473 - INFO - Video thread started with source: Camera
2025-11-25 09:44:35,477 - ERROR - ❌ No camera found!
2025-11-25 09:44:35,477 - ERROR - ❌ No camera found!
2025-11-25 09:44:35,493 - INFO - Frame 22 | PERCLOS: 0.00 | Yaw: 4.3° | Alerts: 1
2025-11-25 09:44:35,674 - INFO - Video thread started with source: Camera
2025-11-25 09:44:35,675 - INFO - Video thread started with source: Camera
2025-11-25 09:44:35,675 - ERROR - ❌ No camera found!
2025-11-25 09:44:35,678 - ERROR - ❌ No camera found!
2025-11-25 09:44:35,892 - INFO - Video thread started with source: Camera
2025-11-25 09:44:35,897 - ERROR - ❌ No camera found!
2025-11-25 09:44:35,897 - INFO - Video thread started with source: Camera
2025-11-25 09:44:35,900 - ERROR - ❌ No camera found!
2025-11-25 09:44:36,098 - INFO - Frame 24 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-25 09:44:36,106 - INFO - Video thread started with source: Camera
2025-11-25 09:44:36,106 - INFO - Video thread started with source: Camera
2025-11-25 09:44:36,107 - ERROR - ❌ No camera found!
2025-11-25 09:44:36,107 - ERROR - ❌ No camera found!
2025-11-25 09:44:36,328 - INFO - Video thread started with source: Camera
2025-11-25 09:44:36,331 - INFO - Video thread started with source: Camera
2025-11-25 09:44:36,331 - ERROR - ❌ No camera found!
2025-11-25 09:44:36,333 - ERROR - ❌ No camera found!
2025-11-25 09:44:36,532 - INFO - Video thread started with source: Camera
2025-11-25 09:44:36,533 - INFO - Video thread started with source: Camera
2025-11-25 09:44:36,533 - ERROR - ❌ No camera found!
2025-11-25 09:44:36,535 - ERROR - ❌ No camera found!
2025-11-25 09:44:36,539 - INFO - Frame 26 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-25 09:44:36,745 - INFO - Video thread started with source: Camera
2025-11-25 09:44:36,746 - INFO - Video thread started with source: Camera
2025-11-25 09:44:36,747 - ERROR - ❌ No camera found!
2025-11-25 09:44:36,747 - ERROR - ❌ No camera found!
2025-11-25 09:44:36,954 - INFO - Video thread started with source: Camera
2025-11-25 09:44:36,955 - INFO - Video thread started with source: Camera
2025-11-25 09:44:36,956 - ERROR - ❌ No camera found!
2025-11-25 09:44:36,956 - ERROR - ❌ No camera found!
2025-11-25 09:44:36,982 - INFO - Frame 28 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-25 09:44:37,148 - INFO - Video thread started with source: Camera
2025-11-25 09:44:37,150 - INFO - Video thread started with source: Camera
2025-11-25 09:44:37,150 - ERROR - ❌ No camera found!
2025-11-25 09:44:37,150 - ERROR - ❌ No camera found!
2025-11-25 09:44:37,352 - INFO - Video thread started with source: Camera
2025-11-25 09:44:37,352 - INFO - Video thread started with source: Camera
2025-11-25 09:44:37,353 - ERROR - ❌ No camera found!
2025-11-25 09:44:37,358 - ERROR - ❌ No camera found!
2025-11-25 09:44:37,556 - INFO - Frame 30 | PERCLOS: 0.09 | Yaw: -2.4° | Alerts: 1
2025-11-25 09:44:37,557 - INFO - Video thread started with source: Camera
2025-11-25 09:44:37,558 - INFO - Video thread started with source: Camera
2025-11-25 09:44:37,558 - ERROR - ❌ No camera found!
2025-11-25 09:44:37,558 - ERROR - ❌ No camera found!
2025-11-25 09:44:37,771 - INFO - Video thread started with source: Camera
2025-11-25 09:44:37,772 - INFO - Video thread started with source: Camera
2025-11-25 09:44:37,773 - ERROR - ❌ No camera found!
2025-11-25 09:44:37,773 - ERROR - ❌ No camera found!
2025-11-25 09:44:37,968 - INFO - Frame 32 | PERCLOS: 0.00 | Yaw: 0.2° | Alerts: 1
2025-11-25 09:44:37,969 - INFO - Video thread started with source: Camera
2025-11-25 09:44:37,972 - INFO - Video thread started with source: Camera
2025-11-25 09:44:37,972 - ERROR - ❌ No camera found!
2025-11-25 09:44:37,974 - ERROR - ❌ No camera found!
2025-11-25 09:44:38,171 - INFO - Video thread started with source: Camera
2025-11-25 09:44:38,173 - INFO - Video thread started with source: Camera
2025-11-25 09:44:38,174 - ERROR - ❌ No camera found!
2025-11-25 09:44:38,176 - ERROR - ❌ No camera found!
2025-11-25 09:44:38,375 - INFO - Video thread started with source: Camera
2025-11-25 09:44:38,376 - INFO - Video thread started with source: Camera
2025-11-25 09:44:38,376 - ERROR - ❌ No camera found!
2025-11-25 09:44:38,377 - ERROR - ❌ No camera found!
2025-11-25 09:44:38,379 - INFO - Frame 34 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 1
2025-11-25 09:44:38,572 - INFO - Video thread started with source: Camera
2025-11-25 09:44:38,574 - INFO - Video thread started with source: Camera
2025-11-25 09:44:38,574 - ERROR - ❌ No camera found!
2025-11-25 09:44:38,578 - ERROR - ❌ No camera found!
2025-11-25 09:44:38,797 - INFO - Video thread started with source: Camera
2025-11-25 09:44:38,801 - ERROR - ❌ No camera found!
2025-11-25 09:44:38,805 - INFO - Video thread started with source: Camera
2025-11-25 09:44:38,811 - ERROR - ❌ No camera found!
2025-11-25 09:44:39,003 - INFO - Frame 36 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 1
2025-11-25 09:44:39,012 - INFO - Video thread started with source: Camera
2025-11-25 09:44:39,012 - INFO - Video thread started with source: Camera
2025-11-25 09:44:39,012 - ERROR - ❌ No camera found!
2025-11-25 09:44:39,014 - ERROR - ❌ No camera found!
2025-11-25 09:44:39,219 - INFO - Video thread started with source: Camera
2025-11-25 09:44:39,219 - INFO - Video thread started with source: Camera
2025-11-25 09:44:39,221 - ERROR - ❌ No camera found!
2025-11-25 09:44:39,221 - ERROR - ❌ No camera found!
2025-11-25 09:44:39,401 - INFO - Video thread started with source: Camera
2025-11-25 09:44:39,401 - INFO - Video thread started with source: Camera
2025-11-25 09:44:39,406 - ERROR - ❌ No camera found!
2025-11-25 09:44:39,408 - ERROR - ❌ No camera found!
2025-11-25 09:44:39,433 - INFO - Frame 38 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-25 09:44:39,625 - INFO - Video thread started with source: Camera
2025-11-25 09:44:39,625 - INFO - Video thread started with source: Camera
2025-11-25 09:44:39,629 - ERROR - ❌ No camera found!
2025-11-25 09:44:39,632 - ERROR - ❌ No camera found!
2025-11-25 09:44:39,852 - INFO - Video thread started with source: Camera
2025-11-25 09:44:39,852 - INFO - Video thread started with source: Camera
2025-11-25 09:44:39,852 - INFO - Frame 40 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-25 09:44:39,853 - ERROR - ❌ No camera found!
2025-11-25 09:44:39,853 - ERROR - ❌ No camera found!
2025-11-25 09:44:40,059 - INFO - Video thread started with source: Camera
2025-11-25 09:44:40,059 - INFO - Video thread started with source: Camera
2025-11-25 09:44:40,061 - ERROR - ❌ No camera found!
2025-11-25 09:44:40,061 - ERROR - ❌ No camera found!
2025-11-25 09:44:40,264 - INFO - Video thread started with source: Camera
2025-11-25 09:44:40,264 - INFO - Video thread started with source: Camera
2025-11-25 09:44:40,265 - ERROR - ❌ No camera found!
2025-11-25 09:44:40,266 - ERROR - ❌ No camera found!
2025-11-25 09:44:40,459 - INFO - Frame 42 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 1
2025-11-25 09:44:40,466 - INFO - Video thread started with source: Camera
2025-11-25 09:44:40,469 - INFO - Video thread started with source: Camera
2025-11-25 09:44:40,470 - ERROR - ❌ No camera found!
2025-11-25 09:44:40,471 - ERROR - ❌ No camera found!
2025-11-25 09:44:40,666 - INFO - Video thread started with source: Camera
2025-11-25 09:44:40,667 - INFO - Video thread started with source: Camera
2025-11-25 09:44:40,667 - ERROR - ❌ No camera found!
2025-11-25 09:44:40,671 - ERROR - ❌ No camera found!
2025-11-25 09:44:40,857 - INFO - Video thread started with source: Camera
2025-11-25 09:44:40,862 - ERROR - ❌ No camera found!
2025-11-25 09:44:40,868 - INFO - Video thread started with source: Camera
2025-11-25 09:44:40,874 - ERROR - ❌ No camera found!
2025-11-25 09:44:40,890 - INFO - Frame 44 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-25 09:44:41,070 - INFO - Video thread started with source: Camera
2025-11-25 09:44:41,070 - INFO - Video thread started with source: Camera
2025-11-25 09:44:41,071 - ERROR - ❌ No camera found!
2025-11-25 09:44:41,075 - ERROR - ❌ No camera found!
2025-11-25 09:44:41,294 - INFO - Video thread started with source: Camera
2025-11-25 09:44:41,295 - INFO - Video thread started with source: Camera
2025-11-25 09:44:41,295 - INFO - Frame 46 | PERCLOS: 0.36 | Yaw: 1.7° | Alerts: 2
2025-11-25 09:44:41,297 - ERROR - ❌ No camera found!
2025-11-25 09:44:41,297 - ERROR - ❌ No camera found!
2025-11-25 09:44:41,502 - ERROR - ❌ No camera found!
2025-11-25 09:44:41,502 - INFO - Video thread started with source: Camera
2025-11-25 09:44:41,509 - INFO - Video thread started with source: Camera
2025-11-25 09:44:41,510 - ERROR - ❌ No camera found!
2025-11-25 09:44:41,714 - INFO - Video thread started with source: Camera
2025-11-25 09:44:41,720 - INFO - Video thread started with source: Camera
2025-11-25 09:44:41,720 - ERROR - ❌ No camera found!
2025-11-25 09:44:41,721 - ERROR - ❌ No camera found!
2025-11-25 09:44:41,920 - INFO - Video thread started with source: Camera
2025-11-25 09:44:41,922 - INFO - Video thread started with source: Camera
2025-11-25 09:44:41,923 - ERROR - ❌ No camera found!
2025-11-25 09:44:41,923 - ERROR - ❌ No camera found!
2025-11-25 09:44:41,935 - INFO - Frame 48 | PERCLOS: 0.16 | Yaw: 1.4° | Alerts: 1
2025-11-25 09:44:42,131 - INFO - Video thread started with source: Camera
2025-11-25 09:44:42,132 - INFO - Video thread started with source: Camera
2025-11-25 09:44:42,132 - ERROR - ❌ No camera found!
2025-11-25 09:44:42,133 - ERROR - ❌ No camera found!
2025-11-25 09:44:42,354 - INFO - Video thread started with source: Camera
2025-11-25 09:44:42,354 - INFO - Video thread started with source: Camera
2025-11-25 09:44:42,355 - INFO - Frame 50 | PERCLOS: 0.21 | Yaw: 1.5° | Alerts: 1
2025-11-25 09:44:42,355 - ERROR - ❌ No camera found!
2025-11-25 09:44:42,355 - ERROR - ❌ No camera found!
2025-11-25 09:44:42,550 - INFO - Video thread started with source: Camera
2025-11-25 09:44:42,554 - INFO - Video thread started with source: Camera
2025-11-25 09:44:42,556 - ERROR - ❌ No camera found!
2025-11-25 09:44:42,557 - ERROR - ❌ No camera found!
2025-11-25 09:44:42,755 - INFO - Video thread started with source: Camera
2025-11-25 09:44:42,755 - INFO - Video thread started with source: Camera
2025-11-25 09:44:42,756 - ERROR - ❌ No camera found!
2025-11-25 09:44:42,758 - INFO - Frame 52 | PERCLOS: 0.23 | Yaw: -0.9° | Alerts: 1
2025-11-25 09:44:42,758 - ERROR - ❌ No camera found!
2025-11-25 09:44:42,978 - INFO - Video thread started with source: Camera
2025-11-25 09:44:42,978 - INFO - Video thread started with source: Camera
2025-11-25 09:44:42,980 - ERROR - ❌ No camera found!
2025-11-25 09:44:42,980 - ERROR - ❌ No camera found!
2025-11-25 09:44:43,199 - INFO - Video thread started with source: Camera
2025-11-25 09:44:43,204 - INFO - Video thread started with source: Camera
2025-11-25 09:44:43,204 - ERROR - ❌ No camera found!
2025-11-25 09:44:43,208 - ERROR - ❌ No camera found!
2025-11-25 09:44:43,401 - INFO - Video thread started with source: Camera
2025-11-25 09:44:43,402 - INFO - Video thread started with source: Camera
2025-11-25 09:44:43,402 - INFO - Frame 54 | PERCLOS: 0.42 | Yaw: 1.0° | Alerts: 2
2025-11-25 09:44:43,402 - ERROR - ❌ No camera found!
2025-11-25 09:44:43,403 - ERROR - ❌ No camera found!
2025-11-25 09:44:43,594 - INFO - Video thread started with source: Camera
2025-11-25 09:44:43,594 - INFO - Video thread started with source: Camera
2025-11-25 09:44:43,598 - ERROR - ❌ No camera found!
2025-11-25 09:44:43,599 - ERROR - ❌ No camera found!
2025-11-25 09:44:43,790 - INFO - Video thread started with source: Camera
2025-11-25 09:44:43,792 - ERROR - ❌ No camera found!
2025-11-25 09:44:43,796 - INFO - Video thread started with source: Camera
2025-11-25 09:44:43,804 - ERROR - ❌ No camera found!
2025-11-25 09:44:43,823 - INFO - Frame 56 | PERCLOS: 0.00 | Yaw: 3.2° | Alerts: 1
2025-11-25 09:44:44,015 - INFO - Video thread started with source: Camera
2025-11-25 09:44:44,018 - INFO - Video thread started with source: Camera
2025-11-25 09:44:44,019 - ERROR - ❌ No camera found!
2025-11-25 09:44:44,020 - ERROR - ❌ No camera found!
2025-11-25 09:44:44,226 - INFO - Video thread started with source: Camera
2025-11-25 09:44:44,226 - ERROR - ❌ No camera found!
2025-11-25 09:44:44,231 - INFO - Video thread started with source: Camera
2025-11-25 09:44:44,235 - ERROR - ❌ No camera found!
2025-11-25 09:44:44,248 - INFO - Frame 58 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 1
2025-11-25 09:44:44,433 - INFO - Video thread started with source: Camera
2025-11-25 09:44:44,433 - INFO - Video thread started with source: Camera
2025-11-25 09:44:44,435 - ERROR - ❌ No camera found!
2025-11-25 09:44:44,436 - ERROR - ❌ No camera found!
2025-11-25 09:44:44,637 - INFO - Video thread started with source: Camera
2025-11-25 09:44:44,638 - INFO - Video thread started with source: Camera
2025-11-25 09:44:44,642 - ERROR - ❌ No camera found!
2025-11-25 09:44:44,647 - ERROR - ❌ No camera found!
2025-11-25 09:44:44,846 - INFO - Video thread started with source: Camera
2025-11-25 09:44:44,846 - INFO - Video thread started with source: Camera
2025-11-25 09:44:44,848 - ERROR - ❌ No camera found!
2025-11-25 09:44:44,848 - ERROR - ❌ No camera found!
2025-11-25 09:44:44,864 - INFO - Frame 60 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 1
2025-11-25 09:44:45,071 - INFO - Video thread started with source: Camera
2025-11-25 09:44:45,071 - INFO - Video thread started with source: Camera
2025-11-25 09:44:45,074 - ERROR - ❌ No camera found!
2025-11-25 09:44:45,079 - ERROR - ❌ No camera found!
2025-11-25 09:44:45,287 - INFO - Video thread started with source: Camera
2025-11-25 09:44:45,290 - INFO - Video thread started with source: Camera
2025-11-25 09:44:45,291 - ERROR - ❌ No camera found!
2025-11-25 09:44:45,291 - INFO - Frame 62 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 1
2025-11-25 09:44:45,291 - ERROR - ❌ No camera found!
2025-11-25 09:44:45,488 - INFO - Video thread started with source: Camera
2025-11-25 09:44:45,489 - ERROR - ❌ No camera found!
2025-11-25 09:44:45,490 - INFO - Video thread started with source: Camera
2025-11-25 09:44:45,496 - ERROR - ❌ No camera found!
2025-11-25 09:44:45,690 - INFO - Video thread started with source: Camera
2025-11-25 09:44:45,690 - INFO - Video thread started with source: Camera
2025-11-25 09:44:45,692 - INFO - Frame 64 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 1
2025-11-25 09:44:45,692 - ERROR - ❌ No camera found!
2025-11-25 09:44:45,693 - ERROR - ❌ No camera found!
2025-11-25 09:44:45,890 - INFO - Video thread started with source: Camera
2025-11-25 09:44:45,891 - INFO - Video thread started with source: Camera
2025-11-25 09:44:45,892 - ERROR - ❌ No camera found!
2025-11-25 09:44:45,893 - ERROR - ❌ No camera found!
2025-11-25 09:44:46,101 - INFO - Video thread started with source: Camera
2025-11-25 09:44:46,103 - INFO - Video thread started with source: Camera
2025-11-25 09:44:46,105 - ERROR - ❌ No camera found!
2025-11-25 09:44:46,105 - ERROR - ❌ No camera found!
2025-11-25 09:44:46,301 - INFO - Frame 66 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 1
2025-11-25 09:44:46,306 - INFO - Video thread started with source: Camera
2025-11-25 09:44:46,307 - INFO - Video thread started with source: Camera
2025-11-25 09:44:46,307 - ERROR - ❌ No camera found!
2025-11-25 09:44:46,307 - ERROR - ❌ No camera found!
2025-11-25 09:44:46,510 - INFO - Video thread started with source: Camera
2025-11-25 09:44:46,510 - INFO - Video thread started with source: Camera
2025-11-25 09:44:46,511 - ERROR - ❌ No camera found!
2025-11-25 09:44:46,512 - ERROR - ❌ No camera found!
2025-11-25 09:44:46,548 - INFO - Frame 68 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 1
2025-11-25 09:44:46,730 - INFO - Video thread started with source: Camera
2025-11-25 09:44:46,733 - ERROR - ❌ No camera found!
2025-11-25 09:44:46,736 - INFO - Video thread started with source: Camera
2025-11-25 09:44:46,737 - ERROR - ❌ No camera found!
2025-11-25 09:44:46,949 - INFO - Video thread started with source: Camera
2025-11-25 09:44:46,950 - ERROR - ❌ No camera found!
2025-11-25 09:44:46,954 - INFO - Video thread started with source: Camera
2025-11-25 09:44:46,954 - INFO - Frame 70 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 1
2025-11-25 09:44:46,955 - ERROR - ❌ No camera found!
2025-11-25 09:44:47,164 - INFO - Video thread started with source: Camera
2025-11-25 09:44:47,164 - INFO - Video thread started with source: Camera
2025-11-25 09:44:47,165 - ERROR - ❌ No camera found!
2025-11-25 09:44:47,166 - ERROR - ❌ No camera found!
2025-11-25 09:44:47,367 - INFO - Video thread started with source: Camera
2025-11-25 09:44:47,369 - INFO - Video thread started with source: Camera
2025-11-25 09:44:47,369 - ERROR - ❌ No camera found!
2025-11-25 09:44:47,370 - ERROR - ❌ No camera found!
2025-11-25 09:44:47,574 - INFO - Frame 72 | PERCLOS: 0.00 | Yaw: 8.9° | Alerts: 0
2025-11-25 09:44:47,577 - INFO - Video thread started with source: Camera
2025-11-25 09:44:47,577 - INFO - Video thread started with source: Camera
2025-11-25 09:44:47,580 - ERROR - ❌ No camera found!
2025-11-25 09:44:47,580 - ERROR - ❌ No camera found!
2025-11-25 09:44:47,777 - INFO - Video thread started with source: Camera
2025-11-25 09:44:47,782 - INFO - Video thread started with source: Camera
2025-11-25 09:44:47,782 - ERROR - ❌ No camera found!
2025-11-25 09:44:47,789 - ERROR - ❌ No camera found!
2025-11-25 09:44:47,986 - INFO - Video thread started with source: Camera
2025-11-25 09:44:47,986 - INFO - Frame 74 | PERCLOS: 0.00 | Yaw: 9.4° | Alerts: 0
2025-11-25 09:44:47,987 - ERROR - ❌ No camera found!
2025-11-25 09:44:47,988 - INFO - Video thread started with source: Camera
2025-11-25 09:44:47,989 - ERROR - ❌ No camera found!
2025-11-25 09:44:48,207 - INFO - Video thread started with source: Camera
2025-11-25 09:44:48,207 - INFO - Video thread started with source: Camera
2025-11-25 09:44:48,208 - ERROR - ❌ No camera found!
2025-11-25 09:44:48,208 - ERROR - ❌ No camera found!
2025-11-25 09:44:48,240 - INFO - Frame 76 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:44:48,407 - INFO - Video thread started with source: Camera
2025-11-25 09:44:48,407 - INFO - Video thread started with source: Camera
2025-11-25 09:44:48,411 - ERROR - ❌ No camera found!
2025-11-25 09:44:48,411 - ERROR - ❌ No camera found!
2025-11-25 09:44:48,604 - INFO - Frame 78 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:44:48,610 - INFO - Video thread started with source: Camera
2025-11-25 09:44:48,615 - ERROR - ❌ No camera found!
2025-11-25 09:44:48,615 - INFO - Video thread started with source: Camera
2025-11-25 09:44:48,615 - ERROR - ❌ No camera found!
2025-11-25 09:44:48,795 - INFO - Video thread started with source: Camera
2025-11-25 09:44:48,800 - ERROR - ❌ No camera found!
2025-11-25 09:44:48,801 - INFO - Video thread started with source: Camera
2025-11-25 09:44:48,802 - ERROR - ❌ No camera found!
2025-11-25 09:44:48,991 - INFO - Video thread started with source: Camera
2025-11-25 09:44:48,995 - INFO - Video thread started with source: Camera
2025-11-25 09:44:48,996 - ERROR - ❌ No camera found!
2025-11-25 09:44:48,996 - INFO - Frame 80 | PERCLOS: 0.00 | Yaw: 6.8° | Alerts: 0
2025-11-25 09:44:48,997 - ERROR - ❌ No camera found!
2025-11-25 09:44:49,205 - INFO - Video thread started with source: Camera
2025-11-25 09:44:49,207 - ERROR - ❌ No camera found!
2025-11-25 09:44:49,208 - INFO - Video thread started with source: Camera
2025-11-25 09:44:49,208 - ERROR - ❌ No camera found!
2025-11-25 09:44:49,424 - INFO - Video thread started with source: Camera
2025-11-25 09:44:49,424 - INFO - Frame 82 | PERCLOS: 0.00 | Yaw: 5.1° | Alerts: 0
2025-11-25 09:44:49,424 - INFO - Video thread started with source: Camera
2025-11-25 09:44:49,426 - ERROR - ❌ No camera found!
2025-11-25 09:44:49,429 - ERROR - ❌ No camera found!
2025-11-25 09:44:49,625 - INFO - Video thread started with source: Camera
2025-11-25 09:44:49,627 - ERROR - ❌ No camera found!
2025-11-25 09:44:49,627 - INFO - Video thread started with source: Camera
2025-11-25 09:44:49,628 - ERROR - ❌ No camera found!
2025-11-25 09:44:49,825 - INFO - Video thread started with source: Camera
2025-11-25 09:44:49,825 - INFO - Video thread started with source: Camera
2025-11-25 09:44:49,831 - ERROR - ❌ No camera found!
2025-11-25 09:44:49,831 - ERROR - ❌ No camera found!
2025-11-25 09:44:50,022 - INFO - Frame 84 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 0
2025-11-25 09:44:50,027 - INFO - Video thread started with source: Camera
2025-11-25 09:44:50,030 - ERROR - ❌ No camera found!
2025-11-25 09:44:50,030 - INFO - Video thread started with source: Camera
2025-11-25 09:44:50,033 - ERROR - ❌ No camera found!
2025-11-25 09:44:50,228 - INFO - Video thread started with source: Camera
2025-11-25 09:44:50,232 - ERROR - ❌ No camera found!
2025-11-25 09:44:50,234 - INFO - Video thread started with source: Camera
2025-11-25 09:44:50,235 - ERROR - ❌ No camera found!
2025-11-25 09:44:50,460 - INFO - Video thread started with source: Camera
2025-11-25 09:44:50,460 - INFO - Video thread started with source: Camera
2025-11-25 09:44:50,464 - INFO - Frame 86 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 0
2025-11-25 09:44:50,465 - ERROR - ❌ No camera found!
2025-11-25 09:44:50,469 - ERROR - ❌ No camera found!
2025-11-25 09:44:50,679 - INFO - Video thread started with source: Camera
2025-11-25 09:44:50,681 - INFO - Video thread started with source: Camera
2025-11-25 09:44:50,682 - ERROR - ❌ No camera found!
2025-11-25 09:44:50,683 - ERROR - ❌ No camera found!
2025-11-25 09:44:50,720 - INFO - Frame 88 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:44:50,892 - INFO - Video thread started with source: Camera
2025-11-25 09:44:50,893 - INFO - Video thread started with source: Camera
2025-11-25 09:44:50,894 - ERROR - ❌ No camera found!
2025-11-25 09:44:50,897 - ERROR - ❌ No camera found!
2025-11-25 09:44:50,928 - INFO - Frame 90 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:44:51,103 - INFO - Video thread started with source: Camera
2025-11-25 09:44:51,108 - INFO - Video thread started with source: Camera
2025-11-25 09:44:51,108 - ERROR - ❌ No camera found!
2025-11-25 09:44:51,108 - ERROR - ❌ No camera found!
2025-11-25 09:44:51,144 - INFO - Frame 92 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:44:51,311 - INFO - Video thread started with source: Camera
2025-11-25 09:44:51,314 - INFO - Video thread started with source: Camera
2025-11-25 09:44:51,317 - ERROR - ❌ No camera found!
2025-11-25 09:44:51,318 - ERROR - ❌ No camera found!
2025-11-25 09:44:51,351 - INFO - Frame 94 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:44:51,501 - INFO - Video thread started with source: Camera
2025-11-25 09:44:51,501 - INFO - Video thread started with source: Camera
2025-11-25 09:44:51,506 - ERROR - ❌ No camera found!
2025-11-25 09:44:51,506 - ERROR - ❌ No camera found!
2025-11-25 09:44:51,694 - INFO - Video thread started with source: Camera
2025-11-25 09:44:51,695 - INFO - Video thread started with source: Camera
2025-11-25 09:44:51,696 - INFO - Frame 96 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:44:51,696 - ERROR - ❌ No camera found!
2025-11-25 09:44:51,700 - ERROR - ❌ No camera found!
2025-11-25 09:44:51,888 - INFO - Video thread started with source: Camera
2025-11-25 09:44:51,889 - ERROR - ❌ No camera found!
2025-11-25 09:44:51,890 - INFO - Video thread started with source: Camera
2025-11-25 09:44:51,894 - ERROR - ❌ No camera found!
2025-11-25 09:44:51,903 - INFO - Frame 98 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:44:52,091 - INFO - Video thread started with source: Camera
2025-11-25 09:44:52,091 - INFO - Video thread started with source: Camera
2025-11-25 09:44:52,092 - ERROR - ❌ No camera found!
2025-11-25 09:44:52,093 - ERROR - ❌ No camera found!
2025-11-25 09:44:52,265 - INFO - Frame 100 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:44:52,274 - INFO - Video thread started with source: Camera
2025-11-25 09:44:52,276 - ERROR - ❌ No camera found!
2025-11-25 09:44:52,277 - INFO - Video thread started with source: Camera
2025-11-25 09:44:52,279 - ERROR - ❌ No camera found!
2025-11-25 09:44:52,463 - INFO - Video thread started with source: Camera
2025-11-25 09:44:52,469 - INFO - Frame 102 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:44:52,470 - ERROR - ❌ No camera found!
2025-11-25 09:44:52,475 - INFO - Video thread started with source: Camera
2025-11-25 09:44:52,476 - ERROR - ❌ No camera found!
2025-11-25 09:44:52,652 - INFO - Video thread started with source: Camera
2025-11-25 09:44:52,652 - INFO - Video thread started with source: Camera
2025-11-25 09:44:52,654 - ERROR - ❌ No camera found!
2025-11-25 09:44:52,654 - ERROR - ❌ No camera found!
2025-11-25 09:44:52,870 - INFO - Video thread started with source: Camera
2025-11-25 09:44:52,871 - ERROR - ❌ No camera found!
2025-11-25 09:44:52,872 - INFO - Frame 104 | PERCLOS: 0.00 | Yaw: 9.3° | Alerts: 0
2025-11-25 09:44:52,877 - INFO - Video thread started with source: Camera
2025-11-25 09:44:52,878 - ERROR - ❌ No camera found!
2025-11-25 09:44:53,072 - INFO - Video thread started with source: Camera
2025-11-25 09:44:53,074 - ERROR - ❌ No camera found!
2025-11-25 09:44:53,080 - INFO - Video thread started with source: Camera
2025-11-25 09:44:53,083 - ERROR - ❌ No camera found!
2025-11-25 09:44:53,271 - INFO - Video thread started with source: Camera
2025-11-25 09:44:53,274 - INFO - Video thread started with source: Camera
2025-11-25 09:44:53,278 - ERROR - ❌ No camera found!
2025-11-25 09:44:53,280 - ERROR - ❌ No camera found!
2025-11-25 09:44:53,303 - INFO - Frame 106 | PERCLOS: 0.00 | Yaw: 6.9° | Alerts: 0
2025-11-25 09:44:53,484 - INFO - Video thread started with source: Camera
2025-11-25 09:44:53,484 - INFO - Video thread started with source: Camera
2025-11-25 09:44:53,486 - ERROR - ❌ No camera found!
2025-11-25 09:44:53,489 - ERROR - ❌ No camera found!
2025-11-25 09:44:53,691 - INFO - Video thread started with source: Camera
2025-11-25 09:44:53,694 - ERROR - ❌ No camera found!
2025-11-25 09:44:53,694 - INFO - Video thread started with source: Camera
2025-11-25 09:44:53,702 - ERROR - ❌ No camera found!
2025-11-25 09:44:53,891 - INFO - Frame 108 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 0
2025-11-25 09:44:53,897 - INFO - Video thread started with source: Camera
2025-11-25 09:44:53,899 - INFO - Video thread started with source: Camera
2025-11-25 09:44:53,900 - ERROR - ❌ No camera found!
2025-11-25 09:44:53,900 - ERROR - ❌ No camera found!
2025-11-25 09:44:54,109 - INFO - Video thread started with source: Camera
2025-11-25 09:44:54,109 - INFO - Video thread started with source: Camera
2025-11-25 09:44:54,114 - ERROR - ❌ No camera found!
2025-11-25 09:44:54,114 - ERROR - ❌ No camera found!
2025-11-25 09:44:54,325 - INFO - Video thread started with source: Camera
2025-11-25 09:44:54,327 - ERROR - ❌ No camera found!
2025-11-25 09:44:54,328 - INFO - Video thread started with source: Camera
2025-11-25 09:44:54,328 - INFO - Frame 110 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 0
2025-11-25 09:44:54,332 - ERROR - ❌ No camera found!
2025-11-25 09:44:54,532 - INFO - Video thread started with source: Camera
2025-11-25 09:44:54,532 - INFO - Video thread started with source: Camera
2025-11-25 09:44:54,535 - ERROR - ❌ No camera found!
2025-11-25 09:44:54,541 - ERROR - ❌ No camera found!
2025-11-25 09:44:54,740 - INFO - Frame 112 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 0
2025-11-25 09:44:54,740 - INFO - Video thread started with source: Camera
2025-11-25 09:44:54,743 - INFO - Video thread started with source: Camera
2025-11-25 09:44:54,744 - ERROR - ❌ No camera found!
2025-11-25 09:44:54,746 - ERROR - ❌ No camera found!
2025-11-25 09:44:54,941 - INFO - Frame 114 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:44:54,941 - INFO - Video thread started with source: Camera
2025-11-25 09:44:54,942 - INFO - Video thread started with source: Camera
2025-11-25 09:44:54,942 - ERROR - ❌ No camera found!
2025-11-25 09:44:54,942 - ERROR - ❌ No camera found!
2025-11-25 09:44:55,144 - INFO - Video thread started with source: Camera
2025-11-25 09:44:55,147 - ERROR - ❌ No camera found!
2025-11-25 09:44:55,147 - INFO - Video thread started with source: Camera
2025-11-25 09:44:55,149 - ERROR - ❌ No camera found!
2025-11-25 09:44:55,338 - INFO - Frame 116 | PERCLOS: 0.00 | Yaw: 11.2° | Alerts: 0
2025-11-25 09:44:55,339 - INFO - Video thread started with source: Camera
2025-11-25 09:44:55,339 - INFO - Video thread started with source: Camera
2025-11-25 09:44:55,342 - ERROR - ❌ No camera found!
2025-11-25 09:44:55,342 - ERROR - ❌ No camera found!
2025-11-25 09:44:55,563 - INFO - Video thread started with source: Camera
2025-11-25 09:44:55,565 - ERROR - ❌ No camera found!
2025-11-25 09:44:55,565 - INFO - Video thread started with source: Camera
2025-11-25 09:44:55,571 - ERROR - ❌ No camera found!
2025-11-25 09:44:55,779 - INFO - Video thread started with source: Camera
2025-11-25 09:44:55,779 - INFO - Video thread started with source: Camera
2025-11-25 09:44:55,782 - ERROR - ❌ No camera found!
2025-11-25 09:44:55,784 - INFO - Frame 118 | PERCLOS: 0.00 | Yaw: 10.7° | Alerts: 0
2025-11-25 09:44:55,784 - ERROR - ❌ No camera found!
2025-11-25 09:44:55,972 - INFO - Video thread started with source: Camera
2025-11-25 09:44:55,975 - INFO - Video thread started with source: Camera
2025-11-25 09:44:55,977 - ERROR - ❌ No camera found!
2025-11-25 09:44:55,981 - ERROR - ❌ No camera found!
2025-11-25 09:44:56,192 - INFO - Video thread started with source: Camera
2025-11-25 09:44:56,192 - ERROR - ❌ No camera found!
2025-11-25 09:44:56,204 - INFO - Video thread started with source: Camera
2025-11-25 09:44:56,205 - ERROR - ❌ No camera found!
2025-11-25 09:44:56,341 - INFO - Frame 120 | PERCLOS: 0.00 | Yaw: 11.5° | Alerts: 0
2025-11-25 09:44:56,400 - INFO - Video thread started with source: Camera
2025-11-25 09:44:56,400 - INFO - Video thread started with source: Camera
2025-11-25 09:44:56,401 - ERROR - ❌ No camera found!
2025-11-25 09:44:56,407 - ERROR - ❌ No camera found!
2025-11-25 09:44:56,604 - INFO - Video thread started with source: Camera
2025-11-25 09:44:56,609 - ERROR - ❌ No camera found!
2025-11-25 09:44:56,614 - INFO - Video thread started with source: Camera
2025-11-25 09:44:56,621 - ERROR - ❌ No camera found!
2025-11-25 09:44:56,815 - INFO - Frame 122 | PERCLOS: 0.00 | Yaw: 11.5° | Alerts: 0
2025-11-25 09:44:56,821 - INFO - Video thread started with source: Camera
2025-11-25 09:44:56,821 - INFO - Video thread started with source: Camera
2025-11-25 09:44:56,823 - ERROR - ❌ No camera found!
2025-11-25 09:44:56,823 - ERROR - ❌ No camera found!
2025-11-25 09:44:57,026 - INFO - Video thread started with source: Camera
2025-11-25 09:44:57,028 - ERROR - ❌ No camera found!
2025-11-25 09:44:57,031 - INFO - Video thread started with source: Camera
2025-11-25 09:44:57,035 - ERROR - ❌ No camera found!
2025-11-25 09:44:57,237 - INFO - Video thread started with source: Camera
2025-11-25 09:44:57,237 - INFO - Video thread started with source: Camera
2025-11-25 09:44:57,242 - ERROR - ❌ No camera found!
2025-11-25 09:44:57,242 - ERROR - ❌ No camera found!
2025-11-25 09:44:57,267 - INFO - Frame 124 | PERCLOS: 0.00 | Yaw: 9.2° | Alerts: 0
2025-11-25 09:44:57,443 - INFO - Video thread started with source: Camera
2025-11-25 09:44:57,443 - INFO - Video thread started with source: Camera
2025-11-25 09:44:57,444 - ERROR - ❌ No camera found!
2025-11-25 09:44:57,444 - ERROR - ❌ No camera found!
2025-11-25 09:44:57,637 - INFO - Video thread started with source: Camera
2025-11-25 09:44:57,641 - INFO - Video thread started with source: Camera
2025-11-25 09:44:57,645 - ERROR - ❌ No camera found!
2025-11-25 09:44:57,647 - ERROR - ❌ No camera found!
2025-11-25 09:44:57,855 - INFO - Video thread started with source: Camera
2025-11-25 09:44:57,855 - INFO - Video thread started with source: Camera
2025-11-25 09:44:57,855 - ERROR - ❌ No camera found!
2025-11-25 09:44:57,855 - ERROR - ❌ No camera found!
2025-11-25 09:44:57,869 - INFO - Frame 126 | PERCLOS: 0.00 | Yaw: 7.4° | Alerts: 1
2025-11-25 09:44:58,066 - INFO - Video thread started with source: Camera
2025-11-25 09:44:58,067 - INFO - Video thread started with source: Camera
2025-11-25 09:44:58,070 - ERROR - ❌ No camera found!
2025-11-25 09:44:58,073 - ERROR - ❌ No camera found!
2025-11-25 09:44:58,271 - INFO - Video thread started with source: Camera
2025-11-25 09:44:58,273 - ERROR - ❌ No camera found!
2025-11-25 09:44:58,276 - INFO - Video thread started with source: Camera
2025-11-25 09:44:58,282 - ERROR - ❌ No camera found!
2025-11-25 09:44:58,303 - INFO - Frame 128 | PERCLOS: 0.00 | Yaw: 5.2° | Alerts: 1
2025-11-25 09:44:58,481 - INFO - Video thread started with source: Camera
2025-11-25 09:44:58,483 - INFO - Video thread started with source: Camera
2025-11-25 09:44:58,486 - ERROR - ❌ No camera found!
2025-11-25 09:44:58,486 - ERROR - ❌ No camera found!
2025-11-25 09:44:58,687 - INFO - Video thread started with source: Camera
2025-11-25 09:44:58,690 - INFO - Video thread started with source: Camera
2025-11-25 09:44:58,692 - ERROR - ❌ No camera found!
2025-11-25 09:44:58,695 - ERROR - ❌ No camera found!
2025-11-25 09:44:58,707 - INFO - Frame 130 | PERCLOS: 0.00 | Yaw: 5.0° | Alerts: 1
2025-11-25 09:44:58,895 - INFO - Video thread started with source: Camera
2025-11-25 09:44:58,895 - INFO - Video thread started with source: Camera
2025-11-25 09:44:58,895 - ERROR - ❌ No camera found!
2025-11-25 09:44:58,897 - ERROR - ❌ No camera found!
2025-11-25 09:44:59,102 - INFO - Video thread started with source: Camera
2025-11-25 09:44:59,105 - INFO - Video thread started with source: Camera
2025-11-25 09:44:59,106 - ERROR - ❌ No camera found!
2025-11-25 09:44:59,107 - ERROR - ❌ No camera found!
2025-11-25 09:44:59,323 - INFO - Video thread started with source: Camera
2025-11-25 09:44:59,324 - INFO - Video thread started with source: Camera
2025-11-25 09:44:59,325 - ERROR - ❌ No camera found!
2025-11-25 09:44:59,328 - ERROR - ❌ No camera found!
2025-11-25 09:44:59,339 - INFO - Frame 132 | PERCLOS: 0.00 | Yaw: 3.8° | Alerts: 1
2025-11-25 09:44:59,549 - INFO - Video thread started with source: Camera
2025-11-25 09:44:59,553 - ERROR - ❌ No camera found!
2025-11-25 09:44:59,553 - INFO - Video thread started with source: Camera
2025-11-25 09:44:59,556 - ERROR - ❌ No camera found!
2025-11-25 09:44:59,757 - INFO - Video thread started with source: Camera
2025-11-25 09:44:59,758 - INFO - Video thread started with source: Camera
2025-11-25 09:44:59,760 - ERROR - ❌ No camera found!
2025-11-25 09:44:59,761 - ERROR - ❌ No camera found!
2025-11-25 09:44:59,762 - INFO - Frame 134 | PERCLOS: 0.00 | Yaw: 2.7° | Alerts: 1
2025-11-25 09:44:59,975 - INFO - Video thread started with source: Camera
2025-11-25 09:44:59,979 - ERROR - ❌ No camera found!
2025-11-25 09:44:59,981 - INFO - Video thread started with source: Camera
2025-11-25 09:44:59,986 - ERROR - ❌ No camera found!
2025-11-25 09:45:00,181 - INFO - Video thread started with source: Camera
2025-11-25 09:45:00,184 - INFO - Video thread started with source: Camera
2025-11-25 09:45:00,184 - ERROR - ❌ No camera found!
2025-11-25 09:45:00,187 - ERROR - ❌ No camera found!
2025-11-25 09:45:00,203 - INFO - Frame 136 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 2
2025-11-25 09:45:00,390 - INFO - Video thread started with source: Camera
2025-11-25 09:45:00,391 - ERROR - ❌ No camera found!
2025-11-25 09:45:00,391 - INFO - Video thread started with source: Camera
2025-11-25 09:45:00,393 - ERROR - ❌ No camera found!
2025-11-25 09:45:00,595 - INFO - Video thread started with source: Camera
2025-11-25 09:45:00,598 - ERROR - ❌ No camera found!
2025-11-25 09:45:00,598 - INFO - Video thread started with source: Camera
2025-11-25 09:45:00,599 - ERROR - ❌ No camera found!
2025-11-25 09:45:00,796 - INFO - Video thread started with source: Camera
2025-11-25 09:45:00,799 - ERROR - ❌ No camera found!
2025-11-25 09:45:00,799 - INFO - Video thread started with source: Camera
2025-11-25 09:45:00,801 - ERROR - ❌ No camera found!
2025-11-25 09:45:00,802 - INFO - Frame 138 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 2
2025-11-25 09:45:01,017 - INFO - Video thread started with source: Camera
2025-11-25 09:45:01,018 - INFO - Video thread started with source: Camera
2025-11-25 09:45:01,020 - ERROR - ❌ No camera found!
2025-11-25 09:45:01,021 - ERROR - ❌ No camera found!
2025-11-25 09:45:01,224 - INFO - Video thread started with source: Camera
2025-11-25 09:45:01,227 - INFO - Video thread started with source: Camera
2025-11-25 09:45:01,228 - ERROR - ❌ No camera found!
2025-11-25 09:45:01,232 - ERROR - ❌ No camera found!
2025-11-25 09:45:01,241 - INFO - Frame 140 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 2
2025-11-25 09:45:01,443 - INFO - Video thread started with source: Camera
2025-11-25 09:45:01,447 - ERROR - ❌ No camera found!
2025-11-25 09:45:01,447 - INFO - Video thread started with source: Camera
2025-11-25 09:45:01,452 - ERROR - ❌ No camera found!
2025-11-25 09:45:01,651 - INFO - Video thread started with source: Camera
2025-11-25 09:45:01,651 - INFO - Video thread started with source: Camera
2025-11-25 09:45:01,652 - ERROR - ❌ No camera found!
2025-11-25 09:45:01,655 - ERROR - ❌ No camera found!
2025-11-25 09:45:01,665 - INFO - Frame 142 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 2
2025-11-25 09:45:01,852 - INFO - Video thread started with source: Camera
2025-11-25 09:45:01,855 - INFO - Video thread started with source: Camera
2025-11-25 09:45:01,857 - ERROR - ❌ No camera found!
2025-11-25 09:45:01,858 - ERROR - ❌ No camera found!
2025-11-25 09:45:02,057 - INFO - Video thread started with source: Camera
2025-11-25 09:45:02,062 - ERROR - ❌ No camera found!
2025-11-25 09:45:02,062 - INFO - Video thread started with source: Camera
2025-11-25 09:45:02,068 - ERROR - ❌ No camera found!
2025-11-25 09:45:02,273 - INFO - Video thread started with source: Camera
2025-11-25 09:45:02,273 - INFO - Video thread started with source: Camera
2025-11-25 09:45:02,275 - ERROR - ❌ No camera found!
2025-11-25 09:45:02,281 - ERROR - ❌ No camera found!
2025-11-25 09:45:02,291 - INFO - Frame 144 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 2
2025-11-25 09:45:02,570 - INFO - Video thread started with source: Camera
2025-11-25 09:45:02,572 - INFO - Video thread started with source: Camera
2025-11-25 09:45:02,576 - ERROR - ❌ No camera found!
2025-11-25 09:45:02,576 - ERROR - ❌ No camera found!
2025-11-25 09:45:02,769 - INFO - Video thread started with source: Camera
2025-11-25 09:45:02,769 - ERROR - ❌ No camera found!
2025-11-25 09:45:02,769 - INFO - Video thread started with source: Camera
2025-11-25 09:45:02,769 - ERROR - ❌ No camera found!
2025-11-25 09:45:02,773 - INFO - Frame 146 | PERCLOS: 0.00 | Yaw: 0.1° | Alerts: 2
2025-11-25 09:45:02,972 - INFO - Video thread started with source: Camera
2025-11-25 09:45:02,972 - ERROR - ❌ No camera found!
2025-11-25 09:45:02,978 - INFO - Video thread started with source: Camera
2025-11-25 09:45:02,980 - ERROR - ❌ No camera found!
2025-11-25 09:45:03,185 - INFO - Video thread started with source: Camera
2025-11-25 09:45:03,186 - INFO - Video thread started with source: Camera
2025-11-25 09:45:03,191 - ERROR - ❌ No camera found!
2025-11-25 09:45:03,192 - ERROR - ❌ No camera found!
2025-11-25 09:45:03,219 - INFO - Frame 148 | PERCLOS: 0.00 | Yaw: -0.7° | Alerts: 1
2025-11-25 09:45:03,385 - INFO - Video thread started with source: Camera
2025-11-25 09:45:03,385 - INFO - Video thread started with source: Camera
2025-11-25 09:45:03,387 - ERROR - ❌ No camera found!
2025-11-25 09:45:03,389 - ERROR - ❌ No camera found!
2025-11-25 09:45:03,578 - INFO - Video thread started with source: Camera
2025-11-25 09:45:03,579 - INFO - Video thread started with source: Camera
2025-11-25 09:45:03,580 - ERROR - ❌ No camera found!
2025-11-25 09:45:03,580 - ERROR - ❌ No camera found!
2025-11-25 09:45:03,794 - INFO - Video thread started with source: Camera
2025-11-25 09:45:03,794 - INFO - Video thread started with source: Camera
2025-11-25 09:45:03,795 - ERROR - ❌ No camera found!
2025-11-25 09:45:03,795 - ERROR - ❌ No camera found!
2025-11-25 09:45:03,809 - INFO - Frame 150 | PERCLOS: 0.00 | Yaw: -1.0° | Alerts: 1
2025-11-25 09:45:04,009 - INFO - Video thread started with source: Camera
2025-11-25 09:45:04,010 - INFO - Video thread started with source: Camera
2025-11-25 09:45:04,011 - ERROR - ❌ No camera found!
2025-11-25 09:45:04,011 - ERROR - ❌ No camera found!
2025-11-25 09:45:04,228 - INFO - Video thread started with source: Camera
2025-11-25 09:45:04,231 - INFO - Video thread started with source: Camera
2025-11-25 09:45:04,232 - ERROR - ❌ No camera found!
2025-11-25 09:45:04,234 - ERROR - ❌ No camera found!
2025-11-25 09:45:04,234 - INFO - Frame 152 | PERCLOS: 0.00 | Yaw: -0.8° | Alerts: 1
2025-11-25 09:45:04,430 - INFO - Video thread started with source: Camera
2025-11-25 09:45:04,431 - INFO - Video thread started with source: Camera
2025-11-25 09:45:04,431 - ERROR - ❌ No camera found!
2025-11-25 09:45:04,434 - ERROR - ❌ No camera found!
2025-11-25 09:45:04,630 - INFO - Video thread started with source: Camera
2025-11-25 09:45:04,632 - INFO - Video thread started with source: Camera
2025-11-25 09:45:04,635 - ERROR - ❌ No camera found!
2025-11-25 09:45:04,635 - ERROR - ❌ No camera found!
2025-11-25 09:45:04,635 - INFO - Frame 154 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 1
2025-11-25 09:45:04,847 - INFO - Video thread started with source: Camera
2025-11-25 09:45:04,852 - ERROR - ❌ No camera found!
2025-11-25 09:45:04,852 - INFO - Video thread started with source: Camera
2025-11-25 09:45:04,853 - ERROR - ❌ No camera found!
2025-11-25 09:45:05,048 - INFO - Video thread started with source: Camera
2025-11-25 09:45:05,048 - INFO - Video thread started with source: Camera
2025-11-25 09:45:05,052 - ERROR - ❌ No camera found!
2025-11-25 09:45:05,053 - ERROR - ❌ No camera found!
2025-11-25 09:45:05,249 - INFO - Frame 156 | PERCLOS: 0.00 | Yaw: -1.1° | Alerts: 1
2025-11-25 09:45:05,254 - INFO - Video thread started with source: Camera
2025-11-25 09:45:05,255 - INFO - Video thread started with source: Camera
2025-11-25 09:45:05,255 - ERROR - ❌ No camera found!
2025-11-25 09:45:05,256 - ERROR - ❌ No camera found!
2025-11-25 09:45:05,457 - INFO - Video thread started with source: Camera
2025-11-25 09:45:05,460 - INFO - Video thread started with source: Camera
2025-11-25 09:45:05,463 - ERROR - ❌ No camera found!
2025-11-25 09:45:05,464 - ERROR - ❌ No camera found!
2025-11-25 09:45:05,661 - INFO - Video thread started with source: Camera
2025-11-25 09:45:05,662 - INFO - Frame 158 | PERCLOS: 0.00 | Yaw: 0.4° | Alerts: 1
2025-11-25 09:45:05,662 - ERROR - ❌ No camera found!
2025-11-25 09:45:05,662 - INFO - Video thread started with source: Camera
2025-11-25 09:45:05,663 - ERROR - ❌ No camera found!
2025-11-25 09:45:05,857 - INFO - Video thread started with source: Camera
2025-11-25 09:45:05,860 - ERROR - ❌ No camera found!
2025-11-25 09:45:05,861 - INFO - Video thread started with source: Camera
2025-11-25 09:45:05,862 - ERROR - ❌ No camera found!
2025-11-25 09:45:06,059 - INFO - Video thread started with source: Camera
2025-11-25 09:45:06,060 - ERROR - ❌ No camera found!
2025-11-25 09:45:06,065 - INFO - Video thread started with source: Camera
2025-11-25 09:45:06,067 - ERROR - ❌ No camera found!
2025-11-25 09:45:06,091 - INFO - Frame 160 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 1
2025-11-25 09:45:06,281 - INFO - Video thread started with source: Camera
2025-11-25 09:45:06,283 - INFO - Video thread started with source: Camera
2025-11-25 09:45:06,287 - ERROR - ❌ No camera found!
2025-11-25 09:45:06,287 - ERROR - ❌ No camera found!
2025-11-25 09:45:06,488 - INFO - Video thread started with source: Camera
2025-11-25 09:45:06,491 - ERROR - ❌ No camera found!
2025-11-25 09:45:06,493 - INFO - Video thread started with source: Camera
2025-11-25 09:45:06,499 - ERROR - ❌ No camera found!
2025-11-25 09:45:06,704 - INFO - Video thread started with source: Camera
2025-11-25 09:45:06,708 - INFO - Video thread started with source: Camera
2025-11-25 09:45:06,709 - ERROR - ❌ No camera found!
2025-11-25 09:45:06,709 - ERROR - ❌ No camera found!
2025-11-25 09:45:06,724 - INFO - Frame 162 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 1
2025-11-25 09:45:06,921 - INFO - Video thread started with source: Camera
2025-11-25 09:45:06,923 - ERROR - ❌ No camera found!
2025-11-25 09:45:06,924 - INFO - Video thread started with source: Camera
2025-11-25 09:45:06,925 - ERROR - ❌ No camera found!
2025-11-25 09:45:07,132 - INFO - Video thread started with source: Camera
2025-11-25 09:45:07,132 - INFO - Video thread started with source: Camera
2025-11-25 09:45:07,133 - INFO - Frame 164 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-25 09:45:07,134 - ERROR - ❌ No camera found!
2025-11-25 09:45:07,134 - ERROR - ❌ No camera found!
2025-11-25 09:45:07,354 - INFO - Video thread started with source: Camera
2025-11-25 09:45:07,354 - INFO - Video thread started with source: Camera
2025-11-25 09:45:07,355 - ERROR - ❌ No camera found!
2025-11-25 09:45:07,355 - ERROR - ❌ No camera found!
2025-11-25 09:45:07,549 - INFO - Video thread started with source: Camera
2025-11-25 09:45:07,550 - INFO - Video thread started with source: Camera
2025-11-25 09:45:07,550 - INFO - Frame 166 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-25 09:45:07,550 - ERROR - ❌ No camera found!
2025-11-25 09:45:07,553 - ERROR - ❌ No camera found!
2025-11-25 09:45:07,754 - INFO - Video thread started with source: Camera
2025-11-25 09:45:07,758 - ERROR - ❌ No camera found!
2025-11-25 09:45:07,760 - INFO - Video thread started with source: Camera
2025-11-25 09:45:07,761 - ERROR - ❌ No camera found!
2025-11-25 09:45:07,974 - INFO - Video thread started with source: Camera
2025-11-25 09:45:07,975 - INFO - Video thread started with source: Camera
2025-11-25 09:45:07,979 - ERROR - ❌ No camera found!
2025-11-25 09:45:07,979 - ERROR - ❌ No camera found!
2025-11-25 09:45:08,157 - INFO - Frame 168 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 0
2025-11-25 09:45:08,165 - INFO - Video thread started with source: Camera
2025-11-25 09:45:08,166 - INFO - Video thread started with source: Camera
2025-11-25 09:45:08,167 - ERROR - ❌ No camera found!
2025-11-25 09:45:08,169 - ERROR - ❌ No camera found!
2025-11-25 09:45:08,361 - INFO - Video thread started with source: Camera
2025-11-25 09:45:08,361 - INFO - Video thread started with source: Camera
2025-11-25 09:45:08,365 - ERROR - ❌ No camera found!
2025-11-25 09:45:08,366 - ERROR - ❌ No camera found!
2025-11-25 09:45:08,558 - INFO - Frame 170 | PERCLOS: 0.00 | Yaw: 3.4° | Alerts: 0
2025-11-25 09:45:08,560 - INFO - Video thread started with source: Camera
2025-11-25 09:45:08,560 - INFO - Video thread started with source: Camera
2025-11-25 09:45:08,561 - ERROR - ❌ No camera found!
2025-11-25 09:45:08,562 - ERROR - ❌ No camera found!
2025-11-25 09:45:08,776 - INFO - Video thread started with source: Camera
2025-11-25 09:45:08,777 - INFO - Video thread started with source: Camera
2025-11-25 09:45:08,780 - ERROR - ❌ No camera found!
2025-11-25 09:45:08,781 - ERROR - ❌ No camera found!
2025-11-25 09:45:08,994 - INFO - Video thread started with source: Camera
2025-11-25 09:45:08,996 - INFO - Frame 172 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 0
2025-11-25 09:45:08,996 - ERROR - ❌ No camera found!
2025-11-25 09:45:09,005 - INFO - Video thread started with source: Camera
2025-11-25 09:45:09,006 - ERROR - ❌ No camera found!
2025-11-25 09:45:09,196 - INFO - Video thread started with source: Camera
2025-11-25 09:45:09,198 - INFO - Video thread started with source: Camera
2025-11-25 09:45:09,201 - ERROR - ❌ No camera found!
2025-11-25 09:45:09,201 - ERROR - ❌ No camera found!
2025-11-25 09:45:09,231 - INFO - Frame 174 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:09,403 - INFO - Video thread started with source: Camera
2025-11-25 09:45:09,404 - INFO - Video thread started with source: Camera
2025-11-25 09:45:09,404 - ERROR - ❌ No camera found!
2025-11-25 09:45:09,405 - ERROR - ❌ No camera found!
2025-11-25 09:45:09,610 - INFO - Video thread started with source: Camera
2025-11-25 09:45:09,612 - INFO - Frame 176 | PERCLOS: 0.00 | Yaw: 10.8° | Alerts: 0
2025-11-25 09:45:09,614 - ERROR - ❌ No camera found!
2025-11-25 09:45:09,615 - INFO - Video thread started with source: Camera
2025-11-25 09:45:09,620 - ERROR - ❌ No camera found!
2025-11-25 09:45:09,812 - INFO - Video thread started with source: Camera
2025-11-25 09:45:09,812 - INFO - Video thread started with source: Camera
2025-11-25 09:45:09,813 - ERROR - ❌ No camera found!
2025-11-25 09:45:09,814 - ERROR - ❌ No camera found!
2025-11-25 09:45:10,026 - INFO - Video thread started with source: Camera
2025-11-25 09:45:10,027 - ERROR - ❌ No camera found!
2025-11-25 09:45:10,028 - INFO - Video thread started with source: Camera
2025-11-25 09:45:10,030 - ERROR - ❌ No camera found!
2025-11-25 09:45:10,031 - INFO - Frame 178 | PERCLOS: 0.00 | Yaw: 8.7° | Alerts: 0
2025-11-25 09:45:10,225 - INFO - Video thread started with source: Camera
2025-11-25 09:45:10,228 - ERROR - ❌ No camera found!
2025-11-25 09:45:10,231 - INFO - Video thread started with source: Camera
2025-11-25 09:45:10,237 - ERROR - ❌ No camera found!
2025-11-25 09:45:10,426 - INFO - Video thread started with source: Camera
2025-11-25 09:45:10,428 - ERROR - ❌ No camera found!
2025-11-25 09:45:10,429 - INFO - Video thread started with source: Camera
2025-11-25 09:45:10,431 - ERROR - ❌ No camera found!
2025-11-25 09:45:10,468 - INFO - Frame 180 | PERCLOS: 0.00 | Yaw: 9.0° | Alerts: 0
2025-11-25 09:45:10,645 - INFO - Video thread started with source: Camera
2025-11-25 09:45:10,645 - INFO - Video thread started with source: Camera
2025-11-25 09:45:10,647 - ERROR - ❌ No camera found!
2025-11-25 09:45:10,650 - ERROR - ❌ No camera found!
2025-11-25 09:45:10,849 - INFO - Video thread started with source: Camera
2025-11-25 09:45:10,849 - INFO - Video thread started with source: Camera
2025-11-25 09:45:10,853 - ERROR - ❌ No camera found!
2025-11-25 09:45:10,853 - ERROR - ❌ No camera found!
2025-11-25 09:45:10,881 - INFO - Frame 182 | PERCLOS: 0.00 | Yaw: 8.9° | Alerts: 0
2025-11-25 09:45:11,056 - INFO - Video thread started with source: Camera
2025-11-25 09:45:11,061 - ERROR - ❌ No camera found!
2025-11-25 09:45:11,062 - INFO - Video thread started with source: Camera
2025-11-25 09:45:11,062 - ERROR - ❌ No camera found!
2025-11-25 09:45:11,258 - INFO - Video thread started with source: Camera
2025-11-25 09:45:11,263 - ERROR - ❌ No camera found!
2025-11-25 09:45:11,263 - INFO - Frame 184 | PERCLOS: 0.00 | Yaw: 8.6° | Alerts: 0
2025-11-25 09:45:11,267 - INFO - Video thread started with source: Camera
2025-11-25 09:45:11,267 - ERROR - ❌ No camera found!
2025-11-25 09:45:11,456 - INFO - Video thread started with source: Camera
2025-11-25 09:45:11,458 - ERROR - ❌ No camera found!
2025-11-25 09:45:11,460 - INFO - Video thread started with source: Camera
2025-11-25 09:45:11,462 - ERROR - ❌ No camera found!
2025-11-25 09:45:11,496 - INFO - Frame 186 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:11,677 - INFO - Video thread started with source: Camera
2025-11-25 09:45:11,677 - INFO - Video thread started with source: Camera
2025-11-25 09:45:11,679 - ERROR - ❌ No camera found!
2025-11-25 09:45:11,680 - ERROR - ❌ No camera found!
2025-11-25 09:45:11,863 - INFO - Video thread started with source: Camera
2025-11-25 09:45:11,864 - ERROR - ❌ No camera found!
2025-11-25 09:45:11,869 - INFO - Video thread started with source: Camera
2025-11-25 09:45:11,873 - ERROR - ❌ No camera found!
2025-11-25 09:45:11,896 - INFO - Frame 188 | PERCLOS: 0.35 | Yaw: 8.3° | Alerts: 1
2025-11-25 09:45:12,085 - INFO - Video thread started with source: Camera
2025-11-25 09:45:12,089 - INFO - Video thread started with source: Camera
2025-11-25 09:45:12,089 - ERROR - ❌ No camera found!
2025-11-25 09:45:12,090 - ERROR - ❌ No camera found!
2025-11-25 09:45:12,300 - INFO - Video thread started with source: Camera
2025-11-25 09:45:12,301 - INFO - Video thread started with source: Camera
2025-11-25 09:45:12,302 - ERROR - ❌ No camera found!
2025-11-25 09:45:12,302 - INFO - Frame 190 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 0
2025-11-25 09:45:12,302 - ERROR - ❌ No camera found!
2025-11-25 09:45:12,505 - INFO - Video thread started with source: Camera
2025-11-25 09:45:12,511 - ERROR - ❌ No camera found!
2025-11-25 09:45:12,514 - INFO - Video thread started with source: Camera
2025-11-25 09:45:12,516 - ERROR - ❌ No camera found!
2025-11-25 09:45:12,739 - INFO - Video thread started with source: Camera
2025-11-25 09:45:12,739 - INFO - Video thread started with source: Camera
2025-11-25 09:45:12,740 - INFO - Frame 192 | PERCLOS: 0.00 | Yaw: 6.2° | Alerts: 0
2025-11-25 09:45:12,743 - ERROR - ❌ No camera found!
2025-11-25 09:45:12,744 - ERROR - ❌ No camera found!
2025-11-25 09:45:12,944 - INFO - Video thread started with source: Camera
2025-11-25 09:45:12,945 - INFO - Video thread started with source: Camera
2025-11-25 09:45:12,945 - ERROR - ❌ No camera found!
2025-11-25 09:45:12,950 - ERROR - ❌ No camera found!
2025-11-25 09:45:13,149 - INFO - Video thread started with source: Camera
2025-11-25 09:45:13,151 - INFO - Video thread started with source: Camera
2025-11-25 09:45:13,152 - ERROR - ❌ No camera found!
2025-11-25 09:45:13,152 - INFO - Frame 194 | PERCLOS: 0.00 | Yaw: 5.8° | Alerts: 0
2025-11-25 09:45:13,153 - ERROR - ❌ No camera found!
2025-11-25 09:45:13,352 - INFO - Video thread started with source: Camera
2025-11-25 09:45:13,355 - INFO - Video thread started with source: Camera
2025-11-25 09:45:13,356 - ERROR - ❌ No camera found!
2025-11-25 09:45:13,358 - ERROR - ❌ No camera found!
2025-11-25 09:45:13,558 - INFO - Video thread started with source: Camera
2025-11-25 09:45:13,559 - INFO - Frame 196 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 0
2025-11-25 09:45:13,559 - INFO - Video thread started with source: Camera
2025-11-25 09:45:13,560 - ERROR - ❌ No camera found!
2025-11-25 09:45:13,562 - ERROR - ❌ No camera found!
2025-11-25 09:45:13,760 - INFO - Video thread started with source: Camera
2025-11-25 09:45:13,760 - INFO - Video thread started with source: Camera
2025-11-25 09:45:13,764 - ERROR - ❌ No camera found!
2025-11-25 09:45:13,766 - ERROR - ❌ No camera found!
2025-11-25 09:45:13,973 - INFO - Video thread started with source: Camera
2025-11-25 09:45:13,977 - INFO - Video thread started with source: Camera
2025-11-25 09:45:13,980 - ERROR - ❌ No camera found!
2025-11-25 09:45:13,980 - ERROR - ❌ No camera found!
2025-11-25 09:45:14,169 - INFO - Frame 198 | PERCLOS: 0.00 | Yaw: 10.6° | Alerts: 0
2025-11-25 09:45:14,174 - INFO - Video thread started with source: Camera
2025-11-25 09:45:14,177 - ERROR - ❌ No camera found!
2025-11-25 09:45:14,186 - INFO - Video thread started with source: Camera
2025-11-25 09:45:14,187 - ERROR - ❌ No camera found!
2025-11-25 09:45:14,388 - INFO - Video thread started with source: Camera
2025-11-25 09:45:14,390 - INFO - Frame 200 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:14,390 - INFO - Video thread started with source: Camera
2025-11-25 09:45:14,390 - ERROR - ❌ No camera found!
2025-11-25 09:45:14,396 - ERROR - ❌ No camera found!
2025-11-25 09:45:14,577 - INFO - Video thread started with source: Camera
2025-11-25 09:45:14,578 - INFO - Video thread started with source: Camera
2025-11-25 09:45:14,580 - INFO - Frame 202 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:14,582 - ERROR - ❌ No camera found!
2025-11-25 09:45:14,582 - ERROR - ❌ No camera found!
2025-11-25 09:45:14,757 - INFO - Video thread started with source: Camera
2025-11-25 09:45:14,760 - INFO - Video thread started with source: Camera
2025-11-25 09:45:14,760 - ERROR - ❌ No camera found!
2025-11-25 09:45:14,762 - ERROR - ❌ No camera found!
2025-11-25 09:45:14,795 - INFO - Frame 204 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:14,963 - INFO - Video thread started with source: Camera
2025-11-25 09:45:14,963 - INFO - Video thread started with source: Camera
2025-11-25 09:45:14,964 - ERROR - ❌ No camera found!
2025-11-25 09:45:14,964 - ERROR - ❌ No camera found!
2025-11-25 09:45:15,138 - INFO - Frame 206 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:15,142 - INFO - Video thread started with source: Camera
2025-11-25 09:45:15,147 - ERROR - ❌ No camera found!
2025-11-25 09:45:15,147 - INFO - Video thread started with source: Camera
2025-11-25 09:45:15,150 - ERROR - ❌ No camera found!
2025-11-25 09:45:15,339 - INFO - Video thread started with source: Camera
2025-11-25 09:45:15,341 - INFO - Video thread started with source: Camera
2025-11-25 09:45:15,341 - ERROR - ❌ No camera found!
2025-11-25 09:45:15,347 - ERROR - ❌ No camera found!
2025-11-25 09:45:15,540 - INFO - Video thread started with source: Camera
2025-11-25 09:45:15,542 - ERROR - ❌ No camera found!
2025-11-25 09:45:15,544 - INFO - Video thread started with source: Camera
2025-11-25 09:45:15,545 - INFO - Frame 208 | PERCLOS: 0.00 | Yaw: 10.0° | Alerts: 0
2025-11-25 09:45:15,549 - ERROR - ❌ No camera found!
2025-11-25 09:45:15,752 - INFO - Video thread started with source: Camera
2025-11-25 09:45:15,753 - INFO - Video thread started with source: Camera
2025-11-25 09:45:15,756 - ERROR - ❌ No camera found!
2025-11-25 09:45:15,756 - ERROR - ❌ No camera found!
2025-11-25 09:45:15,964 - INFO - Video thread started with source: Camera
2025-11-25 09:45:15,967 - INFO - Video thread started with source: Camera
2025-11-25 09:45:15,970 - ERROR - ❌ No camera found!
2025-11-25 09:45:15,973 - ERROR - ❌ No camera found!
2025-11-25 09:45:16,165 - INFO - Video thread started with source: Camera
2025-11-25 09:45:16,165 - INFO - Video thread started with source: Camera
2025-11-25 09:45:16,167 - ERROR - ❌ No camera found!
2025-11-25 09:45:16,168 - ERROR - ❌ No camera found!
2025-11-25 09:45:16,358 - INFO - Frame 210 | PERCLOS: 0.00 | Yaw: 9.6° | Alerts: 0
2025-11-25 09:45:16,361 - INFO - Video thread started with source: Camera
2025-11-25 09:45:16,367 - ERROR - ❌ No camera found!
2025-11-25 09:45:16,367 - ERROR - ❌ No camera found!
2025-11-25 09:45:16,367 - INFO - Video thread started with source: Camera
2025-11-25 09:45:16,566 - INFO - Video thread started with source: Camera
2025-11-25 09:45:16,567 - INFO - Video thread started with source: Camera
2025-11-25 09:45:16,570 - ERROR - ❌ No camera found!
2025-11-25 09:45:16,573 - ERROR - ❌ No camera found!
2025-11-25 09:45:16,782 - INFO - Video thread started with source: Camera
2025-11-25 09:45:16,782 - ERROR - ❌ No camera found!
2025-11-25 09:45:16,785 - INFO - Video thread started with source: Camera
2025-11-25 09:45:16,790 - ERROR - ❌ No camera found!
2025-11-25 09:45:16,808 - INFO - Frame 212 | PERCLOS: 0.00 | Yaw: 9.3° | Alerts: 0
2025-11-25 09:45:17,000 - INFO - Video thread started with source: Camera
2025-11-25 09:45:17,000 - INFO - Video thread started with source: Camera
2025-11-25 09:45:17,003 - ERROR - ❌ No camera found!
2025-11-25 09:45:17,003 - ERROR - ❌ No camera found!
2025-11-25 09:45:17,216 - INFO - Video thread started with source: Camera
2025-11-25 09:45:17,216 - INFO - Frame 214 | PERCLOS: 0.00 | Yaw: 8.4° | Alerts: 0
2025-11-25 09:45:17,217 - INFO - Video thread started with source: Camera
2025-11-25 09:45:17,218 - ERROR - ❌ No camera found!
2025-11-25 09:45:17,220 - ERROR - ❌ No camera found!
2025-11-25 09:45:17,411 - INFO - Video thread started with source: Camera
2025-11-25 09:45:17,415 - INFO - Video thread started with source: Camera
2025-11-25 09:45:17,416 - ERROR - ❌ No camera found!
2025-11-25 09:45:17,417 - ERROR - ❌ No camera found!
2025-11-25 09:45:17,629 - INFO - Video thread started with source: Camera
2025-11-25 09:45:17,629 - INFO - Video thread started with source: Camera
2025-11-25 09:45:17,632 - ERROR - ❌ No camera found!
2025-11-25 09:45:17,634 - ERROR - ❌ No camera found!
2025-11-25 09:45:17,827 - INFO - Frame 216 | PERCLOS: 0.00 | Yaw: 9.1° | Alerts: 0
2025-11-25 09:45:17,830 - INFO - Video thread started with source: Camera
2025-11-25 09:45:17,836 - INFO - Video thread started with source: Camera
2025-11-25 09:45:17,837 - ERROR - ❌ No camera found!
2025-11-25 09:45:17,838 - ERROR - ❌ No camera found!
2025-11-25 09:45:18,024 - INFO - Video thread started with source: Camera
2025-11-25 09:45:18,025 - ERROR - ❌ No camera found!
2025-11-25 09:45:18,032 - INFO - Video thread started with source: Camera
2025-11-25 09:45:18,036 - ERROR - ❌ No camera found!
2025-11-25 09:45:18,228 - INFO - Video thread started with source: Camera
2025-11-25 09:45:18,229 - INFO - Frame 218 | PERCLOS: 0.00 | Yaw: 9.3° | Alerts: 0
2025-11-25 09:45:18,231 - ERROR - ❌ No camera found!
2025-11-25 09:45:18,233 - INFO - Video thread started with source: Camera
2025-11-25 09:45:18,239 - ERROR - ❌ No camera found!
2025-11-25 09:45:18,434 - INFO - Video thread started with source: Camera
2025-11-25 09:45:18,436 - INFO - Video thread started with source: Camera
2025-11-25 09:45:18,436 - ERROR - ❌ No camera found!
2025-11-25 09:45:18,437 - ERROR - ❌ No camera found!
2025-11-25 09:45:18,645 - INFO - Video thread started with source: Camera
2025-11-25 09:45:18,647 - INFO - Video thread started with source: Camera
2025-11-25 09:45:18,649 - INFO - Frame 220 | PERCLOS: 0.00 | Yaw: 9.5° | Alerts: 0
2025-11-25 09:45:18,649 - ERROR - ❌ No camera found!
2025-11-25 09:45:18,657 - ERROR - ❌ No camera found!
2025-11-25 09:45:18,861 - INFO - Video thread started with source: Camera
2025-11-25 09:45:18,863 - INFO - Video thread started with source: Camera
2025-11-25 09:45:18,864 - ERROR - ❌ No camera found!
2025-11-25 09:45:18,865 - ERROR - ❌ No camera found!
2025-11-25 09:45:19,078 - INFO - Video thread started with source: Camera
2025-11-25 09:45:19,078 - INFO - Video thread started with source: Camera
2025-11-25 09:45:19,078 - ERROR - ❌ No camera found!
2025-11-25 09:45:19,082 - ERROR - ❌ No camera found!
2025-11-25 09:45:19,097 - INFO - Frame 222 | PERCLOS: 0.00 | Yaw: 6.3° | Alerts: 1
2025-11-25 09:45:19,278 - INFO - Video thread started with source: Camera
2025-11-25 09:45:19,278 - INFO - Video thread started with source: Camera
2025-11-25 09:45:19,281 - ERROR - ❌ No camera found!
2025-11-25 09:45:19,284 - ERROR - ❌ No camera found!
2025-11-25 09:45:19,487 - INFO - Video thread started with source: Camera
2025-11-25 09:45:19,489 - INFO - Video thread started with source: Camera
2025-11-25 09:45:19,489 - INFO - Frame 224 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-25 09:45:19,489 - ERROR - ❌ No camera found!
2025-11-25 09:45:19,493 - ERROR - ❌ No camera found!
2025-11-25 09:45:19,710 - INFO - Video thread started with source: Camera
2025-11-25 09:45:19,710 - INFO - Video thread started with source: Camera
2025-11-25 09:45:19,712 - ERROR - ❌ No camera found!
2025-11-25 09:45:19,712 - ERROR - ❌ No camera found!
2025-11-25 09:45:19,912 - INFO - Video thread started with source: Camera
2025-11-25 09:45:19,914 - INFO - Video thread started with source: Camera
2025-11-25 09:45:19,915 - ERROR - ❌ No camera found!
2025-11-25 09:45:19,916 - ERROR - ❌ No camera found!
2025-11-25 09:45:19,918 - INFO - Frame 226 | PERCLOS: 0.00 | Yaw: 4.0° | Alerts: 1
2025-11-25 09:45:20,115 - INFO - Video thread started with source: Camera
2025-11-25 09:45:20,116 - INFO - Video thread started with source: Camera
2025-11-25 09:45:20,118 - ERROR - ❌ No camera found!
2025-11-25 09:45:20,118 - ERROR - ❌ No camera found!
2025-11-25 09:45:20,337 - INFO - Video thread started with source: Camera
2025-11-25 09:45:20,337 - INFO - Video thread started with source: Camera
2025-11-25 09:45:20,338 - ERROR - ❌ No camera found!
2025-11-25 09:45:20,339 - ERROR - ❌ No camera found!
2025-11-25 09:45:20,530 - INFO - Frame 228 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-25 09:45:20,535 - INFO - Video thread started with source: Camera
2025-11-25 09:45:20,536 - ERROR - ❌ No camera found!
2025-11-25 09:45:20,540 - INFO - Video thread started with source: Camera
2025-11-25 09:45:20,545 - ERROR - ❌ No camera found!
2025-11-25 09:45:20,736 - INFO - Video thread started with source: Camera
2025-11-25 09:45:20,736 - INFO - Video thread started with source: Camera
2025-11-25 09:45:20,739 - ERROR - ❌ No camera found!
2025-11-25 09:45:20,740 - ERROR - ❌ No camera found!
2025-11-25 09:45:20,779 - INFO - Frame 230 | PERCLOS: 0.00 | Yaw: 0.9° | Alerts: 1
2025-11-25 09:45:20,945 - INFO - Video thread started with source: Camera
2025-11-25 09:45:20,947 - INFO - Video thread started with source: Camera
2025-11-25 09:45:20,951 - ERROR - ❌ No camera found!
2025-11-25 09:45:20,952 - ERROR - ❌ No camera found!
2025-11-25 09:45:21,157 - INFO - Video thread started with source: Camera
2025-11-25 09:45:21,159 - ERROR - ❌ No camera found!
2025-11-25 09:45:21,165 - INFO - Video thread started with source: Camera
2025-11-25 09:45:21,167 - ERROR - ❌ No camera found!
2025-11-25 09:45:21,190 - INFO - Frame 232 | PERCLOS: 0.00 | Yaw: 0.3° | Alerts: 1
2025-11-25 09:45:21,369 - INFO - Video thread started with source: Camera
2025-11-25 09:45:21,369 - INFO - Video thread started with source: Camera
2025-11-25 09:45:21,372 - ERROR - ❌ No camera found!
2025-11-25 09:45:21,373 - ERROR - ❌ No camera found!
2025-11-25 09:45:21,584 - INFO - Video thread started with source: Camera
2025-11-25 09:45:21,584 - INFO - Video thread started with source: Camera
2025-11-25 09:45:21,590 - ERROR - ❌ No camera found!
2025-11-25 09:45:21,591 - ERROR - ❌ No camera found!
2025-11-25 09:45:21,800 - INFO - Video thread started with source: Camera
2025-11-25 09:45:21,803 - ERROR - ❌ No camera found!
2025-11-25 09:45:21,803 - INFO - Video thread started with source: Camera
2025-11-25 09:45:21,805 - ERROR - ❌ No camera found!
2025-11-25 09:45:21,822 - INFO - Frame 234 | PERCLOS: 0.00 | Yaw: -0.3° | Alerts: 1
2025-11-25 09:45:22,014 - INFO - Video thread started with source: Camera
2025-11-25 09:45:22,014 - INFO - Video thread started with source: Camera
2025-11-25 09:45:22,016 - ERROR - ❌ No camera found!
2025-11-25 09:45:22,020 - ERROR - ❌ No camera found!
2025-11-25 09:45:22,215 - INFO - Video thread started with source: Camera
2025-11-25 09:45:22,216 - INFO - Video thread started with source: Camera
2025-11-25 09:45:22,217 - INFO - Frame 236 | PERCLOS: 0.00 | Yaw: -0.2° | Alerts: 1
2025-11-25 09:45:22,217 - ERROR - ❌ No camera found!
2025-11-25 09:45:22,219 - ERROR - ❌ No camera found!
2025-11-25 09:45:22,414 - INFO - Video thread started with source: Camera
2025-11-25 09:45:22,417 - ERROR - ❌ No camera found!
2025-11-25 09:45:22,424 - INFO - Video thread started with source: Camera
2025-11-25 09:45:22,424 - ERROR - ❌ No camera found!
2025-11-25 09:45:22,625 - INFO - Video thread started with source: Camera
2025-11-25 09:45:22,628 - ERROR - ❌ No camera found!
2025-11-25 09:45:22,633 - INFO - Video thread started with source: Camera
2025-11-25 09:45:22,639 - ERROR - ❌ No camera found!
2025-11-25 09:45:22,657 - INFO - Frame 238 | PERCLOS: 0.00 | Yaw: -0.6° | Alerts: 1
2025-11-25 09:45:22,821 - INFO - Video thread started with source: Camera
2025-11-25 09:45:22,821 - INFO - Video thread started with source: Camera
2025-11-25 09:45:22,823 - ERROR - ❌ No camera found!
2025-11-25 09:45:22,825 - ERROR - ❌ No camera found!
2025-11-25 09:45:23,032 - INFO - Video thread started with source: Camera
2025-11-25 09:45:23,035 - ERROR - ❌ No camera found!
2025-11-25 09:45:23,037 - INFO - Video thread started with source: Camera
2025-11-25 09:45:23,040 - ERROR - ❌ No camera found!
2025-11-25 09:45:23,237 - INFO - Frame 240 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 1
2025-11-25 09:45:23,241 - INFO - Video thread started with source: Camera
2025-11-25 09:45:23,243 - INFO - Video thread started with source: Camera
2025-11-25 09:45:23,245 - ERROR - ❌ No camera found!
2025-11-25 09:45:23,246 - ERROR - ❌ No camera found!
2025-11-25 09:45:23,448 - INFO - Video thread started with source: Camera
2025-11-25 09:45:23,451 - INFO - Video thread started with source: Camera
2025-11-25 09:45:23,452 - ERROR - ❌ No camera found!
2025-11-25 09:45:23,453 - ERROR - ❌ No camera found!
2025-11-25 09:45:23,489 - INFO - Frame 242 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 1
2025-11-25 09:45:23,665 - INFO - Video thread started with source: Camera
2025-11-25 09:45:23,665 - INFO - Video thread started with source: Camera
2025-11-25 09:45:23,666 - ERROR - ❌ No camera found!
2025-11-25 09:45:23,667 - ERROR - ❌ No camera found!
2025-11-25 09:45:23,890 - INFO - Video thread started with source: Camera
2025-11-25 09:45:23,891 - INFO - Frame 244 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 1
2025-11-25 09:45:23,892 - ERROR - ❌ No camera found!
2025-11-25 09:45:23,895 - INFO - Video thread started with source: Camera
2025-11-25 09:45:23,897 - ERROR - ❌ No camera found!
2025-11-25 09:45:24,093 - INFO - Video thread started with source: Camera
2025-11-25 09:45:24,094 - ERROR - ❌ No camera found!
2025-11-25 09:45:24,095 - INFO - Video thread started with source: Camera
2025-11-25 09:45:24,100 - ERROR - ❌ No camera found!
2025-11-25 09:45:24,287 - INFO - Video thread started with source: Camera
2025-11-25 09:45:24,290 - ERROR - ❌ No camera found!
2025-11-25 09:45:24,296 - INFO - Video thread started with source: Camera
2025-11-25 09:45:24,304 - ERROR - ❌ No camera found!
2025-11-25 09:45:24,508 - INFO - Video thread started with source: Camera
2025-11-25 09:45:24,508 - INFO - Video thread started with source: Camera
2025-11-25 09:45:24,509 - ERROR - ❌ No camera found!
2025-11-25 09:45:24,509 - ERROR - ❌ No camera found!
2025-11-25 09:45:24,523 - INFO - Frame 246 | PERCLOS: 0.00 | Yaw: 3.0° | Alerts: 1
2025-11-25 09:45:24,723 - INFO - Video thread started with source: Camera
2025-11-25 09:45:24,729 - ERROR - ❌ No camera found!
2025-11-25 09:45:24,730 - INFO - Video thread started with source: Camera
2025-11-25 09:45:24,733 - ERROR - ❌ No camera found!
2025-11-25 09:45:24,933 - INFO - Video thread started with source: Camera
2025-11-25 09:45:24,933 - INFO - Video thread started with source: Camera
2025-11-25 09:45:24,934 - ERROR - ❌ No camera found!
2025-11-25 09:45:24,937 - ERROR - ❌ No camera found!
2025-11-25 09:45:24,937 - INFO - Frame 248 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-25 09:45:25,131 - INFO - Video thread started with source: Camera
2025-11-25 09:45:25,133 - INFO - Video thread started with source: Camera
2025-11-25 09:45:25,133 - ERROR - ❌ No camera found!
2025-11-25 09:45:25,134 - ERROR - ❌ No camera found!
2025-11-25 09:45:25,361 - INFO - Video thread started with source: Camera
2025-11-25 09:45:25,365 - INFO - Frame 250 | PERCLOS: 0.00 | Yaw: 8.2° | Alerts: 1
2025-11-25 09:45:25,366 - ERROR - ❌ No camera found!
2025-11-25 09:45:25,456 - INFO - Video thread started with source: Camera
2025-11-25 09:45:25,456 - ERROR - ❌ No camera found!
2025-11-25 09:45:25,667 - INFO - Video thread started with source: Camera
2025-11-25 09:45:25,670 - INFO - Video thread started with source: Camera
2025-11-25 09:45:25,670 - INFO - Frame 252 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:25,671 - ERROR - ❌ No camera found!
2025-11-25 09:45:25,671 - ERROR - ❌ No camera found!
2025-11-25 09:45:25,869 - INFO - Video thread started with source: Camera
2025-11-25 09:45:25,871 - INFO - Video thread started with source: Camera
2025-11-25 09:45:25,871 - ERROR - ❌ No camera found!
2025-11-25 09:45:25,871 - ERROR - ❌ No camera found!
2025-11-25 09:45:26,069 - INFO - Video thread started with source: Camera
2025-11-25 09:45:26,071 - ERROR - ❌ No camera found!
2025-11-25 09:45:26,073 - INFO - Video thread started with source: Camera
2025-11-25 09:45:26,076 - INFO - Frame 254 | PERCLOS: 0.00 | Yaw: 2.1° | Alerts: 0
2025-11-25 09:45:26,077 - ERROR - ❌ No camera found!
2025-11-25 09:45:26,270 - INFO - Video thread started with source: Camera
2025-11-25 09:45:26,271 - INFO - Video thread started with source: Camera
2025-11-25 09:45:26,271 - ERROR - ❌ No camera found!
2025-11-25 09:45:26,272 - ERROR - ❌ No camera found!
2025-11-25 09:45:26,473 - INFO - Video thread started with source: Camera
2025-11-25 09:45:26,474 - INFO - Frame 256 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 0
2025-11-25 09:45:26,475 - ERROR - ❌ No camera found!
2025-11-25 09:45:26,475 - INFO - Video thread started with source: Camera
2025-11-25 09:45:26,480 - ERROR - ❌ No camera found!
2025-11-25 09:45:26,693 - INFO - Video thread started with source: Camera
2025-11-25 09:45:26,693 - INFO - Video thread started with source: Camera
2025-11-25 09:45:26,696 - ERROR - ❌ No camera found!
2025-11-25 09:45:26,700 - ERROR - ❌ No camera found!
2025-11-25 09:45:26,904 - INFO - Video thread started with source: Camera
2025-11-25 09:45:26,907 - ERROR - ❌ No camera found!
2025-11-25 09:45:26,907 - INFO - Video thread started with source: Camera
2025-11-25 09:45:26,911 - ERROR - ❌ No camera found!
2025-11-25 09:45:27,115 - INFO - Frame 258 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 1
2025-11-25 09:45:27,120 - INFO - Video thread started with source: Camera
2025-11-25 09:45:27,121 - INFO - Video thread started with source: Camera
2025-11-25 09:45:27,122 - ERROR - ❌ No camera found!
2025-11-25 09:45:27,128 - ERROR - ❌ No camera found!
2025-11-25 09:45:27,318 - INFO - Video thread started with source: Camera
2025-11-25 09:45:27,325 - ERROR - ❌ No camera found!
2025-11-25 09:45:27,330 - INFO - Video thread started with source: Camera
2025-11-25 09:45:27,331 - ERROR - ❌ No camera found!
2025-11-25 09:45:27,517 - INFO - Video thread started with source: Camera
2025-11-25 09:45:27,518 - INFO - Frame 260 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 1
2025-11-25 09:45:27,520 - ERROR - ❌ No camera found!
2025-11-25 09:45:27,520 - INFO - Video thread started with source: Camera
2025-11-25 09:45:27,522 - ERROR - ❌ No camera found!
2025-11-25 09:45:27,729 - INFO - Video thread started with source: Camera
2025-11-25 09:45:27,732 - INFO - Video thread started with source: Camera
2025-11-25 09:45:27,733 - ERROR - ❌ No camera found!
2025-11-25 09:45:27,735 - ERROR - ❌ No camera found!
2025-11-25 09:45:27,939 - INFO - Video thread started with source: Camera
2025-11-25 09:45:27,940 - INFO - Frame 262 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 1
2025-11-25 09:45:27,941 - ERROR - ❌ No camera found!
2025-11-25 09:45:27,942 - INFO - Video thread started with source: Camera
2025-11-25 09:45:27,945 - ERROR - ❌ No camera found!
2025-11-25 09:45:28,148 - INFO - Video thread started with source: Camera
2025-11-25 09:45:28,152 - ERROR - ❌ No camera found!
2025-11-25 09:45:28,157 - INFO - Video thread started with source: Camera
2025-11-25 09:45:28,160 - ERROR - ❌ No camera found!
2025-11-25 09:45:28,186 - INFO - Frame 264 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:28,351 - INFO - Video thread started with source: Camera
2025-11-25 09:45:28,355 - ERROR - ❌ No camera found!
2025-11-25 09:45:28,355 - INFO - Video thread started with source: Camera
2025-11-25 09:45:28,361 - ERROR - ❌ No camera found!
2025-11-25 09:45:28,547 - INFO - Video thread started with source: Camera
2025-11-25 09:45:28,550 - ERROR - ❌ No camera found!
2025-11-25 09:45:28,553 - INFO - Video thread started with source: Camera
2025-11-25 09:45:28,563 - ERROR - ❌ No camera found!
2025-11-25 09:45:28,574 - INFO - Frame 266 | PERCLOS: 0.00 | Yaw: 10.9° | Alerts: 0
2025-11-25 09:45:28,759 - INFO - Video thread started with source: Camera
2025-11-25 09:45:28,761 - INFO - Video thread started with source: Camera
2025-11-25 09:45:28,761 - ERROR - ❌ No camera found!
2025-11-25 09:45:28,765 - ERROR - ❌ No camera found!
2025-11-25 09:45:28,975 - INFO - Video thread started with source: Camera
2025-11-25 09:45:28,975 - INFO - Video thread started with source: Camera
2025-11-25 09:45:28,975 - INFO - Frame 268 | PERCLOS: 0.00 | Yaw: 10.8° | Alerts: 0
2025-11-25 09:45:28,980 - ERROR - ❌ No camera found!
2025-11-25 09:45:28,981 - ERROR - ❌ No camera found!
2025-11-25 09:45:29,187 - INFO - Video thread started with source: Camera
2025-11-25 09:45:29,190 - ERROR - ❌ No camera found!
2025-11-25 09:45:29,190 - INFO - Video thread started with source: Camera
2025-11-25 09:45:29,194 - ERROR - ❌ No camera found!
2025-11-25 09:45:29,407 - INFO - Video thread started with source: Camera
2025-11-25 09:45:29,410 - ERROR - ❌ No camera found!
2025-11-25 09:45:29,413 - INFO - Video thread started with source: Camera
2025-11-25 09:45:29,414 - ERROR - ❌ No camera found!
2025-11-25 09:45:29,606 - INFO - Frame 270 | PERCLOS: 0.00 | Yaw: 10.8° | Alerts: 1
2025-11-25 09:45:29,610 - INFO - Video thread started with source: Camera
2025-11-25 09:45:29,611 - INFO - Video thread started with source: Camera
2025-11-25 09:45:29,612 - ERROR - ❌ No camera found!
2025-11-25 09:45:29,613 - ERROR - ❌ No camera found!
2025-11-25 09:45:29,817 - INFO - Video thread started with source: Camera
2025-11-25 09:45:29,817 - INFO - Video thread started with source: Camera
2025-11-25 09:45:29,822 - ERROR - ❌ No camera found!
2025-11-25 09:45:29,822 - ERROR - ❌ No camera found!
2025-11-25 09:45:29,822 - INFO - Frame 272 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:30,013 - INFO - Video thread started with source: Camera
2025-11-25 09:45:30,013 - INFO - Video thread started with source: Camera
2025-11-25 09:45:30,016 - ERROR - ❌ No camera found!
2025-11-25 09:45:30,018 - ERROR - ❌ No camera found!
2025-11-25 09:45:30,210 - INFO - Video thread started with source: Camera
2025-11-25 09:45:30,211 - INFO - Video thread started with source: Camera
2025-11-25 09:45:30,212 - ERROR - ❌ No camera found!
2025-11-25 09:45:30,217 - ERROR - ❌ No camera found!
2025-11-25 09:45:30,234 - INFO - Frame 274 | PERCLOS: 0.00 | Yaw: 8.1° | Alerts: 0
2025-11-25 09:45:30,437 - INFO - Video thread started with source: Camera
2025-11-25 09:45:30,438 - INFO - Video thread started with source: Camera
2025-11-25 09:45:30,443 - ERROR - ❌ No camera found!
2025-11-25 09:45:30,444 - ERROR - ❌ No camera found!
2025-11-25 09:45:30,646 - INFO - Frame 276 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:30,654 - INFO - Video thread started with source: Camera
2025-11-25 09:45:30,654 - INFO - Video thread started with source: Camera
2025-11-25 09:45:30,655 - ERROR - ❌ No camera found!
2025-11-25 09:45:30,655 - ERROR - ❌ No camera found!
2025-11-25 09:45:30,848 - INFO - Video thread started with source: Camera
2025-11-25 09:45:30,849 - ERROR - ❌ No camera found!
2025-11-25 09:45:30,851 - INFO - Video thread started with source: Camera
2025-11-25 09:45:30,854 - ERROR - ❌ No camera found!
2025-11-25 09:45:31,071 - INFO - Frame 278 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 0
2025-11-25 09:45:31,071 - INFO - Video thread started with source: Camera
2025-11-25 09:45:31,073 - ERROR - ❌ No camera found!
2025-11-25 09:45:31,077 - INFO - Video thread started with source: Camera
2025-11-25 09:45:31,083 - ERROR - ❌ No camera found!
2025-11-25 09:45:31,276 - INFO - Video thread started with source: Camera
2025-11-25 09:45:31,278 - INFO - Frame 280 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:31,279 - ERROR - ❌ No camera found!
2025-11-25 09:45:31,280 - INFO - Video thread started with source: Camera
2025-11-25 09:45:31,283 - ERROR - ❌ No camera found!
2025-11-25 09:45:31,479 - INFO - Video thread started with source: Camera
2025-11-25 09:45:31,480 - ERROR - ❌ No camera found!
2025-11-25 09:45:31,480 - INFO - Video thread started with source: Camera
2025-11-25 09:45:31,485 - ERROR - ❌ No camera found!
2025-11-25 09:45:31,681 - INFO - Video thread started with source: Camera
2025-11-25 09:45:31,681 - INFO - Video thread started with source: Camera
2025-11-25 09:45:31,684 - ERROR - ❌ No camera found!
2025-11-25 09:45:31,685 - ERROR - ❌ No camera found!
2025-11-25 09:45:31,896 - INFO - Video thread started with source: Camera
2025-11-25 09:45:31,896 - INFO - Video thread started with source: Camera
2025-11-25 09:45:31,897 - ERROR - ❌ No camera found!
2025-11-25 09:45:31,900 - ERROR - ❌ No camera found!
2025-11-25 09:45:31,909 - INFO - Frame 282 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 1
2025-11-25 09:45:32,099 - INFO - Video thread started with source: Camera
2025-11-25 09:45:32,101 - INFO - Video thread started with source: Camera
2025-11-25 09:45:32,102 - ERROR - ❌ No camera found!
2025-11-25 09:45:32,103 - ERROR - ❌ No camera found!
2025-11-25 09:45:32,326 - INFO - Video thread started with source: Camera
2025-11-25 09:45:32,326 - INFO - Video thread started with source: Camera
2025-11-25 09:45:32,328 - ERROR - ❌ No camera found!
2025-11-25 09:45:32,328 - ERROR - ❌ No camera found!
2025-11-25 09:45:32,330 - INFO - Frame 284 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 1
2025-11-25 09:45:32,534 - INFO - Video thread started with source: Camera
2025-11-25 09:45:32,536 - INFO - Video thread started with source: Camera
2025-11-25 09:45:32,537 - ERROR - ❌ No camera found!
2025-11-25 09:45:32,538 - ERROR - ❌ No camera found!
2025-11-25 09:45:32,732 - INFO - Video thread started with source: Camera
2025-11-25 09:45:32,735 - ERROR - ❌ No camera found!
2025-11-25 09:45:32,744 - INFO - Video thread started with source: Camera
2025-11-25 09:45:32,746 - ERROR - ❌ No camera found!
2025-11-25 09:45:32,760 - INFO - Frame 286 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-25 09:45:32,941 - INFO - Video thread started with source: Camera
2025-11-25 09:45:32,947 - ERROR - ❌ No camera found!
2025-11-25 09:45:32,948 - INFO - Video thread started with source: Camera
2025-11-25 09:45:32,949 - ERROR - ❌ No camera found!
2025-11-25 09:45:33,159 - INFO - Video thread started with source: Camera
2025-11-25 09:45:33,159 - INFO - Video thread started with source: Camera
2025-11-25 09:45:33,161 - ERROR - ❌ No camera found!
2025-11-25 09:45:33,163 - ERROR - ❌ No camera found!
2025-11-25 09:45:33,374 - INFO - Video thread started with source: Camera
2025-11-25 09:45:33,375 - INFO - Video thread started with source: Camera
2025-11-25 09:45:33,375 - ERROR - ❌ No camera found!
2025-11-25 09:45:33,375 - ERROR - ❌ No camera found!
2025-11-25 09:45:33,392 - INFO - Frame 288 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 1
2025-11-25 09:45:33,593 - INFO - Video thread started with source: Camera
2025-11-25 09:45:33,593 - INFO - Video thread started with source: Camera
2025-11-25 09:45:33,595 - ERROR - ❌ No camera found!
2025-11-25 09:45:33,595 - ERROR - ❌ No camera found!
2025-11-25 09:45:33,800 - INFO - Video thread started with source: Camera
2025-11-25 09:45:33,804 - ERROR - ❌ No camera found!
2025-11-25 09:45:33,808 - INFO - Video thread started with source: Camera
2025-11-25 09:45:33,813 - ERROR - ❌ No camera found!
2025-11-25 09:45:33,830 - INFO - Frame 290 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 1
2025-11-25 09:45:34,013 - INFO - Video thread started with source: Camera
2025-11-25 09:45:34,014 - INFO - Video thread started with source: Camera
2025-11-25 09:45:34,018 - ERROR - ❌ No camera found!
2025-11-25 09:45:34,018 - ERROR - ❌ No camera found!
2025-11-25 09:45:34,247 - INFO - Video thread started with source: Camera
2025-11-25 09:45:34,247 - INFO - Video thread started with source: Camera
2025-11-25 09:45:34,247 - INFO - Frame 292 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 1
2025-11-25 09:45:34,247 - ERROR - ❌ No camera found!
2025-11-25 09:45:34,248 - ERROR - ❌ No camera found!
2025-11-25 09:45:34,441 - INFO - Video thread started with source: Camera
2025-11-25 09:45:34,441 - INFO - Video thread started with source: Camera
2025-11-25 09:45:34,442 - ERROR - ❌ No camera found!
2025-11-25 09:45:34,442 - ERROR - ❌ No camera found!
2025-11-25 09:45:34,652 - INFO - Video thread started with source: Camera
2025-11-25 09:45:34,656 - INFO - Video thread started with source: Camera
2025-11-25 09:45:34,658 - ERROR - ❌ No camera found!
2025-11-25 09:45:34,658 - ERROR - ❌ No camera found!
2025-11-25 09:45:34,851 - INFO - Frame 294 | PERCLOS: 0.00 | Yaw: 0.6° | Alerts: 1
2025-11-25 09:45:34,859 - INFO - Video thread started with source: Camera
2025-11-25 09:45:34,859 - INFO - Video thread started with source: Camera
2025-11-25 09:45:34,862 - ERROR - ❌ No camera found!
2025-11-25 09:45:34,862 - ERROR - ❌ No camera found!
2025-11-25 09:45:35,068 - INFO - Video thread started with source: Camera
2025-11-25 09:45:35,069 - ERROR - ❌ No camera found!
2025-11-25 09:45:35,070 - INFO - Video thread started with source: Camera
2025-11-25 09:45:35,074 - ERROR - ❌ No camera found!
2025-11-25 09:45:35,277 - INFO - Video thread started with source: Camera
2025-11-25 09:45:35,277 - INFO - Video thread started with source: Camera
2025-11-25 09:45:35,282 - ERROR - ❌ No camera found!
2025-11-25 09:45:35,284 - ERROR - ❌ No camera found!
2025-11-25 09:45:35,310 - INFO - Frame 296 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 1
2025-11-25 09:45:35,474 - INFO - Video thread started with source: Camera
2025-11-25 09:45:35,474 - INFO - Video thread started with source: Camera
2025-11-25 09:45:35,475 - ERROR - ❌ No camera found!
2025-11-25 09:45:35,475 - ERROR - ❌ No camera found!
2025-11-25 09:45:35,692 - INFO - Video thread started with source: Camera
2025-11-25 09:45:35,694 - INFO - Video thread started with source: Camera
2025-11-25 09:45:35,694 - ERROR - ❌ No camera found!
2025-11-25 09:45:35,696 - ERROR - ❌ No camera found!
2025-11-25 09:45:35,696 - INFO - Frame 298 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 1
2025-11-25 09:45:35,892 - INFO - Video thread started with source: Camera
2025-11-25 09:45:35,895 - ERROR - ❌ No camera found!
2025-11-25 09:45:35,896 - INFO - Video thread started with source: Camera
2025-11-25 09:45:35,897 - ERROR - ❌ No camera found!
2025-11-25 09:45:35,934 - INFO - Frame 300 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:36,101 - INFO - Video thread started with source: Camera
2025-11-25 09:45:36,106 - INFO - Video thread started with source: Camera
2025-11-25 09:45:36,109 - ERROR - ❌ No camera found!
2025-11-25 09:45:36,114 - ERROR - ❌ No camera found!
2025-11-25 09:45:36,141 - INFO - Frame 302 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:36,300 - INFO - Video thread started with source: Camera
2025-11-25 09:45:36,302 - INFO - Video thread started with source: Camera
2025-11-25 09:45:36,304 - ERROR - ❌ No camera found!
2025-11-25 09:45:36,304 - ERROR - ❌ No camera found!
2025-11-25 09:45:36,504 - INFO - Video thread started with source: Camera
2025-11-25 09:45:36,508 - INFO - Video thread started with source: Camera
2025-11-25 09:45:36,512 - ERROR - ❌ No camera found!
2025-11-25 09:45:36,513 - ERROR - ❌ No camera found!
2025-11-25 09:45:36,529 - INFO - Frame 304 | PERCLOS: 0.00 | Yaw: 9.0° | Alerts: 0
2025-11-25 09:45:36,724 - INFO - Video thread started with source: Camera
2025-11-25 09:45:36,725 - INFO - Video thread started with source: Camera
2025-11-25 09:45:36,726 - ERROR - ❌ No camera found!
2025-11-25 09:45:36,726 - ERROR - ❌ No camera found!
2025-11-25 09:45:36,937 - INFO - Video thread started with source: Camera
2025-11-25 09:45:36,944 - ERROR - ❌ No camera found!
2025-11-25 09:45:36,944 - INFO - Video thread started with source: Camera
2025-11-25 09:45:36,947 - ERROR - ❌ No camera found!
2025-11-25 09:45:37,144 - INFO - Video thread started with source: Camera
2025-11-25 09:45:37,145 - INFO - Frame 306 | PERCLOS: 0.00 | Yaw: -4.9° | Alerts: 1
2025-11-25 09:45:37,146 - ERROR - ❌ No camera found!
2025-11-25 09:45:37,147 - INFO - Video thread started with source: Camera
2025-11-25 09:45:37,148 - ERROR - ❌ No camera found!
2025-11-25 09:45:37,358 - INFO - Video thread started with source: Camera
2025-11-25 09:45:37,359 - INFO - Video thread started with source: Camera
2025-11-25 09:45:37,360 - ERROR - ❌ No camera found!
2025-11-25 09:45:37,361 - ERROR - ❌ No camera found!
2025-11-25 09:45:37,550 - INFO - Video thread started with source: Camera
2025-11-25 09:45:37,552 - ERROR - ❌ No camera found!
2025-11-25 09:45:37,552 - INFO - Video thread started with source: Camera
2025-11-25 09:45:37,562 - ERROR - ❌ No camera found!
2025-11-25 09:45:37,591 - INFO - Frame 308 | PERCLOS: 0.00 | Yaw: -1.8° | Alerts: 1
2025-11-25 09:45:37,778 - INFO - Video thread started with source: Camera
2025-11-25 09:45:37,779 - INFO - Video thread started with source: Camera
2025-11-25 09:45:37,785 - ERROR - ❌ No camera found!
2025-11-25 09:45:37,787 - ERROR - ❌ No camera found!
2025-11-25 09:45:37,977 - INFO - Video thread started with source: Camera
2025-11-25 09:45:37,981 - ERROR - ❌ No camera found!
2025-11-25 09:45:37,982 - INFO - Video thread started with source: Camera
2025-11-25 09:45:37,982 - ERROR - ❌ No camera found!
2025-11-25 09:45:38,009 - INFO - Frame 310 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 1
2025-11-25 09:45:38,185 - INFO - Video thread started with source: Camera
2025-11-25 09:45:38,186 - INFO - Video thread started with source: Camera
2025-11-25 09:45:38,188 - ERROR - ❌ No camera found!
2025-11-25 09:45:38,188 - ERROR - ❌ No camera found!
2025-11-25 09:45:38,391 - INFO - Video thread started with source: Camera
2025-11-25 09:45:38,395 - ERROR - ❌ No camera found!
2025-11-25 09:45:38,395 - INFO - Video thread started with source: Camera
2025-11-25 09:45:38,405 - ERROR - ❌ No camera found!
2025-11-25 09:45:38,585 - INFO - Video thread started with source: Camera
2025-11-25 09:45:38,586 - INFO - Video thread started with source: Camera
2025-11-25 09:45:38,591 - ERROR - ❌ No camera found!
2025-11-25 09:45:38,591 - ERROR - ❌ No camera found!
2025-11-25 09:45:38,605 - INFO - Frame 312 | PERCLOS: 0.00 | Yaw: 0.8° | Alerts: 1
2025-11-25 09:45:38,808 - INFO - Video thread started with source: Camera
2025-11-25 09:45:38,810 - ERROR - ❌ No camera found!
2025-11-25 09:45:38,811 - INFO - Video thread started with source: Camera
2025-11-25 09:45:38,816 - ERROR - ❌ No camera found!
2025-11-25 09:45:39,041 - INFO - Video thread started with source: Camera
2025-11-25 09:45:39,041 - INFO - Video thread started with source: Camera
2025-11-25 09:45:39,043 - ERROR - ❌ No camera found!
2025-11-25 09:45:39,043 - INFO - Frame 314 | PERCLOS: 0.00 | Yaw: -0.5° | Alerts: 1
2025-11-25 09:45:39,043 - ERROR - ❌ No camera found!
2025-11-25 09:45:39,244 - INFO - Video thread started with source: Camera
2025-11-25 09:45:39,247 - ERROR - ❌ No camera found!
2025-11-25 09:45:39,251 - INFO - Video thread started with source: Camera
2025-11-25 09:45:39,257 - ERROR - ❌ No camera found!
2025-11-25 09:45:39,464 - INFO - Video thread started with source: Camera
2025-11-25 09:45:39,464 - INFO - Frame 316 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 1
2025-11-25 09:45:39,465 - INFO - Video thread started with source: Camera
2025-11-25 09:45:39,466 - ERROR - ❌ No camera found!
2025-11-25 09:45:39,469 - ERROR - ❌ No camera found!
2025-11-25 09:45:39,664 - INFO - Video thread started with source: Camera
2025-11-25 09:45:39,664 - INFO - Video thread started with source: Camera
2025-11-25 09:45:39,666 - ERROR - ❌ No camera found!
2025-11-25 09:45:39,667 - ERROR - ❌ No camera found!
2025-11-25 09:45:39,702 - INFO - Frame 318 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:39,867 - INFO - Video thread started with source: Camera
2025-11-25 09:45:39,867 - INFO - Video thread started with source: Camera
2025-11-25 09:45:39,868 - ERROR - ❌ No camera found!
2025-11-25 09:45:39,872 - ERROR - ❌ No camera found!
2025-11-25 09:45:40,057 - INFO - Video thread started with source: Camera
2025-11-25 09:45:40,060 - INFO - Video thread started with source: Camera
2025-11-25 09:45:40,061 - ERROR - ❌ No camera found!
2025-11-25 09:45:40,061 - INFO - Frame 320 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:40,063 - ERROR - ❌ No camera found!
2025-11-25 09:45:40,245 - INFO - Video thread started with source: Camera
2025-11-25 09:45:40,248 - ERROR - ❌ No camera found!
2025-11-25 09:45:40,249 - INFO - Video thread started with source: Camera
2025-11-25 09:45:40,251 - ERROR - ❌ No camera found!
2025-11-25 09:45:40,283 - INFO - Frame 322 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:40,449 - INFO - Video thread started with source: Camera
2025-11-25 09:45:40,449 - INFO - Video thread started with source: Camera
2025-11-25 09:45:40,451 - ERROR - ❌ No camera found!
2025-11-25 09:45:40,452 - ERROR - ❌ No camera found!
2025-11-25 09:45:40,491 - INFO - Frame 324 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:40,652 - INFO - Video thread started with source: Camera
2025-11-25 09:45:40,652 - INFO - Video thread started with source: Camera
2025-11-25 09:45:40,656 - ERROR - ❌ No camera found!
2025-11-25 09:45:40,656 - ERROR - ❌ No camera found!
2025-11-25 09:45:40,835 - INFO - Video thread started with source: Camera
2025-11-25 09:45:40,835 - INFO - Frame 326 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:40,840 - INFO - Video thread started with source: Camera
2025-11-25 09:45:40,840 - ERROR - ❌ No camera found!
2025-11-25 09:45:40,850 - ERROR - ❌ No camera found!
2025-11-25 09:45:41,030 - INFO - Video thread started with source: Camera
2025-11-25 09:45:41,032 - INFO - Video thread started with source: Camera
2025-11-25 09:45:41,033 - ERROR - ❌ No camera found!
2025-11-25 09:45:41,038 - ERROR - ❌ No camera found!
2025-11-25 09:45:41,041 - INFO - Frame 328 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:41,237 - INFO - Video thread started with source: Camera
2025-11-25 09:45:41,237 - INFO - Video thread started with source: Camera
2025-11-25 09:45:41,239 - ERROR - ❌ No camera found!
2025-11-25 09:45:41,241 - ERROR - ❌ No camera found!
2025-11-25 09:45:41,432 - INFO - Frame 330 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:41,438 - INFO - Video thread started with source: Camera
2025-11-25 09:45:41,438 - INFO - Video thread started with source: Camera
2025-11-25 09:45:41,439 - ERROR - ❌ No camera found!
2025-11-25 09:45:41,441 - ERROR - ❌ No camera found!
2025-11-25 09:45:41,634 - INFO - Video thread started with source: Camera
2025-11-25 09:45:41,639 - ERROR - ❌ No camera found!
2025-11-25 09:45:41,640 - INFO - Frame 332 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:41,641 - INFO - Video thread started with source: Camera
2025-11-25 09:45:41,644 - ERROR - ❌ No camera found!
2025-11-25 09:45:41,839 - INFO - Video thread started with source: Camera
2025-11-25 09:45:41,839 - INFO - Video thread started with source: Camera
2025-11-25 09:45:41,841 - INFO - Frame 334 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:41,841 - ERROR - ❌ No camera found!
2025-11-25 09:45:41,842 - ERROR - ❌ No camera found!
2025-11-25 09:45:42,020 - INFO - Video thread started with source: Camera
2025-11-25 09:45:42,020 - INFO - Video thread started with source: Camera
2025-11-25 09:45:42,022 - ERROR - ❌ No camera found!
2025-11-25 09:45:42,023 - ERROR - ❌ No camera found!
2025-11-25 09:45:42,060 - INFO - Frame 336 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:42,217 - INFO - Video thread started with source: Camera
2025-11-25 09:45:42,219 - INFO - Video thread started with source: Camera
2025-11-25 09:45:42,219 - ERROR - ❌ No camera found!
2025-11-25 09:45:42,222 - ERROR - ❌ No camera found!
2025-11-25 09:45:42,409 - INFO - Video thread started with source: Camera
2025-11-25 09:45:42,409 - INFO - Frame 338 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:42,409 - INFO - Video thread started with source: Camera
2025-11-25 09:45:42,412 - ERROR - ❌ No camera found!
2025-11-25 09:45:42,412 - ERROR - ❌ No camera found!
2025-11-25 09:45:42,604 - INFO - Video thread started with source: Camera
2025-11-25 09:45:42,607 - INFO - Video thread started with source: Camera
2025-11-25 09:45:42,608 - ERROR - ❌ No camera found!
2025-11-25 09:45:42,610 - ERROR - ❌ No camera found!
2025-11-25 09:45:42,812 - INFO - Video thread started with source: Camera
2025-11-25 09:45:42,812 - INFO - Video thread started with source: Camera
2025-11-25 09:45:42,813 - ERROR - ❌ No camera found!
2025-11-25 09:45:42,814 - INFO - Frame 340 | PERCLOS: 0.10 | Yaw: -7.7° | Alerts: 0
2025-11-25 09:45:42,814 - ERROR - ❌ No camera found!
2025-11-25 09:45:43,006 - INFO - Video thread started with source: Camera
2025-11-25 09:45:43,008 - ERROR - ❌ No camera found!
2025-11-25 09:45:43,011 - INFO - Video thread started with source: Camera
2025-11-25 09:45:43,016 - ERROR - ❌ No camera found!
2025-11-25 09:45:43,227 - INFO - Video thread started with source: Camera
2025-11-25 09:45:43,227 - INFO - Video thread started with source: Camera
2025-11-25 09:45:43,230 - ERROR - ❌ No camera found!
2025-11-25 09:45:43,231 - ERROR - ❌ No camera found!
2025-11-25 09:45:43,418 - INFO - Frame 342 | PERCLOS: 0.45 | Yaw: 2.5° | Alerts: 2
2025-11-25 09:45:43,421 - INFO - Video thread started with source: Camera
2025-11-25 09:45:43,421 - INFO - Video thread started with source: Camera
2025-11-25 09:45:43,422 - ERROR - ❌ No camera found!
2025-11-25 09:45:43,422 - ERROR - ❌ No camera found!
2025-11-25 09:45:43,633 - INFO - Video thread started with source: Camera
2025-11-25 09:45:43,638 - INFO - Video thread started with source: Camera
2025-11-25 09:45:43,638 - ERROR - ❌ No camera found!
2025-11-25 09:45:43,642 - ERROR - ❌ No camera found!
2025-11-25 09:45:43,835 - INFO - Frame 344 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:43,838 - INFO - Video thread started with source: Camera
2025-11-25 09:45:43,840 - ERROR - ❌ No camera found!
2025-11-25 09:45:43,843 - INFO - Video thread started with source: Camera
2025-11-25 09:45:43,849 - ERROR - ❌ No camera found!
2025-11-25 09:45:44,031 - INFO - Video thread started with source: Camera
2025-11-25 09:45:44,031 - INFO - Video thread started with source: Camera
2025-11-25 09:45:44,032 - INFO - Frame 346 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:44,032 - ERROR - ❌ No camera found!
2025-11-25 09:45:44,037 - ERROR - ❌ No camera found!
2025-11-25 09:45:44,224 - INFO - Video thread started with source: Camera
2025-11-25 09:45:44,227 - INFO - Video thread started with source: Camera
2025-11-25 09:45:44,227 - ERROR - ❌ No camera found!
2025-11-25 09:45:44,229 - ERROR - ❌ No camera found!
2025-11-25 09:45:44,412 - INFO - Frame 348 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:44,418 - INFO - Video thread started with source: Camera
2025-11-25 09:45:44,418 - INFO - Video thread started with source: Camera
2025-11-25 09:45:44,420 - ERROR - ❌ No camera found!
2025-11-25 09:45:44,422 - ERROR - ❌ No camera found!
2025-11-25 09:45:44,602 - INFO - Video thread started with source: Camera
2025-11-25 09:45:44,605 - ERROR - ❌ No camera found!
2025-11-25 09:45:44,611 - INFO - Video thread started with source: Camera
2025-11-25 09:45:44,615 - ERROR - ❌ No camera found!
2025-11-25 09:45:44,806 - INFO - Frame 350 | PERCLOS: 0.05 | Yaw: -0.8° | Alerts: 0
2025-11-25 09:45:44,807 - INFO - Video thread started with source: Camera
2025-11-25 09:45:44,807 - INFO - Video thread started with source: Camera
2025-11-25 09:45:44,810 - ERROR - ❌ No camera found!
2025-11-25 09:45:44,810 - ERROR - ❌ No camera found!
2025-11-25 09:45:45,006 - INFO - Video thread started with source: Camera
2025-11-25 09:45:45,006 - INFO - Video thread started with source: Camera
2025-11-25 09:45:45,010 - ERROR - ❌ No camera found!
2025-11-25 09:45:45,012 - ERROR - ❌ No camera found!
2025-11-25 09:45:45,216 - INFO - Frame 352 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 0
2025-11-25 09:45:45,221 - INFO - Video thread started with source: Camera
2025-11-25 09:45:45,221 - INFO - Video thread started with source: Camera
2025-11-25 09:45:45,222 - ERROR - ❌ No camera found!
2025-11-25 09:45:45,222 - ERROR - ❌ No camera found!
2025-11-25 09:45:45,437 - INFO - Video thread started with source: Camera
2025-11-25 09:45:45,438 - ERROR - ❌ No camera found!
2025-11-25 09:45:45,438 - INFO - Video thread started with source: Camera
2025-11-25 09:45:45,441 - ERROR - ❌ No camera found!
2025-11-25 09:45:45,656 - INFO - Video thread started with source: Camera
2025-11-25 09:45:45,656 - INFO - Video thread started with source: Camera
2025-11-25 09:45:45,658 - ERROR - ❌ No camera found!
2025-11-25 09:45:45,658 - ERROR - ❌ No camera found!
2025-11-25 09:45:45,693 - INFO - Frame 354 | PERCLOS: 0.00 | Yaw: 5.7° | Alerts: 1
2025-11-25 09:45:45,874 - INFO - Video thread started with source: Camera
2025-11-25 09:45:45,874 - INFO - Video thread started with source: Camera
2025-11-25 09:45:45,875 - ERROR - ❌ No camera found!
2025-11-25 09:45:45,875 - ERROR - ❌ No camera found!
2025-11-25 09:45:46,071 - INFO - Video thread started with source: Camera
2025-11-25 09:45:46,073 - INFO - Video thread started with source: Camera
2025-11-25 09:45:46,074 - ERROR - ❌ No camera found!
2025-11-25 09:45:46,076 - ERROR - ❌ No camera found!
2025-11-25 09:45:46,108 - INFO - Frame 356 | PERCLOS: 0.00 | Yaw: 5.5° | Alerts: 1
2025-11-25 09:45:46,262 - INFO - Video thread started with source: Camera
2025-11-25 09:45:46,263 - INFO - Video thread started with source: Camera
2025-11-25 09:45:46,268 - ERROR - ❌ No camera found!
2025-11-25 09:45:46,268 - ERROR - ❌ No camera found!
2025-11-25 09:45:46,485 - INFO - Video thread started with source: Camera
2025-11-25 09:45:46,487 - ERROR - ❌ No camera found!
2025-11-25 09:45:46,489 - INFO - Frame 358 | PERCLOS: 0.00 | Yaw: 7.3° | Alerts: 1
2025-11-25 09:45:46,492 - INFO - Video thread started with source: Camera
2025-11-25 09:45:46,495 - ERROR - ❌ No camera found!
2025-11-25 09:45:46,685 - INFO - Video thread started with source: Camera
2025-11-25 09:45:46,689 - INFO - Video thread started with source: Camera
2025-11-25 09:45:46,690 - ERROR - ❌ No camera found!
2025-11-25 09:45:46,695 - ERROR - ❌ No camera found!
2025-11-25 09:45:46,723 - INFO - Frame 360 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:46,904 - INFO - Video thread started with source: Camera
2025-11-25 09:45:46,904 - INFO - Video thread started with source: Camera
2025-11-25 09:45:46,906 - ERROR - ❌ No camera found!
2025-11-25 09:45:46,907 - ERROR - ❌ No camera found!
2025-11-25 09:45:46,944 - INFO - Frame 362 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:47,103 - INFO - Video thread started with source: Camera
2025-11-25 09:45:47,106 - ERROR - ❌ No camera found!
2025-11-25 09:45:47,116 - INFO - Video thread started with source: Camera
2025-11-25 09:45:47,117 - ERROR - ❌ No camera found!
2025-11-25 09:45:47,289 - INFO - Video thread started with source: Camera
2025-11-25 09:45:47,291 - INFO - Video thread started with source: Camera
2025-11-25 09:45:47,291 - INFO - Frame 364 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:47,294 - ERROR - ❌ No camera found!
2025-11-25 09:45:47,295 - ERROR - ❌ No camera found!
2025-11-25 09:45:47,484 - INFO - Video thread started with source: Camera
2025-11-25 09:45:47,488 - ERROR - ❌ No camera found!
2025-11-25 09:45:47,494 - INFO - Video thread started with source: Camera
2025-11-25 09:45:47,497 - ERROR - ❌ No camera found!
2025-11-25 09:45:47,498 - INFO - Frame 366 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:47,691 - INFO - Video thread started with source: Camera
2025-11-25 09:45:47,692 - INFO - Video thread started with source: Camera
2025-11-25 09:45:47,693 - ERROR - ❌ No camera found!
2025-11-25 09:45:47,696 - ERROR - ❌ No camera found!
2025-11-25 09:45:47,724 - INFO - Frame 368 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:47,887 - INFO - Video thread started with source: Camera
2025-11-25 09:45:47,887 - INFO - Video thread started with source: Camera
2025-11-25 09:45:47,888 - ERROR - ❌ No camera found!
2025-11-25 09:45:47,891 - ERROR - ❌ No camera found!
2025-11-25 09:45:48,070 - INFO - Frame 370 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:48,076 - INFO - Video thread started with source: Camera
2025-11-25 09:45:48,077 - INFO - Video thread started with source: Camera
2025-11-25 09:45:48,080 - ERROR - ❌ No camera found!
2025-11-25 09:45:48,084 - ERROR - ❌ No camera found!
2025-11-25 09:45:48,270 - INFO - Video thread started with source: Camera
2025-11-25 09:45:48,270 - INFO - Video thread started with source: Camera
2025-11-25 09:45:48,272 - ERROR - ❌ No camera found!
2025-11-25 09:45:48,276 - ERROR - ❌ No camera found!
2025-11-25 09:45:48,276 - INFO - Frame 372 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:48,475 - INFO - Video thread started with source: Camera
2025-11-25 09:45:48,476 - INFO - Video thread started with source: Camera
2025-11-25 09:45:48,476 - ERROR - ❌ No camera found!
2025-11-25 09:45:48,477 - ERROR - ❌ No camera found!
2025-11-25 09:45:48,657 - INFO - Frame 374 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:48,664 - INFO - Video thread started with source: Camera
2025-11-25 09:45:48,669 - ERROR - ❌ No camera found!
2025-11-25 09:45:48,669 - INFO - Video thread started with source: Camera
2025-11-25 09:45:48,673 - ERROR - ❌ No camera found!
2025-11-25 09:45:48,854 - INFO - Video thread started with source: Camera
2025-11-25 09:45:48,855 - ERROR - ❌ No camera found!
2025-11-25 09:45:48,856 - INFO - Video thread started with source: Camera
2025-11-25 09:45:48,856 - ERROR - ❌ No camera found!
2025-11-25 09:45:48,864 - INFO - Frame 376 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:49,048 - INFO - Video thread started with source: Camera
2025-11-25 09:45:49,050 - INFO - Video thread started with source: Camera
2025-11-25 09:45:49,050 - ERROR - ❌ No camera found!
2025-11-25 09:45:49,051 - ERROR - ❌ No camera found!
2025-11-25 09:45:49,090 - INFO - Frame 378 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:49,240 - INFO - Video thread started with source: Camera
2025-11-25 09:45:49,244 - ERROR - ❌ No camera found!
2025-11-25 09:45:49,244 - INFO - Video thread started with source: Camera
2025-11-25 09:45:49,248 - ERROR - ❌ No camera found!
2025-11-25 09:45:49,426 - INFO - Frame 380 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:49,427 - INFO - Video thread started with source: Camera
2025-11-25 09:45:49,432 - INFO - Video thread started with source: Camera
2025-11-25 09:45:49,434 - ERROR - ❌ No camera found!
2025-11-25 09:45:49,438 - ERROR - ❌ No camera found!
2025-11-25 09:45:49,635 - INFO - Video thread started with source: Camera
2025-11-25 09:45:49,637 - INFO - Video thread started with source: Camera
2025-11-25 09:45:49,637 - ERROR - ❌ No camera found!
2025-11-25 09:45:49,638 - ERROR - ❌ No camera found!
2025-11-25 09:45:49,847 - INFO - Video thread started with source: Camera
2025-11-25 09:45:49,849 - INFO - Frame 382 | PERCLOS: 0.00 | Yaw: 14.6° | Alerts: 0
2025-11-25 09:45:49,851 - INFO - Video thread started with source: Camera
2025-11-25 09:45:49,852 - ERROR - ❌ No camera found!
2025-11-25 09:45:49,854 - ERROR - ❌ No camera found!
2025-11-25 09:45:50,041 - INFO - Video thread started with source: Camera
2025-11-25 09:45:50,045 - ERROR - ❌ No camera found!
2025-11-25 09:45:50,047 - INFO - Video thread started with source: Camera
2025-11-25 09:45:50,051 - ERROR - ❌ No camera found!
2025-11-25 09:45:50,082 - INFO - Frame 384 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:50,242 - INFO - Video thread started with source: Camera
2025-11-25 09:45:50,244 - INFO - Video thread started with source: Camera
2025-11-25 09:45:50,244 - ERROR - ❌ No camera found!
2025-11-25 09:45:50,248 - ERROR - ❌ No camera found!
2025-11-25 09:45:50,441 - INFO - Video thread started with source: Camera
2025-11-25 09:45:50,441 - INFO - Video thread started with source: Camera
2025-11-25 09:45:50,443 - ERROR - ❌ No camera found!
2025-11-25 09:45:50,444 - ERROR - ❌ No camera found!
2025-11-25 09:45:50,658 - INFO - Video thread started with source: Camera
2025-11-25 09:45:50,659 - INFO - Video thread started with source: Camera
2025-11-25 09:45:50,662 - ERROR - ❌ No camera found!
2025-11-25 09:45:50,662 - ERROR - ❌ No camera found!
2025-11-25 09:45:50,662 - INFO - Frame 386 | PERCLOS: 0.00 | Yaw: -6.2° | Alerts: 0
2025-11-25 09:45:50,876 - INFO - Video thread started with source: Camera
2025-11-25 09:45:50,877 - INFO - Video thread started with source: Camera
2025-11-25 09:45:50,881 - ERROR - ❌ No camera found!
2025-11-25 09:45:50,881 - ERROR - ❌ No camera found!
2025-11-25 09:45:51,081 - INFO - Video thread started with source: Camera
2025-11-25 09:45:51,083 - ERROR - ❌ No camera found!
2025-11-25 09:45:51,083 - INFO - Frame 388 | PERCLOS: 0.00 | Yaw: -0.4° | Alerts: 0
2025-11-25 09:45:51,084 - INFO - Video thread started with source: Camera
2025-11-25 09:45:51,088 - ERROR - ❌ No camera found!
2025-11-25 09:45:51,282 - INFO - Video thread started with source: Camera
2025-11-25 09:45:51,285 - ERROR - ❌ No camera found!
2025-11-25 09:45:51,287 - INFO - Video thread started with source: Camera
2025-11-25 09:45:51,295 - ERROR - ❌ No camera found!
2025-11-25 09:45:51,481 - INFO - Video thread started with source: Camera
2025-11-25 09:45:51,482 - INFO - Video thread started with source: Camera
2025-11-25 09:45:51,484 - ERROR - ❌ No camera found!
2025-11-25 09:45:51,486 - ERROR - ❌ No camera found!
2025-11-25 09:45:51,499 - INFO - Frame 390 | PERCLOS: 0.00 | Yaw: -2.1° | Alerts: 1
2025-11-25 09:45:51,672 - INFO - Video thread started with source: Camera
2025-11-25 09:45:51,673 - INFO - Video thread started with source: Camera
2025-11-25 09:45:51,674 - ERROR - ❌ No camera found!
2025-11-25 09:45:51,674 - ERROR - ❌ No camera found!
2025-11-25 09:45:51,884 - INFO - Video thread started with source: Camera
2025-11-25 09:45:51,885 - ERROR - ❌ No camera found!
2025-11-25 09:45:51,885 - INFO - Video thread started with source: Camera
2025-11-25 09:45:51,887 - INFO - Frame 392 | PERCLOS: 0.00 | Yaw: -3.1° | Alerts: 1
2025-11-25 09:45:51,887 - ERROR - ❌ No camera found!
2025-11-25 09:45:52,089 - INFO - Video thread started with source: Camera
2025-11-25 09:45:52,090 - INFO - Video thread started with source: Camera
2025-11-25 09:45:52,090 - ERROR - ❌ No camera found!
2025-11-25 09:45:52,092 - ERROR - ❌ No camera found!
2025-11-25 09:45:52,298 - INFO - Video thread started with source: Camera
2025-11-25 09:45:52,300 - INFO - Video thread started with source: Camera
2025-11-25 09:45:52,300 - ERROR - ❌ No camera found!
2025-11-25 09:45:52,302 - INFO - Frame 394 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:45:52,304 - ERROR - ❌ No camera found!
2025-11-25 09:45:52,493 - INFO - Video thread started with source: Camera
2025-11-25 09:45:52,494 - INFO - Video thread started with source: Camera
2025-11-25 09:45:52,495 - ERROR - ❌ No camera found!
2025-11-25 09:45:52,496 - ERROR - ❌ No camera found!
2025-11-25 09:45:52,709 - INFO - Video thread started with source: Camera
2025-11-25 09:45:52,712 - ERROR - ❌ No camera found!
2025-11-25 09:45:52,713 - INFO - Video thread started with source: Camera
2025-11-25 09:45:52,715 - ERROR - ❌ No camera found!
2025-11-25 09:45:52,918 - INFO - Video thread started with source: Camera
2025-11-25 09:45:52,918 - INFO - Video thread started with source: Camera
2025-11-25 09:45:52,919 - ERROR - ❌ No camera found!
2025-11-25 09:45:52,919 - ERROR - ❌ No camera found!
2025-11-25 09:45:52,930 - INFO - Frame 396 | PERCLOS: 0.00 | Yaw: 0.7° | Alerts: 1
2025-11-25 09:45:53,123 - INFO - Video thread started with source: Camera
2025-11-25 09:45:53,125 - ERROR - ❌ No camera found!
2025-11-25 09:45:53,125 - INFO - Video thread started with source: Camera
2025-11-25 09:45:53,130 - ERROR - ❌ No camera found!
2025-11-25 09:45:53,359 - INFO - Video thread started with source: Camera
2025-11-25 09:45:53,359 - INFO - Frame 398 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 1
2025-11-25 09:45:53,364 - INFO - Video thread started with source: Camera
2025-11-25 09:45:53,364 - ERROR - ❌ No camera found!
2025-11-25 09:45:53,369 - ERROR - ❌ No camera found!
2025-11-25 09:45:53,562 - INFO - Video thread started with source: Camera
2025-11-25 09:45:53,566 - INFO - Video thread started with source: Camera
2025-11-25 09:45:53,567 - ERROR - ❌ No camera found!
2025-11-25 09:45:53,568 - ERROR - ❌ No camera found!
2025-11-25 09:45:53,765 - INFO - Video thread started with source: Camera
2025-11-25 09:45:53,765 - INFO - Frame 400 | PERCLOS: 0.00 | Yaw: 2.8° | Alerts: 1
2025-11-25 09:45:53,768 - INFO - Video thread started with source: Camera
2025-11-25 09:45:53,768 - ERROR - ❌ No camera found!
2025-11-25 09:45:53,774 - ERROR - ❌ No camera found!
2025-11-25 09:45:53,980 - INFO - Video thread started with source: Camera
2025-11-25 09:45:53,982 - ERROR - ❌ No camera found!
2025-11-25 09:45:53,984 - INFO - Video thread started with source: Camera
2025-11-25 09:45:53,986 - ERROR - ❌ No camera found!
2025-11-25 09:45:54,221 - INFO - Video thread started with source: Camera
2025-11-25 09:45:54,222 - ERROR - ❌ No camera found!
2025-11-25 09:45:54,227 - INFO - Video thread started with source: Camera
2025-11-25 09:45:54,228 - ERROR - ❌ No camera found!
2025-11-25 09:45:54,239 - INFO - Frame 402 | PERCLOS: 0.00 | Yaw: 3.7° | Alerts: 1
2025-11-25 09:45:54,426 - INFO - Video thread started with source: Camera
2025-11-25 09:45:54,426 - INFO - Video thread started with source: Camera
2025-11-25 09:45:54,429 - ERROR - ❌ No camera found!
2025-11-25 09:45:54,429 - ERROR - ❌ No camera found!
2025-11-25 09:45:54,652 - INFO - Video thread started with source: Camera
2025-11-25 09:45:54,655 - ERROR - ❌ No camera found!
2025-11-25 09:45:54,655 - INFO - Video thread started with source: Camera
2025-11-25 09:45:54,657 - INFO - Frame 404 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 1
2025-11-25 09:45:54,660 - ERROR - ❌ No camera found!
2025-11-25 09:45:54,859 - INFO - Video thread started with source: Camera
2025-11-25 09:45:54,860 - ERROR - ❌ No camera found!
2025-11-25 09:45:54,860 - INFO - Video thread started with source: Camera
2025-11-25 09:45:54,863 - ERROR - ❌ No camera found!
2025-11-25 09:45:55,078 - INFO - Video thread started with source: Camera
2025-11-25 09:45:55,078 - INFO - Frame 406 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 1
2025-11-25 09:45:55,082 - ERROR - ❌ No camera found!
2025-11-25 09:45:55,085 - INFO - Video thread started with source: Camera
2025-11-25 09:45:55,086 - ERROR - ❌ No camera found!
2025-11-25 09:45:55,287 - INFO - Video thread started with source: Camera
2025-11-25 09:45:55,287 - INFO - Video thread started with source: Camera
2025-11-25 09:45:55,288 - ERROR - ❌ No camera found!
2025-11-25 09:45:55,289 - ERROR - ❌ No camera found!
2025-11-25 09:45:55,579 - INFO - Video thread started with source: Camera
2025-11-25 09:45:55,579 - ERROR - ❌ No camera found!
2025-11-25 09:45:55,581 - INFO - Video thread started with source: Camera
2025-11-25 09:45:55,590 - ERROR - ❌ No camera found!
2025-11-25 09:45:55,778 - INFO - Frame 408 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-25 09:45:55,785 - INFO - Video thread started with source: Camera
2025-11-25 09:45:55,787 - INFO - Video thread started with source: Camera
2025-11-25 09:45:55,787 - ERROR - ❌ No camera found!
2025-11-25 09:45:55,790 - ERROR - ❌ No camera found!
2025-11-25 09:45:55,980 - INFO - Video thread started with source: Camera
2025-11-25 09:45:55,982 - ERROR - ❌ No camera found!
2025-11-25 09:45:55,982 - INFO - Video thread started with source: Camera
2025-11-25 09:45:55,986 - ERROR - ❌ No camera found!
2025-11-25 09:45:56,184 - INFO - Video thread started with source: Camera
2025-11-25 09:45:56,185 - ERROR - ❌ No camera found!
2025-11-25 09:45:56,185 - INFO - Frame 410 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 1
2025-11-25 09:45:56,193 - INFO - Video thread started with source: Camera
2025-11-25 09:45:56,195 - ERROR - ❌ No camera found!
2025-11-25 09:45:56,374 - INFO - Video thread started with source: Camera
2025-11-25 09:45:56,375 - ERROR - ❌ No camera found!
2025-11-25 09:45:56,376 - INFO - Video thread started with source: Camera
2025-11-25 09:45:56,379 - ERROR - ❌ No camera found!
2025-11-25 09:45:56,608 - INFO - Video thread started with source: Camera
2025-11-25 09:45:56,610 - INFO - Video thread started with source: Camera
2025-11-25 09:45:56,610 - ERROR - ❌ No camera found!
2025-11-25 09:45:56,614 - INFO - Frame 412 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 1
2025-11-25 09:45:56,614 - ERROR - ❌ No camera found!
2025-11-25 09:45:56,811 - INFO - Video thread started with source: Camera
2025-11-25 09:45:56,811 - INFO - Video thread started with source: Camera
2025-11-25 09:45:56,814 - ERROR - ❌ No camera found!
2025-11-25 09:45:56,815 - ERROR - ❌ No camera found!
2025-11-25 09:45:57,016 - INFO - Video thread started with source: Camera
2025-11-25 09:45:57,020 - INFO - Video thread started with source: Camera
2025-11-25 09:45:57,020 - ERROR - ❌ No camera found!
2025-11-25 09:45:57,025 - ERROR - ❌ No camera found!
2025-11-25 09:45:57,228 - INFO - Frame 414 | PERCLOS: 0.00 | Yaw: 4.4° | Alerts: 1
2025-11-25 09:45:57,232 - INFO - Video thread started with source: Camera
2025-11-25 09:45:57,234 - ERROR - ❌ No camera found!
2025-11-25 09:45:57,235 - INFO - Video thread started with source: Camera
2025-11-25 09:45:57,236 - ERROR - ❌ No camera found!
2025-11-25 09:45:57,443 - INFO - Video thread started with source: Camera
2025-11-25 09:45:57,443 - INFO - Video thread started with source: Camera
2025-11-25 09:45:57,446 - ERROR - ❌ No camera found!
2025-11-25 09:45:57,446 - ERROR - ❌ No camera found!
2025-11-25 09:45:57,669 - INFO - Video thread started with source: Camera
2025-11-25 09:45:57,670 - INFO - Frame 416 | PERCLOS: 0.00 | Yaw: 4.5° | Alerts: 1
2025-11-25 09:45:57,670 - INFO - Video thread started with source: Camera
2025-11-25 09:45:57,670 - ERROR - ❌ No camera found!
2025-11-25 09:45:57,672 - ERROR - ❌ No camera found!
2025-11-25 09:45:57,866 - INFO - Video thread started with source: Camera
2025-11-25 09:45:57,866 - INFO - Video thread started with source: Camera
2025-11-25 09:45:57,868 - ERROR - ❌ No camera found!
2025-11-25 09:45:57,869 - ERROR - ❌ No camera found!
2025-11-25 09:45:58,067 - INFO - Video thread started with source: Camera
2025-11-25 09:45:58,069 - INFO - Video thread started with source: Camera
2025-11-25 09:45:58,069 - ERROR - ❌ No camera found!
2025-11-25 09:45:58,072 - ERROR - ❌ No camera found!
2025-11-25 09:45:58,072 - INFO - Frame 418 | PERCLOS: 0.00 | Yaw: 4.6° | Alerts: 1
2025-11-25 09:45:58,289 - INFO - Video thread started with source: Camera
2025-11-25 09:45:58,289 - INFO - Video thread started with source: Camera
2025-11-25 09:45:58,290 - ERROR - ❌ No camera found!
2025-11-25 09:45:58,293 - ERROR - ❌ No camera found!
2025-11-25 09:45:58,503 - INFO - Video thread started with source: Camera
2025-11-25 09:45:58,508 - INFO - Video thread started with source: Camera
2025-11-25 09:45:58,509 - ERROR - ❌ No camera found!
2025-11-25 09:45:58,511 - ERROR - ❌ No camera found!
2025-11-25 09:45:58,734 - INFO - Video thread started with source: Camera
2025-11-25 09:45:58,734 - INFO - Video thread started with source: Camera
2025-11-25 09:45:58,735 - ERROR - ❌ No camera found!
2025-11-25 09:45:58,736 - ERROR - ❌ No camera found!
2025-11-25 09:45:58,737 - INFO - Frame 420 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 1
2025-11-25 09:45:58,955 - INFO - Video thread started with source: Camera
2025-11-25 09:45:58,955 - INFO - Video thread started with source: Camera
2025-11-25 09:45:58,957 - ERROR - ❌ No camera found!
2025-11-25 09:45:58,957 - ERROR - ❌ No camera found!
2025-11-25 09:45:59,164 - INFO - Video thread started with source: Camera
2025-11-25 09:45:59,165 - INFO - Video thread started with source: Camera
2025-11-25 09:45:59,165 - INFO - Frame 422 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 1
2025-11-25 09:45:59,167 - ERROR - ❌ No camera found!
2025-11-25 09:45:59,169 - ERROR - ❌ No camera found!
2025-11-25 09:45:59,374 - INFO - Video thread started with source: Camera
2025-11-25 09:45:59,376 - INFO - Video thread started with source: Camera
2025-11-25 09:45:59,376 - ERROR - ❌ No camera found!
2025-11-25 09:45:59,379 - ERROR - ❌ No camera found!
2025-11-25 09:45:59,580 - INFO - Video thread started with source: Camera
2025-11-25 09:45:59,581 - INFO - Video thread started with source: Camera
2025-11-25 09:45:59,583 - ERROR - ❌ No camera found!
2025-11-25 09:45:59,583 - ERROR - ❌ No camera found!
2025-11-25 09:45:59,584 - INFO - Frame 424 | PERCLOS: 0.00 | Yaw: 1.2° | Alerts: 1
2025-11-25 09:45:59,782 - INFO - Video thread started with source: Camera
2025-11-25 09:45:59,783 - INFO - Video thread started with source: Camera
2025-11-25 09:45:59,785 - ERROR - ❌ No camera found!
2025-11-25 09:45:59,785 - ERROR - ❌ No camera found!
2025-11-25 09:46:00,005 - INFO - Video thread started with source: Camera
2025-11-25 09:46:00,007 - INFO - Video thread started with source: Camera
2025-11-25 09:46:00,008 - ERROR - ❌ No camera found!
2025-11-25 09:46:00,015 - ERROR - ❌ No camera found!
2025-11-25 09:46:00,023 - INFO - Frame 426 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 1
2025-11-25 09:46:00,208 - INFO - Video thread started with source: Camera
2025-11-25 09:46:00,210 - ERROR - ❌ No camera found!
2025-11-25 09:46:00,211 - INFO - Video thread started with source: Camera
2025-11-25 09:46:00,215 - ERROR - ❌ No camera found!
2025-11-25 09:46:00,424 - INFO - Video thread started with source: Camera
2025-11-25 09:46:00,425 - INFO - Frame 428 | PERCLOS: 0.00 | Yaw: 2.9° | Alerts: 1
2025-11-25 09:46:00,427 - ERROR - ❌ No camera found!
2025-11-25 09:46:00,427 - INFO - Video thread started with source: Camera
2025-11-25 09:46:00,430 - ERROR - ❌ No camera found!
2025-11-25 09:46:00,633 - INFO - Video thread started with source: Camera
2025-11-25 09:46:00,636 - INFO - Video thread started with source: Camera
2025-11-25 09:46:00,637 - ERROR - ❌ No camera found!
2025-11-25 09:46:00,640 - ERROR - ❌ No camera found!
2025-11-25 09:46:00,837 - INFO - Frame 430 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 1
2025-11-25 09:46:00,842 - INFO - Video thread started with source: Camera
2025-11-25 09:46:00,842 - INFO - Video thread started with source: Camera
2025-11-25 09:46:00,843 - ERROR - ❌ No camera found!
2025-11-25 09:46:00,844 - ERROR - ❌ No camera found!
2025-11-25 09:46:01,045 - INFO - Video thread started with source: Camera
2025-11-25 09:46:01,046 - ERROR - ❌ No camera found!
2025-11-25 09:46:01,052 - INFO - Video thread started with source: Camera
2025-11-25 09:46:01,056 - ERROR - ❌ No camera found!
2025-11-25 09:46:01,264 - INFO - Video thread started with source: Camera
2025-11-25 09:46:01,266 - INFO - Video thread started with source: Camera
2025-11-25 09:46:01,266 - ERROR - ❌ No camera found!
2025-11-25 09:46:01,269 - ERROR - ❌ No camera found!
2025-11-25 09:46:01,470 - INFO - Frame 432 | PERCLOS: 0.00 | Yaw: 3.6° | Alerts: 1
2025-11-25 09:46:01,477 - INFO - Video thread started with source: Camera
2025-11-25 09:46:01,480 - ERROR - ❌ No camera found!
2025-11-25 09:46:01,480 - INFO - Video thread started with source: Camera
2025-11-25 09:46:01,482 - ERROR - ❌ No camera found!
2025-11-25 09:46:01,684 - INFO - Video thread started with source: Camera
2025-11-25 09:46:01,690 - ERROR - ❌ No camera found!
2025-11-25 09:46:01,693 - INFO - Video thread started with source: Camera
2025-11-25 09:46:01,694 - ERROR - ❌ No camera found!
2025-11-25 09:46:01,890 - INFO - Video thread started with source: Camera
2025-11-25 09:46:01,890 - INFO - Video thread started with source: Camera
2025-11-25 09:46:01,891 - ERROR - ❌ No camera found!
2025-11-25 09:46:01,893 - ERROR - ❌ No camera found!
2025-11-25 09:46:01,915 - INFO - Frame 434 | PERCLOS: 0.00 | Yaw: 3.1° | Alerts: 1
2025-11-25 09:46:02,101 - INFO - Video thread started with source: Camera
2025-11-25 09:46:02,101 - INFO - Video thread started with source: Camera
2025-11-25 09:46:02,102 - ERROR - ❌ No camera found!
2025-11-25 09:46:02,104 - ERROR - ❌ No camera found!
2025-11-25 09:46:02,317 - INFO - Video thread started with source: Camera
2025-11-25 09:46:02,320 - INFO - Video thread started with source: Camera
2025-11-25 09:46:02,323 - ERROR - ❌ No camera found!
2025-11-25 09:46:02,324 - ERROR - ❌ No camera found!
2025-11-25 09:46:02,324 - INFO - Frame 436 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 1
2025-11-25 09:46:02,524 - INFO - Video thread started with source: Camera
2025-11-25 09:46:02,528 - ERROR - ❌ No camera found!
2025-11-25 09:46:02,528 - INFO - Video thread started with source: Camera
2025-11-25 09:46:02,530 - ERROR - ❌ No camera found!
2025-11-25 09:46:02,759 - INFO - Video thread started with source: Camera
2025-11-25 09:46:02,761 - INFO - Video thread started with source: Camera
2025-11-25 09:46:02,764 - ERROR - ❌ No camera found!
2025-11-25 09:46:02,764 - ERROR - ❌ No camera found!
2025-11-25 09:46:02,809 - INFO - Frame 438 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 1
2025-11-25 09:46:02,996 - INFO - Video thread started with source: Camera
2025-11-25 09:46:02,998 - ERROR - ❌ No camera found!
2025-11-25 09:46:02,998 - INFO - Video thread started with source: Camera
2025-11-25 09:46:03,000 - ERROR - ❌ No camera found!
2025-11-25 09:46:03,200 - INFO - Video thread started with source: Camera
2025-11-25 09:46:03,200 - INFO - Video thread started with source: Camera
2025-11-25 09:46:03,201 - INFO - Frame 440 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-25 09:46:03,202 - ERROR - ❌ No camera found!
2025-11-25 09:46:03,202 - ERROR - ❌ No camera found!
2025-11-25 09:46:03,410 - INFO - Video thread started with source: Camera
2025-11-25 09:46:03,415 - ERROR - ❌ No camera found!
2025-11-25 09:46:03,416 - INFO - Video thread started with source: Camera
2025-11-25 09:46:03,421 - ERROR - ❌ No camera found!
2025-11-25 09:46:03,625 - INFO - Video thread started with source: Camera
2025-11-25 09:46:03,628 - ERROR - ❌ No camera found!
2025-11-25 09:46:03,629 - INFO - Frame 442 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 1
2025-11-25 09:46:03,629 - INFO - Video thread started with source: Camera
2025-11-25 09:46:03,633 - ERROR - ❌ No camera found!
2025-11-25 09:46:03,825 - INFO - Video thread started with source: Camera
2025-11-25 09:46:03,827 - ERROR - ❌ No camera found!
2025-11-25 09:46:03,827 - INFO - Video thread started with source: Camera
2025-11-25 09:46:03,832 - ERROR - ❌ No camera found!
2025-11-25 09:46:04,041 - INFO - Video thread started with source: Camera
2025-11-25 09:46:04,048 - INFO - Video thread started with source: Camera
2025-11-25 09:46:04,049 - ERROR - ❌ No camera found!
2025-11-25 09:46:04,051 - ERROR - ❌ No camera found!
2025-11-25 09:46:04,253 - INFO - Frame 444 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 1
2025-11-25 09:46:04,254 - INFO - Video thread started with source: Camera
2025-11-25 09:46:04,257 - ERROR - ❌ No camera found!
2025-11-25 09:46:04,257 - INFO - Video thread started with source: Camera
2025-11-25 09:46:04,258 - ERROR - ❌ No camera found!
2025-11-25 09:46:04,463 - INFO - Video thread started with source: Camera
2025-11-25 09:46:04,463 - INFO - Video thread started with source: Camera
2025-11-25 09:46:04,464 - ERROR - ❌ No camera found!
2025-11-25 09:46:04,465 - ERROR - ❌ No camera found!
2025-11-25 09:46:04,673 - INFO - Frame 446 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-25 09:46:04,675 - INFO - Video thread started with source: Camera
2025-11-25 09:46:04,675 - INFO - Video thread started with source: Camera
2025-11-25 09:46:04,677 - ERROR - ❌ No camera found!
2025-11-25 09:46:04,678 - ERROR - ❌ No camera found!
2025-11-25 09:46:04,880 - INFO - Video thread started with source: Camera
2025-11-25 09:46:04,883 - INFO - Video thread started with source: Camera
2025-11-25 09:46:04,883 - ERROR - ❌ No camera found!
2025-11-25 09:46:04,887 - ERROR - ❌ No camera found!
2025-11-25 09:46:05,099 - INFO - Video thread started with source: Camera
2025-11-25 09:46:05,099 - INFO - Video thread started with source: Camera
2025-11-25 09:46:05,102 - ERROR - ❌ No camera found!
2025-11-25 09:46:05,102 - ERROR - ❌ No camera found!
2025-11-25 09:46:05,105 - INFO - Frame 448 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-25 09:46:05,300 - INFO - Video thread started with source: Camera
2025-11-25 09:46:05,300 - INFO - Video thread started with source: Camera
2025-11-25 09:46:05,301 - ERROR - ❌ No camera found!
2025-11-25 09:46:05,303 - ERROR - ❌ No camera found!
2025-11-25 09:46:05,502 - INFO - Video thread started with source: Camera
2025-11-25 09:46:05,504 - INFO - Video thread started with source: Camera
2025-11-25 09:46:05,504 - ERROR - ❌ No camera found!
2025-11-25 09:46:05,507 - ERROR - ❌ No camera found!
2025-11-25 09:46:05,725 - INFO - Video thread started with source: Camera
2025-11-25 09:46:05,726 - INFO - Video thread started with source: Camera
2025-11-25 09:46:05,727 - ERROR - ❌ No camera found!
2025-11-25 09:46:05,728 - ERROR - ❌ No camera found!
2025-11-25 09:46:05,741 - INFO - Frame 450 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 1
2025-11-25 09:46:05,951 - INFO - Video thread started with source: Camera
2025-11-25 09:46:05,956 - ERROR - ❌ No camera found!
2025-11-25 09:46:05,956 - INFO - Video thread started with source: Camera
2025-11-25 09:46:05,960 - ERROR - ❌ No camera found!
2025-11-25 09:46:06,180 - INFO - Frame 452 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-25 09:46:06,180 - INFO - Video thread started with source: Camera
2025-11-25 09:46:06,185 - INFO - Video thread started with source: Camera
2025-11-25 09:46:06,186 - ERROR - ❌ No camera found!
2025-11-25 09:46:06,186 - ERROR - ❌ No camera found!
2025-11-25 09:46:06,386 - INFO - Video thread started with source: Camera
2025-11-25 09:46:06,386 - INFO - Video thread started with source: Camera
2025-11-25 09:46:06,389 - ERROR - ❌ No camera found!
2025-11-25 09:46:06,391 - ERROR - ❌ No camera found!
2025-11-25 09:46:06,613 - INFO - Video thread started with source: Camera
2025-11-25 09:46:06,618 - INFO - Video thread started with source: Camera
2025-11-25 09:46:06,618 - ERROR - ❌ No camera found!
2025-11-25 09:46:06,621 - ERROR - ❌ No camera found!
2025-11-25 09:46:06,810 - INFO - Video thread started with source: Camera
2025-11-25 09:46:06,811 - INFO - Video thread started with source: Camera
2025-11-25 09:46:06,812 - ERROR - ❌ No camera found!
2025-11-25 09:46:06,815 - INFO - Frame 454 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-25 09:46:06,815 - ERROR - ❌ No camera found!
2025-11-25 09:46:07,030 - INFO - Video thread started with source: Camera
2025-11-25 09:46:07,031 - ERROR - ❌ No camera found!
2025-11-25 09:46:07,032 - INFO - Video thread started with source: Camera
2025-11-25 09:46:07,041 - ERROR - ❌ No camera found!
2025-11-25 09:46:07,254 - INFO - Video thread started with source: Camera
2025-11-25 09:46:07,256 - ERROR - ❌ No camera found!
2025-11-25 09:46:07,257 - INFO - Video thread started with source: Camera
2025-11-25 09:46:07,260 - ERROR - ❌ No camera found!
2025-11-25 09:46:07,444 - INFO - Frame 456 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-25 09:46:07,450 - INFO - Video thread started with source: Camera
2025-11-25 09:46:07,453 - ERROR - ❌ No camera found!
2025-11-25 09:46:07,453 - INFO - Video thread started with source: Camera
2025-11-25 09:46:07,457 - ERROR - ❌ No camera found!
2025-11-25 09:46:07,641 - INFO - Video thread started with source: Camera
2025-11-25 09:46:07,641 - INFO - Video thread started with source: Camera
2025-11-25 09:46:07,643 - ERROR - ❌ No camera found!
2025-11-25 09:46:07,644 - ERROR - ❌ No camera found!
2025-11-25 09:46:07,855 - INFO - Video thread started with source: Camera
2025-11-25 09:46:07,855 - INFO - Video thread started with source: Camera
2025-11-25 09:46:07,855 - ERROR - ❌ No camera found!
2025-11-25 09:46:07,856 - ERROR - ❌ No camera found!
2025-11-25 09:46:07,877 - INFO - Frame 458 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 1
2025-11-25 09:46:08,054 - INFO - Video thread started with source: Camera
2025-11-25 09:46:08,055 - INFO - Video thread started with source: Camera
2025-11-25 09:46:08,057 - ERROR - ❌ No camera found!
2025-11-25 09:46:08,059 - ERROR - ❌ No camera found!
2025-11-25 09:46:08,256 - INFO - Video thread started with source: Camera
2025-11-25 09:46:08,256 - INFO - Frame 460 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 1
2025-11-25 09:46:08,258 - ERROR - ❌ No camera found!
2025-11-25 09:46:08,262 - INFO - Video thread started with source: Camera
2025-11-25 09:46:08,264 - ERROR - ❌ No camera found!
2025-11-25 09:46:08,472 - INFO - Video thread started with source: Camera
2025-11-25 09:46:08,475 - ERROR - ❌ No camera found!
2025-11-25 09:46:08,476 - INFO - Video thread started with source: Camera
2025-11-25 09:46:08,477 - ERROR - ❌ No camera found!
2025-11-25 09:46:08,672 - INFO - Video thread started with source: Camera
2025-11-25 09:46:08,675 - ERROR - ❌ No camera found!
2025-11-25 09:46:08,676 - INFO - Video thread started with source: Camera
2025-11-25 09:46:08,676 - ERROR - ❌ No camera found!
2025-11-25 09:46:08,884 - INFO - Frame 462 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-25 09:46:08,893 - INFO - Video thread started with source: Camera
2025-11-25 09:46:08,893 - INFO - Video thread started with source: Camera
2025-11-25 09:46:08,895 - ERROR - ❌ No camera found!
2025-11-25 09:46:08,895 - ERROR - ❌ No camera found!
2025-11-25 09:46:09,091 - INFO - Video thread started with source: Camera
2025-11-25 09:46:09,096 - INFO - Video thread started with source: Camera
2025-11-25 09:46:09,096 - ERROR - ❌ No camera found!
2025-11-25 09:46:09,099 - ERROR - ❌ No camera found!
2025-11-25 09:46:09,290 - INFO - Video thread started with source: Camera
2025-11-25 09:46:09,294 - ERROR - ❌ No camera found!
2025-11-25 09:46:09,296 - INFO - Video thread started with source: Camera
2025-11-25 09:46:09,299 - ERROR - ❌ No camera found!
2025-11-25 09:46:09,493 - INFO - Frame 464 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-25 09:46:09,499 - INFO - Video thread started with source: Camera
2025-11-25 09:46:09,499 - INFO - Video thread started with source: Camera
2025-11-25 09:46:09,504 - ERROR - ❌ No camera found!
2025-11-25 09:46:09,506 - ERROR - ❌ No camera found!
2025-11-25 09:46:09,714 - INFO - Video thread started with source: Camera
2025-11-25 09:46:09,714 - INFO - Video thread started with source: Camera
2025-11-25 09:46:09,715 - ERROR - ❌ No camera found!
2025-11-25 09:46:09,717 - ERROR - ❌ No camera found!
2025-11-25 09:46:09,752 - INFO - Frame 466 | PERCLOS: 0.00 | Yaw: 1.8° | Alerts: 1
2025-11-25 09:46:09,910 - INFO - Video thread started with source: Camera
2025-11-25 09:46:09,910 - INFO - Video thread started with source: Camera
2025-11-25 09:46:09,911 - ERROR - ❌ No camera found!
2025-11-25 09:46:09,916 - ERROR - ❌ No camera found!
2025-11-25 09:46:10,124 - INFO - Video thread started with source: Camera
2025-11-25 09:46:10,124 - INFO - Video thread started with source: Camera
2025-11-25 09:46:10,125 - ERROR - ❌ No camera found!
2025-11-25 09:46:10,126 - ERROR - ❌ No camera found!
2025-11-25 09:46:10,326 - INFO - Frame 468 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-25 09:46:10,334 - INFO - Video thread started with source: Camera
2025-11-25 09:46:10,334 - INFO - Video thread started with source: Camera
2025-11-25 09:46:10,335 - ERROR - ❌ No camera found!
2025-11-25 09:46:10,336 - ERROR - ❌ No camera found!
2025-11-25 09:46:10,542 - INFO - Video thread started with source: Camera
2025-11-25 09:46:10,542 - INFO - Video thread started with source: Camera
2025-11-25 09:46:10,544 - ERROR - ❌ No camera found!
2025-11-25 09:46:10,545 - ERROR - ❌ No camera found!
2025-11-25 09:46:10,768 - INFO - Frame 470 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 1
2025-11-25 09:46:10,768 - INFO - Video thread started with source: Camera
2025-11-25 09:46:10,768 - INFO - Video thread started with source: Camera
2025-11-25 09:46:10,769 - ERROR - ❌ No camera found!
2025-11-25 09:46:10,769 - ERROR - ❌ No camera found!
2025-11-25 09:46:10,968 - INFO - Video thread started with source: Camera
2025-11-25 09:46:10,969 - INFO - Video thread started with source: Camera
2025-11-25 09:46:10,980 - ERROR - ❌ No camera found!
2025-11-25 09:46:10,980 - ERROR - ❌ No camera found!
2025-11-25 09:46:11,174 - INFO - Frame 472 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 1
2025-11-25 09:46:11,180 - INFO - Video thread started with source: Camera
2025-11-25 09:46:11,182 - ERROR - ❌ No camera found!
2025-11-25 09:46:11,183 - INFO - Video thread started with source: Camera
2025-11-25 09:46:11,189 - ERROR - ❌ No camera found!
2025-11-25 09:46:11,385 - INFO - Video thread started with source: Camera
2025-11-25 09:46:11,387 - INFO - Video thread started with source: Camera
2025-11-25 09:46:11,387 - ERROR - ❌ No camera found!
2025-11-25 09:46:11,388 - ERROR - ❌ No camera found!
2025-11-25 09:46:11,584 - INFO - Video thread started with source: Camera
2025-11-25 09:46:11,585 - INFO - Video thread started with source: Camera
2025-11-25 09:46:11,586 - ERROR - ❌ No camera found!
2025-11-25 09:46:11,586 - ERROR - ❌ No camera found!
2025-11-25 09:46:11,794 - INFO - Frame 474 | PERCLOS: 0.00 | Yaw: 1.5° | Alerts: 1
2025-11-25 09:46:11,795 - INFO - Video thread started with source: Camera
2025-11-25 09:46:11,797 - INFO - Video thread started with source: Camera
2025-11-25 09:46:11,800 - ERROR - ❌ No camera found!
2025-11-25 09:46:11,800 - ERROR - ❌ No camera found!
2025-11-25 09:46:11,994 - INFO - Video thread started with source: Camera
2025-11-25 09:46:11,998 - ERROR - ❌ No camera found!
2025-11-25 09:46:12,001 - INFO - Video thread started with source: Camera
2025-11-25 09:46:12,003 - ERROR - ❌ No camera found!
2025-11-25 09:46:12,214 - INFO - Video thread started with source: Camera
2025-11-25 09:46:12,214 - INFO - Frame 476 | PERCLOS: 0.23 | Yaw: 1.7° | Alerts: 1
2025-11-25 09:46:12,214 - INFO - Video thread started with source: Camera
2025-11-25 09:46:12,215 - ERROR - ❌ No camera found!
2025-11-25 09:46:12,216 - ERROR - ❌ No camera found!
2025-11-25 09:46:12,433 - INFO - Video thread started with source: Camera
2025-11-25 09:46:12,434 - ERROR - ❌ No camera found!
2025-11-25 09:46:12,435 - INFO - Video thread started with source: Camera
2025-11-25 09:46:12,443 - ERROR - ❌ No camera found!
2025-11-25 09:46:12,645 - INFO - Video thread started with source: Camera
2025-11-25 09:46:12,649 - ERROR - ❌ No camera found!
2025-11-25 09:46:12,650 - INFO - Video thread started with source: Camera
2025-11-25 09:46:12,657 - ERROR - ❌ No camera found!
2025-11-25 09:46:12,658 - INFO - Frame 478 | PERCLOS: 0.00 | Yaw: 4.7° | Alerts: 1
2025-11-25 09:46:12,863 - INFO - Video thread started with source: Camera
2025-11-25 09:46:12,864 - INFO - Video thread started with source: Camera
2025-11-25 09:46:12,864 - ERROR - ❌ No camera found!
2025-11-25 09:46:12,867 - ERROR - ❌ No camera found!
2025-11-25 09:46:12,898 - INFO - Frame 480 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 09:46:13,066 - INFO - Video thread started with source: Camera
2025-11-25 09:46:13,067 - INFO - Video thread started with source: Camera
2025-11-25 09:46:13,067 - ERROR - ❌ No camera found!
2025-11-25 09:46:13,069 - ERROR - ❌ No camera found!
2025-11-25 09:46:13,263 - INFO - Video thread started with source: Camera
2025-11-25 09:46:13,263 - INFO - Video thread started with source: Camera
2025-11-25 09:46:13,264 - ERROR - ❌ No camera found!
2025-11-25 09:46:13,267 - ERROR - ❌ No camera found!
2025-11-25 09:46:13,298 - INFO - Frame 482 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 0
2025-11-25 09:46:13,472 - INFO - Video thread started with source: Camera
2025-11-25 09:46:13,472 - INFO - Video thread started with source: Camera
2025-11-25 09:46:13,474 - ERROR - ❌ No camera found!
2025-11-25 09:46:13,474 - ERROR - ❌ No camera found!
2025-11-25 09:46:13,687 - INFO - Video thread started with source: Camera
2025-11-25 09:46:13,687 - INFO - Video thread started with source: Camera
2025-11-25 09:46:13,687 - INFO - Frame 484 | PERCLOS: 0.00 | Yaw: 2.3° | Alerts: 0
2025-11-25 09:46:13,689 - ERROR - ❌ No camera found!
2025-11-25 09:46:13,693 - ERROR - ❌ No camera found!
2025-11-25 09:46:13,907 - INFO - Video thread started with source: Camera
2025-11-25 09:46:13,907 - INFO - Video thread started with source: Camera
2025-11-25 09:46:13,909 - ERROR - ❌ No camera found!
2025-11-25 09:46:13,912 - ERROR - ❌ No camera found!
2025-11-25 09:46:14,111 - INFO - Video thread started with source: Camera
2025-11-25 09:46:14,111 - INFO - Video thread started with source: Camera
2025-11-25 09:46:14,111 - ERROR - ❌ No camera found!
2025-11-25 09:46:14,111 - ERROR - ❌ No camera found!
2025-11-25 09:46:14,311 - INFO - Frame 486 | PERCLOS: 0.00 | Yaw: 1.9° | Alerts: 1
2025-11-25 09:46:14,319 - INFO - Video thread started with source: Camera
2025-11-25 09:46:14,321 - ERROR - ❌ No camera found!
2025-11-25 09:46:14,321 - INFO - Video thread started with source: Camera
2025-11-25 09:46:14,325 - ERROR - ❌ No camera found!
2025-11-25 09:46:14,509 - INFO - Video thread started with source: Camera
2025-11-25 09:46:14,510 - INFO - Video thread started with source: Camera
2025-11-25 09:46:14,512 - ERROR - ❌ No camera found!
2025-11-25 09:46:14,514 - ERROR - ❌ No camera found!
2025-11-25 09:46:14,700 - INFO - Video thread started with source: Camera
2025-11-25 09:46:14,702 - INFO - Video thread started with source: Camera
2025-11-25 09:46:14,703 - ERROR - ❌ No camera found!
2025-11-25 09:46:14,705 - ERROR - ❌ No camera found!
2025-11-25 09:46:14,910 - INFO - Video thread started with source: Camera
2025-11-25 09:46:14,911 - INFO - Frame 488 | PERCLOS: 0.00 | Yaw: 1.6° | Alerts: 1
2025-11-25 09:46:14,911 - INFO - Video thread started with source: Camera
2025-11-25 09:46:14,912 - ERROR - ❌ No camera found!
2025-11-25 09:46:14,913 - ERROR - ❌ No camera found!
2025-11-25 09:46:15,124 - INFO - Video thread started with source: Camera
2025-11-25 09:46:15,124 - INFO - Video thread started with source: Camera
2025-11-25 09:46:15,124 - ERROR - ❌ No camera found!
2025-11-25 09:46:15,125 - ERROR - ❌ No camera found!
2025-11-25 09:46:15,341 - INFO - Video thread started with source: Camera
2025-11-25 09:46:15,345 - INFO - Video thread started with source: Camera
2025-11-25 09:46:15,347 - ERROR - ❌ No camera found!
2025-11-25 09:46:15,348 - ERROR - ❌ No camera found!
2025-11-25 09:46:15,368 - INFO - Frame 490 | PERCLOS: 0.00 | Yaw: 2.2° | Alerts: 1
2025-11-25 09:46:15,573 - INFO - Video thread started with source: Camera
2025-11-25 09:46:15,576 - ERROR - ❌ No camera found!
2025-11-25 09:46:15,576 - INFO - Video thread started with source: Camera
2025-11-25 09:46:15,580 - ERROR - ❌ No camera found!
2025-11-25 09:46:15,801 - INFO - Video thread started with source: Camera
2025-11-25 09:46:15,803 - INFO - Video thread started with source: Camera
2025-11-25 09:46:15,805 - ERROR - ❌ No camera found!
2025-11-25 09:46:15,809 - ERROR - ❌ No camera found!
2025-11-25 09:46:16,003 - INFO - Frame 492 | PERCLOS: 0.00 | Yaw: 3.9° | Alerts: 1
2025-11-25 09:46:16,008 - INFO - Video thread started with source: Camera
2025-11-25 09:46:16,009 - ERROR - ❌ No camera found!
2025-11-25 09:46:16,010 - INFO - Video thread started with source: Camera
2025-11-25 09:46:16,012 - ERROR - ❌ No camera found!
2025-11-25 09:46:16,222 - INFO - Video thread started with source: Camera
2025-11-25 09:46:16,224 - INFO - Video thread started with source: Camera
2025-11-25 09:46:16,224 - ERROR - ❌ No camera found!
2025-11-25 09:46:16,227 - ERROR - ❌ No camera found!
2025-11-25 09:46:16,439 - INFO - Video thread started with source: Camera
2025-11-25 09:46:16,439 - INFO - Video thread started with source: Camera
2025-11-25 09:46:16,439 - ERROR - ❌ No camera found!
2025-11-25 09:46:16,439 - ERROR - ❌ No camera found!
2025-11-25 09:46:16,443 - INFO - Frame 494 | PERCLOS: 0.00 | Yaw: 6.7° | Alerts: 1
2025-11-25 09:46:16,653 - INFO - Video thread started with source: Camera
2025-11-25 09:46:16,655 - INFO - Video thread started with source: Camera
2025-11-25 09:46:16,655 - ERROR - ❌ No camera found!
2025-11-25 09:46:16,656 - ERROR - ❌ No camera found!
2025-11-25 09:46:16,851 - INFO - Video thread started with source: Camera
2025-11-25 09:46:16,853 - INFO - Video thread started with source: Camera
2025-11-25 09:46:16,860 - ERROR - ❌ No camera found!
2025-11-25 09:46:16,861 - ERROR - ❌ No camera found!
2025-11-25 09:46:16,883 - INFO - Frame 496 | PERCLOS: 0.00 | Yaw: 7.3° | Alerts: 1
2025-11-25 09:46:17,086 - INFO - Video thread started with source: Camera
2025-11-25 09:46:17,089 - INFO - Video thread started with source: Camera
2025-11-25 09:46:17,090 - ERROR - ❌ No camera found!
2025-11-25 09:46:17,092 - ERROR - ❌ No camera found!
2025-11-25 09:46:17,326 - INFO - Video thread started with source: Camera
2025-11-25 09:46:17,328 - ERROR - ❌ No camera found!
2025-11-25 09:46:17,404 - INFO - Video thread started with source: Camera
2025-11-25 09:46:17,406 - ERROR - ❌ No camera found!
2025-11-25 09:46:17,578 - INFO - Frame 498 | PERCLOS: 0.00 | Yaw: 7.9° | Alerts: 1
2025-11-25 09:46:17,581 - INFO - Video thread started with source: Camera
2025-11-25 09:46:17,583 - INFO - Video thread started with source: Camera
2025-11-25 09:46:17,584 - ERROR - ❌ No camera found!
2025-11-25 09:46:17,585 - ERROR - ❌ No camera found!
2025-11-25 09:46:17,609 - INFO - Video thread started with source: Camera
2025-11-25 09:46:17,611 - ERROR - ❌ No camera found!
2025-11-25 09:46:17,808 - INFO - Video thread started with source: Camera
2025-11-25 09:46:17,811 - INFO - Video thread started with source: Camera
2025-11-25 09:46:17,811 - ERROR - ❌ No camera found!
2025-11-25 09:46:17,812 - ERROR - ❌ No camera found!
2025-11-25 09:46:17,813 - INFO - Video thread started with source: Camera
2025-11-25 09:46:17,814 - ERROR - ❌ No camera found!
2025-11-25 09:46:18,011 - INFO - Frame 500 | PERCLOS: 0.00 | Yaw: 5.8° | Alerts: 1
2025-11-25 09:46:18,011 - INFO - Video thread started with source: Camera
2025-11-25 09:46:18,012 - INFO - Video thread started with source: Camera
2025-11-25 09:46:18,013 - ERROR - ❌ No camera found!
2025-11-25 09:46:18,013 - INFO - Video thread started with source: Camera
2025-11-25 09:46:18,013 - ERROR - ❌ No camera found!
2025-11-25 09:46:18,015 - ERROR - ❌ No camera found!
2025-11-25 09:46:18,206 - INFO - Video thread started with source: Camera
2025-11-25 09:46:18,206 - INFO - Video thread started with source: Camera
2025-11-25 09:46:18,207 - INFO - Video thread started with source: Camera
2025-11-25 09:46:18,208 - ERROR - ❌ No camera found!
2025-11-25 09:46:18,208 - ERROR - ❌ No camera found!
2025-11-25 09:46:18,209 - ERROR - ❌ No camera found!
2025-11-25 09:46:18,240 - INFO - Frame 502 | PERCLOS: 0.00 | Yaw: 2.0° | Alerts: 1
2025-11-25 09:46:18,399 - INFO - Video thread started with source: Camera
2025-11-25 09:46:18,403 - INFO - Video thread started with source: Camera
2025-11-25 09:46:18,403 - INFO - Video thread started with source: Camera
2025-11-25 09:46:18,404 - ERROR - ❌ No camera found!
2025-11-25 09:46:18,405 - ERROR - ❌ No camera found!
2025-11-25 09:46:18,407 - ERROR - ❌ No camera found!
2025-11-25 09:46:18,623 - INFO - Video thread started with source: Camera
2025-11-25 09:46:18,623 - INFO - Video thread started with source: Camera
2025-11-25 09:46:18,624 - INFO - Video thread started with source: Camera
2025-11-25 09:46:18,625 - ERROR - ❌ No camera found!
2025-11-25 09:46:18,626 - ERROR - ❌ No camera found!
2025-11-25 09:46:18,628 - ERROR - ❌ No camera found!
2025-11-25 09:46:18,862 - INFO - Frame 504 | PERCLOS: 0.00 | Yaw: 1.4° | Alerts: 1
2025-11-25 09:46:18,868 - INFO - Video thread started with source: Camera
2025-11-25 09:46:18,871 - INFO - Video thread started with source: Camera
2025-11-25 09:46:18,871 - ERROR - ❌ No camera found!
2025-11-25 09:46:18,872 - ERROR - ❌ No camera found!
2025-11-25 09:46:18,872 - INFO - Video thread started with source: Camera
2025-11-25 09:46:18,873 - ERROR - ❌ No camera found!
2025-11-25 09:46:19,075 - INFO - Video thread started with source: Camera
2025-11-25 09:46:19,075 - INFO - Video thread started with source: Camera
2025-11-25 09:46:19,076 - INFO - Video thread started with source: Camera
2025-11-25 09:46:19,077 - ERROR - ❌ No camera found!
2025-11-25 09:46:19,078 - ERROR - ❌ No camera found!
2025-11-25 09:46:19,080 - ERROR - ❌ No camera found!
2025-11-25 09:46:19,293 - INFO - Video thread started with source: Camera
2025-11-25 09:46:19,296 - INFO - Video thread started with source: Camera
2025-11-25 09:46:19,296 - INFO - Video thread started with source: Camera
2025-11-25 09:46:19,298 - INFO - Frame 506 | PERCLOS: 0.00 | Yaw: 1.3° | Alerts: 1
2025-11-25 09:46:19,298 - ERROR - ❌ No camera found!
2025-11-25 09:46:19,302 - ERROR - ❌ No camera found!
2025-11-25 09:46:19,302 - ERROR - ❌ No camera found!
2025-11-25 09:46:19,500 - INFO - Video thread started with source: Camera
2025-11-25 09:46:19,502 - INFO - Video thread started with source: Camera
2025-11-25 09:46:19,503 - INFO - Video thread started with source: Camera
2025-11-25 09:46:19,503 - ERROR - ❌ No camera found!
2025-11-25 09:46:19,504 - ERROR - ❌ No camera found!
2025-11-25 09:46:19,509 - ERROR - ❌ No camera found!
2025-11-25 09:46:19,702 - INFO - Video thread started with source: Camera
2025-11-25 09:46:19,703 - INFO - Video thread started with source: Camera
2025-11-25 09:46:19,704 - ERROR - ❌ No camera found!
2025-11-25 09:46:19,706 - ERROR - ❌ No camera found!
2025-11-25 09:46:19,708 - INFO - Video thread started with source: Camera
2025-11-25 09:46:19,711 - ERROR - ❌ No camera found!
2025-11-25 09:46:19,729 - INFO - Frame 508 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 1
2025-11-25 09:46:19,933 - INFO - Video thread started with source: Camera
2025-11-25 09:46:19,935 - INFO - Video thread started with source: Camera
2025-11-25 09:46:19,935 - ERROR - ❌ No camera found!
2025-11-25 09:46:19,935 - INFO - Video thread started with source: Camera
2025-11-25 09:46:19,936 - ERROR - ❌ No camera found!
2025-11-25 09:46:19,937 - ERROR - ❌ No camera found!
2025-11-25 09:46:20,154 - INFO - Video thread started with source: Camera
2025-11-25 09:46:20,154 - INFO - Video thread started with source: Camera
2025-11-25 09:46:20,156 - INFO - Video thread started with source: Camera
2025-11-25 09:46:20,156 - ERROR - ❌ No camera found!
2025-11-25 09:46:20,158 - ERROR - ❌ No camera found!
2025-11-25 09:46:20,158 - ERROR - ❌ No camera found!
2025-11-25 09:46:20,361 - INFO - Frame 510 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 1
2025-11-25 09:46:20,365 - INFO - Video thread started with source: Camera
2025-11-25 09:46:20,366 - INFO - Video thread started with source: Camera
2025-11-25 09:46:20,369 - ERROR - ❌ No camera found!
2025-11-25 09:46:20,369 - ERROR - ❌ No camera found!
2025-11-25 09:46:20,369 - INFO - Video thread started with source: Camera
2025-11-25 09:46:20,371 - ERROR - ❌ No camera found!
2025-11-25 09:46:20,570 - INFO - Video thread started with source: Camera
2025-11-25 09:46:20,572 - INFO - Video thread started with source: Camera
2025-11-25 09:46:20,573 - ERROR - ❌ No camera found!
2025-11-25 09:46:20,575 - ERROR - ❌ No camera found!
2025-11-25 09:46:20,577 - INFO - Video thread started with source: Camera
2025-11-25 09:46:20,581 - ERROR - ❌ No camera found!
2025-11-25 09:46:20,771 - INFO - Video thread started with source: Camera
2025-11-25 09:46:20,771 - INFO - Frame 512 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 1
2025-11-25 09:46:20,772 - INFO - Video thread started with source: Camera
2025-11-25 09:46:20,773 - INFO - Video thread started with source: Camera
2025-11-25 09:46:20,773 - ERROR - ❌ No camera found!
2025-11-25 09:46:20,774 - ERROR - ❌ No camera found!
2025-11-25 09:46:20,774 - ERROR - ❌ No camera found!
2025-11-25 09:46:20,981 - INFO - Video thread started with source: Camera
2025-11-25 09:46:20,983 - ERROR - ❌ No camera found!
2025-11-25 09:46:20,983 - INFO - Video thread started with source: Camera
2025-11-25 09:46:20,985 - INFO - Video thread started with source: Camera
2025-11-25 09:46:20,986 - ERROR - ❌ No camera found!
2025-11-25 09:46:20,987 - ERROR - ❌ No camera found!
2025-11-25 09:46:21,193 - INFO - Frame 514 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 1
2025-11-25 09:46:21,193 - INFO - Video thread started with source: Camera
2025-11-25 09:46:21,194 - ERROR - ❌ No camera found!
2025-11-25 09:46:21,194 - INFO - Video thread started with source: Camera
2025-11-25 09:46:21,195 - INFO - Video thread started with source: Camera
2025-11-25 09:46:21,196 - ERROR - ❌ No camera found!
2025-11-25 09:46:21,197 - ERROR - ❌ No camera found!
2025-11-25 09:46:21,393 - INFO - Video thread started with source: Camera
2025-11-25 09:46:21,394 - INFO - Video thread started with source: Camera
2025-11-25 09:46:21,394 - ERROR - ❌ No camera found!
2025-11-25 09:46:21,396 - INFO - Video thread started with source: Camera
2025-11-25 09:46:21,397 - ERROR - ❌ No camera found!
2025-11-25 09:46:21,401 - ERROR - ❌ No camera found!
2025-11-25 09:46:21,605 - INFO - Video thread started with source: Camera
2025-11-25 09:46:21,605 - INFO - Video thread started with source: Camera
2025-11-25 09:46:21,607 - ERROR - ❌ No camera found!
2025-11-25 09:46:21,608 - INFO - Video thread started with source: Camera
2025-11-25 09:46:21,610 - ERROR - ❌ No camera found!
2025-11-25 09:46:21,610 - ERROR - ❌ No camera found!
2025-11-25 09:46:21,624 - INFO - Frame 516 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 1
2025-11-25 09:46:21,811 - INFO - Video thread started with source: Camera
2025-11-25 09:46:21,812 - INFO - Video thread started with source: Camera
2025-11-25 09:46:21,814 - ERROR - ❌ No camera found!
2025-11-25 09:46:21,815 - ERROR - ❌ No camera found!
2025-11-25 09:46:21,815 - INFO - Video thread started with source: Camera
2025-11-25 09:46:21,817 - ERROR - ❌ No camera found!
2025-11-25 09:46:22,043 - INFO - Video thread started with source: Camera
2025-11-25 09:46:22,044 - INFO - Video thread started with source: Camera
2025-11-25 09:46:22,044 - ERROR - ❌ No camera found!
2025-11-25 09:46:22,045 - INFO - Video thread started with source: Camera
2025-11-25 09:46:22,045 - INFO - Frame 518 | PERCLOS: 0.00 | Yaw: 1.0° | Alerts: 1
2025-11-25 09:46:22,045 - ERROR - ❌ No camera found!
2025-11-25 09:46:22,045 - ERROR - ❌ No camera found!
2025-11-25 09:46:22,282 - INFO - Video thread started with source: Camera
2025-11-25 09:46:22,282 - INFO - Video thread started with source: Camera
2025-11-25 09:46:22,284 - ERROR - ❌ No camera found!
2025-11-25 09:46:22,286 - ERROR - ❌ No camera found!
2025-11-25 09:46:22,286 - INFO - Video thread started with source: Camera
2025-11-25 09:46:22,289 - ERROR - ❌ No camera found!
2025-11-25 09:46:22,482 - INFO - Video thread started with source: Camera
2025-11-25 09:46:22,484 - INFO - Video thread started with source: Camera
2025-11-25 09:46:22,487 - INFO - Video thread started with source: Camera
2025-11-25 09:46:22,487 - ERROR - ❌ No camera found!
2025-11-25 09:46:22,488 - ERROR - ❌ No camera found!
2025-11-25 09:46:22,489 - ERROR - ❌ No camera found!
2025-11-25 09:46:22,682 - INFO - Video thread started with source: Camera
2025-11-25 09:46:22,683 - INFO - Video thread started with source: Camera
2025-11-25 09:46:22,683 - INFO - Video thread started with source: Camera
2025-11-25 09:46:22,684 - ERROR - ❌ No camera found!
2025-11-25 09:46:22,684 - ERROR - ❌ No camera found!
2025-11-25 09:46:22,685 - ERROR - ❌ No camera found!
2025-11-25 09:46:22,686 - INFO - Frame 520 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 1
2025-11-25 09:46:22,878 - INFO - Video thread started with source: Camera
2025-11-25 09:46:22,878 - INFO - Video thread started with source: Camera
2025-11-25 09:46:22,878 - INFO - Video thread started with source: Camera
2025-11-25 09:46:22,878 - ERROR - ❌ No camera found!
2025-11-25 09:46:22,879 - ERROR - ❌ No camera found!
2025-11-25 09:46:22,879 - ERROR - ❌ No camera found!
2025-11-25 09:46:23,121 - INFO - Video thread started with source: Camera
2025-11-25 09:46:23,122 - INFO - Video thread started with source: Camera
2025-11-25 09:46:23,123 - ERROR - ❌ No camera found!
2025-11-25 09:46:23,124 - INFO - Video thread started with source: Camera
2025-11-25 09:46:23,125 - ERROR - ❌ No camera found!
2025-11-25 09:46:23,126 - ERROR - ❌ No camera found!
2025-11-25 09:46:23,337 - INFO - Frame 522 | PERCLOS: 0.00 | Yaw: 1.1° | Alerts: 1
2025-11-25 09:46:23,340 - INFO - Video thread started with source: Camera
2025-11-25 09:46:23,341 - INFO - Video thread started with source: Camera
2025-11-25 09:46:23,345 - ERROR - ❌ No camera found!
2025-11-25 09:46:23,345 - ERROR - ❌ No camera found!
2025-11-25 09:46:23,345 - INFO - Video thread started with source: Camera
2025-11-25 09:46:23,349 - ERROR - ❌ No camera found!
2025-11-25 09:46:23,535 - INFO - Video thread started with source: Camera
2025-11-25 09:46:23,535 - INFO - Video thread started with source: Camera
2025-11-25 09:46:23,535 - INFO - Video thread started with source: Camera
2025-11-25 09:46:23,535 - ERROR - ❌ No camera found!
2025-11-25 09:46:23,537 - ERROR - ❌ No camera found!
2025-11-25 09:46:23,538 - ERROR - ❌ No camera found!
2025-11-25 09:46:23,638 - INFO - Frame 524 | PERCLOS: 0.00 | Yaw: 1.7° | Alerts: 1
2025-11-25 09:46:23,757 - INFO - Video thread started with source: Camera
2025-11-25 09:46:23,758 - INFO - Video thread started with source: Camera
2025-11-25 09:46:23,759 - ERROR - ❌ No camera found!
2025-11-25 09:46:23,760 - INFO - Video thread started with source: Camera
2025-11-25 09:46:23,761 - ERROR - ❌ No camera found!
2025-11-25 09:46:23,763 - ERROR - ❌ No camera found!
2025-11-25 09:46:23,960 - INFO - Video thread started with source: Camera
2025-11-25 09:46:23,961 - INFO - Video thread started with source: Camera
2025-11-25 09:46:23,961 - INFO - Video thread started with source: Camera
2025-11-25 09:46:23,961 - ERROR - ❌ No camera found!
2025-11-25 09:46:23,962 - ERROR - ❌ No camera found!
2025-11-25 09:46:23,964 - ERROR - ❌ No camera found!
2025-11-25 09:46:23,994 - INFO - Frame 526 | PERCLOS: 0.00 | Yaw: 3.3° | Alerts: 1
2025-11-25 09:46:24,175 - INFO - Video thread started with source: Camera
2025-11-25 09:46:24,175 - INFO - Video thread started with source: Camera
2025-11-25 09:46:24,175 - INFO - Video thread started with source: Camera
2025-11-25 09:46:24,176 - ERROR - ❌ No camera found!
2025-11-25 09:46:24,178 - ERROR - ❌ No camera found!
2025-11-25 09:46:24,179 - ERROR - ❌ No camera found!
2025-11-25 09:46:24,390 - INFO - Video thread started with source: Camera
2025-11-25 09:46:24,392 - INFO - Video thread started with source: Camera
2025-11-25 09:46:24,393 - ERROR - ❌ No camera found!
2025-11-25 09:46:24,394 - ERROR - ❌ No camera found!
2025-11-25 09:46:24,397 - INFO - Video thread started with source: Camera
2025-11-25 09:46:24,401 - ERROR - ❌ No camera found!
2025-11-25 11:31:31,123 - INFO - Loading models...
2025-11-25 11:31:31,155 - INFO - ✓ YOLO ONNX loaded
2025-11-25 11:31:31,192 - INFO - ✓ MediaPipe Face Mesh loaded
2025-11-25 11:31:31,199 - INFO - ✓ MediaPipe Pose loaded (for smoke & seatbelt)
2025-11-25 11:31:31,211 - INFO - Video thread started with source: Camera
2025-11-25 11:31:31,212 - ERROR - ❌ No camera found!
2025-11-25 11:31:31,213 - INFO - Video thread started with source: Camera
2025-11-25 11:31:31,216 - ERROR - ❌ No camera found!
2025-11-25 11:31:31,220 - INFO - Video thread started with source: Camera
2025-11-25 11:31:31,220 - INFO - Video thread started with source: Camera
2025-11-25 11:31:31,224 - ERROR - ❌ No camera found!
2025-11-25 11:31:31,224 - ERROR - ❌ No camera found!
2025-11-25 11:31:31,506 - INFO - Video thread started with source: Camera
2025-11-25 11:31:31,506 - INFO - Video thread started with source: Camera
2025-11-25 11:31:31,508 - INFO - Video thread started with source: Camera
2025-11-25 11:31:31,508 - ERROR - ❌ No camera found!
2025-11-25 11:31:31,508 - ERROR - ❌ No camera found!
2025-11-25 11:31:31,509 - INFO - Video thread started with source: Camera
2025-11-25 11:31:31,509 - ERROR - ❌ No camera found!
2025-11-25 11:31:31,511 - ERROR - ❌ No camera found!
2025-11-25 11:31:31,764 - INFO - Video thread started with source: Camera
2025-11-25 11:31:31,765 - INFO - Video thread started with source: Camera
2025-11-25 11:31:31,766 - INFO - Video thread started with source: Camera
2025-11-25 11:31:31,768 - ERROR - ❌ No camera found!
2025-11-25 11:31:31,768 - ERROR - ❌ No camera found!
2025-11-25 11:31:31,768 - INFO - Video thread started with source: Camera
2025-11-25 11:31:31,768 - ERROR - ❌ No camera found!
2025-11-25 11:31:31,769 - ERROR - ❌ No camera found!
2025-11-25 11:31:32,009 - INFO - Video thread started with source: Camera
2025-11-25 11:31:32,012 - INFO - Video thread started with source: Camera
2025-11-25 11:31:32,012 - INFO - Video thread started with source: Camera
2025-11-25 11:31:32,013 - ERROR - ❌ No camera found!
2025-11-25 11:31:32,015 - ERROR - ❌ No camera found!
2025-11-25 11:31:32,015 - ERROR - ❌ No camera found!
2025-11-25 11:31:32,015 - INFO - Video thread started with source: Camera
2025-11-25 11:31:32,018 - ERROR - ❌ No camera found!
2025-11-25 11:31:32,236 - INFO - Video thread started with source: Camera
2025-11-25 11:31:32,236 - INFO - Video thread started with source: Camera
2025-11-25 11:31:32,236 - INFO - Video thread started with source: Camera
2025-11-25 11:31:32,236 - ERROR - ❌ No camera found!
2025-11-25 11:31:32,238 - ERROR - ❌ No camera found!
2025-11-25 11:31:32,239 - INFO - Video thread started with source: Camera
2025-11-25 11:31:32,239 - ERROR - ❌ No camera found!
2025-11-25 11:31:32,239 - ERROR - ❌ No camera found!
2025-11-25 11:31:32,469 - INFO - Video thread started with source: Camera
2025-11-25 11:31:32,470 - INFO - Video thread started with source: Camera
2025-11-25 11:31:32,470 - INFO - Video thread started with source: Camera
2025-11-25 11:31:32,471 - ERROR - ❌ No camera found!
2025-11-25 11:31:32,471 - ERROR - ❌ No camera found!
2025-11-25 11:31:32,472 - ERROR - ❌ No camera found!
2025-11-25 11:31:32,472 - INFO - Video thread started with source: Camera
2025-11-25 11:31:32,473 - ERROR - ❌ No camera found!
2025-11-25 11:31:32,657 - INFO - Video thread started with source: Camera
2025-11-25 11:31:32,710 - ERROR - ❌ No camera found!
2025-11-25 11:31:32,711 - INFO - Video thread started with source: Camera
2025-11-25 11:31:32,712 - INFO - Video thread started with source: Camera
2025-11-25 11:31:32,715 - INFO - Video thread started with source: Camera
2025-11-25 11:31:32,715 - ERROR - ❌ No camera found!
2025-11-25 11:31:32,716 - ERROR - ❌ No camera found!
2025-11-25 11:31:32,717 - ERROR - ❌ No camera found!
2025-11-25 11:31:32,959 - INFO - Video thread started with source: Camera
2025-11-25 11:31:32,960 - INFO - Video thread started with source: Camera
2025-11-25 11:31:32,960 - INFO - Video thread started with source: Camera
2025-11-25 11:31:32,961 - ERROR - ❌ No camera found!
2025-11-25 11:31:32,962 - ERROR - ❌ No camera found!
2025-11-25 11:31:32,962 - ERROR - ❌ No camera found!
2025-11-25 11:31:32,963 - INFO - Video thread started with source: Camera
2025-11-25 11:31:32,963 - ERROR - ❌ No camera found!
2025-11-25 11:31:33,188 - INFO - Video thread started with source: Camera
2025-11-25 11:31:33,192 - INFO - Video thread started with source: Camera
2025-11-25 11:31:33,193 - INFO - Video thread started with source: Camera
2025-11-25 11:31:33,193 - INFO - Video thread started with source: Camera
2025-11-25 11:31:33,193 - ERROR - ❌ No camera found!
2025-11-25 11:31:33,194 - ERROR - ❌ No camera found!
2025-11-25 11:31:33,194 - ERROR - ❌ No camera found!
2025-11-25 11:31:33,195 - ERROR - ❌ No camera found!
2025-11-25 11:31:33,422 - INFO - Video thread started with source: Camera
2025-11-25 11:31:33,422 - INFO - Video thread started with source: Camera
2025-11-25 11:31:33,422 - ERROR - ❌ No camera found!
2025-11-25 11:31:33,423 - ERROR - ❌ No camera found!
2025-11-25 11:31:33,427 - INFO - Video thread started with source: Camera
2025-11-25 11:31:33,428 - INFO - Video thread started with source: Camera
2025-11-25 11:31:33,429 - ERROR - ❌ No camera found!
2025-11-25 11:31:33,432 - ERROR - ❌ No camera found!
2025-11-25 11:31:33,658 - INFO - Video thread started with source: Camera
2025-11-25 11:31:33,658 - INFO - Video thread started with source: Camera
2025-11-25 11:31:33,658 - ERROR - ❌ No camera found!
2025-11-25 11:31:33,658 - INFO - Video thread started with source: Camera
2025-11-25 11:31:33,660 - INFO - Video thread started with source: Camera
2025-11-25 11:31:33,660 - ERROR - ❌ No camera found!
2025-11-25 11:31:33,660 - ERROR - ❌ No camera found!
2025-11-25 11:31:33,662 - ERROR - ❌ No camera found!
2025-11-25 11:31:33,904 - INFO - Video thread started with source: Camera
2025-11-25 11:31:33,904 - INFO - Video thread started with source: Camera
2025-11-25 11:31:33,906 - ERROR - ❌ No camera found!
2025-11-25 11:31:33,907 - ERROR - ❌ No camera found!
2025-11-25 11:31:33,907 - INFO - Video thread started with source: Camera
2025-11-25 11:31:33,908 - ERROR - ❌ No camera found!
2025-11-25 11:31:33,909 - INFO - Video thread started with source: Camera
2025-11-25 11:31:33,909 - ERROR - ❌ No camera found!
2025-11-25 11:31:34,173 - INFO - Video thread started with source: Camera
2025-11-25 11:31:34,174 - INFO - Video thread started with source: Camera
2025-11-25 11:31:34,174 - INFO - Video thread started with source: Camera
2025-11-25 11:31:34,176 - ERROR - ❌ No camera found!
2025-11-25 11:31:34,176 - INFO - Video thread started with source: Camera
2025-11-25 11:31:34,177 - ERROR - ❌ No camera found!
2025-11-25 11:31:34,177 - ERROR - ❌ No camera found!
2025-11-25 11:31:34,180 - ERROR - ❌ No camera found!
2025-11-25 11:31:34,420 - INFO - Video thread started with source: Camera
2025-11-25 11:31:34,422 - INFO - Video thread started with source: Camera
2025-11-25 11:31:34,422 - INFO - Video thread started with source: Camera
2025-11-25 11:31:34,424 - ERROR - ❌ No camera found!
2025-11-25 11:31:34,424 - INFO - Video thread started with source: Camera
2025-11-25 11:31:34,424 - ERROR - ❌ No camera found!
2025-11-25 11:31:34,425 - ERROR - ❌ No camera found!
2025-11-25 11:31:34,426 - ERROR - ❌ No camera found!
2025-11-25 11:31:34,693 - INFO - Video thread started with source: Camera
2025-11-25 11:31:34,696 - INFO - Video thread started with source: Camera
2025-11-25 11:31:34,696 - INFO - Video thread started with source: Camera
2025-11-25 11:31:34,697 - ERROR - ❌ No camera found!
2025-11-25 11:31:34,697 - ERROR - ❌ No camera found!
2025-11-25 11:31:34,697 - ERROR - ❌ No camera found!
2025-11-25 11:31:34,698 - INFO - Video thread started with source: Camera
2025-11-25 11:31:34,698 - ERROR - ❌ No camera found!
2025-11-25 11:31:34,930 - INFO - Video thread started with source: Camera
2025-11-25 11:31:34,931 - INFO - Video thread started with source: Camera
2025-11-25 11:31:34,932 - ERROR - ❌ No camera found!
2025-11-25 11:31:34,933 - ERROR - ❌ No camera found!
2025-11-25 11:31:34,933 - INFO - Video thread started with source: Camera
2025-11-25 11:31:34,933 - ERROR - ❌ No camera found!
2025-11-25 11:31:34,933 - ERROR - ❌ No camera found!
2025-11-25 11:31:34,933 - INFO - Video thread started with source: Camera
2025-11-25 11:31:35,194 - INFO - Video thread started with source: Camera
2025-11-25 11:31:35,197 - INFO - Video thread started with source: Camera
2025-11-25 11:31:35,198 - INFO - Video thread started with source: Camera
2025-11-25 11:31:35,198 - ERROR - ❌ No camera found!
2025-11-25 11:31:35,198 - ERROR - ❌ No camera found!
2025-11-25 11:31:35,201 - ERROR - ❌ No camera found!
2025-11-25 11:31:35,201 - INFO - Video thread started with source: Camera
2025-11-25 11:31:35,207 - ERROR - ❌ No camera found!
2025-11-25 11:31:35,463 - INFO - Video thread started with source: Camera
2025-11-25 11:31:35,463 - INFO - Video thread started with source: Camera
2025-11-25 11:31:35,465 - INFO - Video thread started with source: Camera
2025-11-25 11:31:35,466 - ERROR - ❌ No camera found!
2025-11-25 11:31:35,468 - INFO - Video thread started with source: Camera
2025-11-25 11:31:35,468 - ERROR - ❌ No camera found!
2025-11-25 11:31:35,468 - ERROR - ❌ No camera found!
2025-11-25 11:31:35,470 - ERROR - ❌ No camera found!
2025-11-25 11:31:35,710 - INFO - Video thread started with source: Camera
2025-11-25 11:31:35,711 - INFO - Video thread started with source: Camera
2025-11-25 11:31:35,711 - INFO - Video thread started with source: Camera
2025-11-25 11:31:35,712 - ERROR - ❌ No camera found!
2025-11-25 11:31:35,712 - ERROR - ❌ No camera found!
2025-11-25 11:31:35,714 - INFO - Video thread started with source: Camera
2025-11-25 11:31:35,714 - ERROR - ❌ No camera found!
2025-11-25 11:31:35,714 - ERROR - ❌ No camera found!
2025-11-25 11:31:35,972 - INFO - Video thread started with source: Camera
2025-11-25 11:31:35,972 - INFO - Video thread started with source: Camera
2025-11-25 11:31:35,975 - INFO - Video thread started with source: Camera
2025-11-25 11:31:35,975 - INFO - Video thread started with source: Camera
2025-11-25 11:31:35,975 - ERROR - ❌ No camera found!
2025-11-25 11:31:35,975 - ERROR - ❌ No camera found!
2025-11-25 11:31:35,976 - ERROR - ❌ No camera found!
2025-11-25 11:31:35,976 - ERROR - ❌ No camera found!
2025-11-25 11:31:36,218 - INFO - Video thread started with source: Camera
2025-11-25 11:31:36,219 - INFO - Video thread started with source: Camera
2025-11-25 11:31:36,219 - ERROR - ❌ No camera found!
2025-11-25 11:31:36,232 - INFO - Video thread started with source: Camera
2025-11-25 11:31:36,232 - ERROR - ❌ No camera found!
2025-11-25 11:31:36,232 - INFO - Video thread started with source: Camera
2025-11-25 11:31:36,233 - ERROR - ❌ No camera found!
2025-11-25 11:31:36,240 - ERROR - ❌ No camera found!
2025-11-25 11:31:36,251 - INFO - Video thread started with source: Camera
2025-11-25 11:31:36,252 - ERROR - ❌ No camera found!
2025-11-25 11:31:36,556 - INFO - Video thread started with source: Camera
2025-11-25 11:31:36,556 - INFO - Video thread started with source: Camera
2025-11-25 11:31:36,557 - INFO - Video thread started with source: Camera
2025-11-25 11:31:36,557 - ERROR - ❌ No camera found!
2025-11-25 11:31:36,558 - ERROR - ❌ No camera found!
2025-11-25 11:31:36,560 - ERROR - ❌ No camera found!
2025-11-25 11:31:36,561 - INFO - Video thread started with source: Camera
2025-11-25 11:31:36,562 - ERROR - ❌ No camera found!
2025-11-25 11:31:36,806 - INFO - Video thread started with source: Camera
2025-11-25 11:31:36,806 - INFO - Video thread started with source: Camera
2025-11-25 11:31:36,806 - ERROR - ❌ No camera found!
2025-11-25 11:31:36,807 - ERROR - ❌ No camera found!
2025-11-25 11:31:36,809 - INFO - Video thread started with source: Camera
2025-11-25 11:31:36,813 - ERROR - ❌ No camera found!
2025-11-25 11:31:36,818 - INFO - Video thread started with source: Camera
2025-11-25 11:31:36,819 - ERROR - ❌ No camera found!
2025-11-25 11:31:36,959 - INFO - Video thread started with source: Camera
2025-11-25 11:31:36,959 - INFO - Video thread started with source: Camera
2025-11-25 11:31:36,959 - ERROR - ❌ No camera found!
2025-11-25 11:31:36,962 - ERROR - ❌ No camera found!
2025-11-25 11:31:36,963 - INFO - Video thread started with source: Camera
2025-11-25 11:31:36,965 - ERROR - ❌ No camera found!
2025-11-25 11:31:36,967 - INFO - Video thread started with source: Camera
2025-11-25 11:31:36,968 - ERROR - ❌ No camera found!
2025-11-25 11:31:37,207 - INFO - Video thread started with source: Camera
2025-11-25 11:31:37,208 - ERROR - ❌ No camera found!
2025-11-25 11:31:37,208 - INFO - Video thread started with source: Camera
2025-11-25 11:31:37,208 - INFO - Video thread started with source: Camera
2025-11-25 11:31:37,208 - ERROR - ❌ No camera found!
2025-11-25 11:31:37,210 - ERROR - ❌ No camera found!
2025-11-25 11:31:37,212 - INFO - Video thread started with source: Camera
2025-11-25 11:31:37,214 - ERROR - ❌ No camera found!
2025-11-25 11:31:37,461 - INFO - Video thread started with source: Camera
2025-11-25 11:31:37,465 - INFO - Video thread started with source: Camera
2025-11-25 11:31:37,466 - ERROR - ❌ No camera found!
2025-11-25 11:31:37,467 - INFO - Video thread started with source: Camera
2025-11-25 11:31:37,467 - ERROR - ❌ No camera found!
2025-11-25 11:31:37,467 - INFO - Video thread started with source: Camera
2025-11-25 11:31:37,469 - ERROR - ❌ No camera found!
2025-11-25 11:31:37,470 - ERROR - ❌ No camera found!
2025-11-25 11:31:37,703 - ERROR - ❌ No camera found!
2025-11-25 11:31:37,705 - INFO - Video thread started with source: Camera
2025-11-25 11:31:37,707 - INFO - Video thread started with source: Camera
2025-11-25 11:31:37,707 - INFO - Video thread started with source: Camera
2025-11-25 11:31:37,708 - ERROR - ❌ No camera found!
2025-11-25 11:31:37,708 - INFO - Video thread started with source: Camera
2025-11-25 11:31:37,709 - ERROR - ❌ No camera found!
2025-11-25 11:31:37,709 - ERROR - ❌ No camera found!
2025-11-25 11:31:37,988 - INFO - Video thread started with source: Camera
2025-11-25 11:31:37,988 - INFO - Video thread started with source: Camera
2025-11-25 11:31:37,991 - ERROR - ❌ No camera found!
2025-11-25 11:31:37,991 - INFO - Video thread started with source: Camera
2025-11-25 11:31:37,994 - ERROR - ❌ No camera found!
2025-11-25 11:31:37,994 - ERROR - ❌ No camera found!
2025-11-25 11:31:38,000 - INFO - Video thread started with source: Camera
2025-11-25 11:31:38,002 - ERROR - ❌ No camera found!
2025-11-25 11:31:38,277 - INFO - Video thread started with source: Camera
2025-11-25 11:31:38,279 - INFO - Video thread started with source: Camera
2025-11-25 11:31:38,282 - INFO - Video thread started with source: Camera
2025-11-25 11:31:38,283 - ERROR - ❌ No camera found!
2025-11-25 11:31:38,283 - ERROR - ❌ No camera found!
2025-11-25 11:31:38,284 - INFO - Video thread started with source: Camera
2025-11-25 11:31:38,286 - ERROR - ❌ No camera found!
2025-11-25 11:31:38,287 - ERROR - ❌ No camera found!
2025-11-25 11:31:38,540 - INFO - Video thread started with source: Camera
2025-11-25 11:31:38,541 - INFO - Video thread started with source: Camera
2025-11-25 11:31:38,541 - INFO - Video thread started with source: Camera
2025-11-25 11:31:38,541 - ERROR - ❌ No camera found!
2025-11-25 11:31:38,542 - ERROR - ❌ No camera found!
2025-11-25 11:31:38,543 - INFO - Video thread started with source: Camera
2025-11-25 11:31:38,543 - ERROR - ❌ No camera found!
2025-11-25 11:31:38,544 - ERROR - ❌ No camera found!
2025-11-25 11:31:38,773 - INFO - Video thread started with source: Camera
2025-11-25 11:31:38,776 - ERROR - ❌ No camera found!
2025-11-25 11:31:38,776 - INFO - Video thread started with source: Camera
2025-11-25 11:31:38,779 - INFO - Video thread started with source: Camera
2025-11-25 11:31:38,779 - INFO - Video thread started with source: Camera
2025-11-25 11:31:38,781 - ERROR - ❌ No camera found!
2025-11-25 11:31:38,783 - ERROR - ❌ No camera found!
2025-11-25 11:31:38,783 - ERROR - ❌ No camera found!
2025-11-25 11:31:39,030 - INFO - Video thread started with source: Camera
2025-11-25 11:31:39,035 - INFO - Video thread started with source: Camera
2025-11-25 11:31:39,035 - ERROR - ❌ No camera found!
2025-11-25 11:31:39,037 - ERROR - ❌ No camera found!
2025-11-25 11:31:39,039 - INFO - Video thread started with source: Camera
2025-11-25 11:31:39,043 - ERROR - ❌ No camera found!
2025-11-25 11:31:39,043 - INFO - Video thread started with source: Camera
2025-11-25 11:31:39,043 - ERROR - ❌ No camera found!
2025-11-25 11:31:39,300 - INFO - Video thread started with source: Camera
2025-11-25 11:31:39,301 - INFO - Video thread started with source: Camera
2025-11-25 11:31:39,302 - ERROR - ❌ No camera found!
2025-11-25 11:31:39,303 - INFO - Video thread started with source: Camera
2025-11-25 11:31:39,303 - ERROR - ❌ No camera found!
2025-11-25 11:31:39,303 - ERROR - ❌ No camera found!
2025-11-25 11:31:39,310 - INFO - Video thread started with source: Camera
2025-11-25 11:31:39,312 - ERROR - ❌ No camera found!
2025-11-25 11:31:39,554 - INFO - Video thread started with source: Camera
2025-11-25 11:31:39,556 - INFO - Video thread started with source: Camera
2025-11-25 11:31:39,557 - INFO - Video thread started with source: Camera
2025-11-25 11:31:39,558 - ERROR - ❌ No camera found!
2025-11-25 11:31:39,558 - ERROR - ❌ No camera found!
2025-11-25 11:31:39,561 - INFO - Video thread started with source: Camera
2025-11-25 11:31:39,561 - ERROR - ❌ No camera found!
2025-11-25 11:31:39,561 - ERROR - ❌ No camera found!
2025-11-25 11:31:39,847 - INFO - Video thread started with source: Camera
2025-11-25 11:31:39,850 - INFO - Video thread started with source: Camera
2025-11-25 11:31:39,852 - ERROR - ❌ No camera found!
2025-11-25 11:31:39,853 - ERROR - ❌ No camera found!
2025-11-25 11:31:39,853 - INFO - Video thread started with source: Camera
2025-11-25 11:31:39,854 - ERROR - ❌ No camera found!
2025-11-25 11:31:39,854 - ERROR - ❌ No camera found!
2025-11-25 11:31:39,855 - INFO - Video thread started with source: Camera
2025-11-25 11:31:40,137 - INFO - Video thread started with source: Camera
2025-11-25 11:31:40,138 - ERROR - ❌ No camera found!
2025-11-25 11:31:40,141 - INFO - Video thread started with source: Camera
2025-11-25 11:31:40,141 - INFO - Video thread started with source: Camera
2025-11-25 11:31:40,143 - ERROR - ❌ No camera found!
2025-11-25 11:31:40,146 - INFO - Video thread started with source: Camera
2025-11-25 11:31:40,146 - ERROR - ❌ No camera found!
2025-11-25 11:31:40,148 - ERROR - ❌ No camera found!
2025-11-25 11:31:40,350 - INFO - Video thread started with source: Camera
2025-11-25 11:31:40,351 - ERROR - ❌ No camera found!
2025-11-25 11:31:40,414 - INFO - Video thread started with source: Camera
2025-11-25 11:31:40,417 - INFO - Video thread started with source: Camera
2025-11-25 11:31:40,419 - ERROR - ❌ No camera found!
2025-11-25 11:31:40,419 - ERROR - ❌ No camera found!
2025-11-25 11:31:40,419 - INFO - Video thread started with source: Camera
2025-11-25 11:31:40,420 - ERROR - ❌ No camera found!
2025-11-25 11:31:40,693 - INFO - Video thread started with source: Camera
2025-11-25 11:31:40,695 - INFO - Video thread started with source: Camera
2025-11-25 11:31:40,698 - INFO - Video thread started with source: Camera
2025-11-25 11:31:40,698 - ERROR - ❌ No camera found!
2025-11-25 11:31:40,702 - ERROR - ❌ No camera found!
2025-11-25 11:31:40,705 - ERROR - ❌ No camera found!
2025-11-25 11:31:40,705 - INFO - Video thread started with source: Camera
2025-11-25 11:31:40,708 - ERROR - ❌ No camera found!
2025-11-25 11:31:40,962 - INFO - Video thread started with source: Camera
2025-11-25 11:31:40,962 - INFO - Video thread started with source: Camera
2025-11-25 11:31:40,963 - INFO - Video thread started with source: Camera
2025-11-25 11:31:40,965 - ERROR - ❌ No camera found!
2025-11-25 11:31:40,966 - ERROR - ❌ No camera found!
2025-11-25 11:31:40,967 - ERROR - ❌ No camera found!
2025-11-25 11:31:40,969 - INFO - Video thread started with source: Camera
2025-11-25 11:31:40,971 - ERROR - ❌ No camera found!
2025-11-25 11:31:41,243 - INFO - Video thread started with source: Camera
2025-11-25 11:31:41,245 - INFO - Video thread started with source: Camera
2025-11-25 11:31:41,247 - ERROR - ❌ No camera found!
2025-11-25 11:31:41,248 - INFO - Video thread started with source: Camera
2025-11-25 11:31:41,248 - ERROR - ❌ No camera found!
2025-11-25 11:31:41,253 - ERROR - ❌ No camera found!
2025-11-25 11:31:41,257 - INFO - Video thread started with source: Camera
2025-11-25 11:31:41,259 - ERROR - ❌ No camera found!
2025-11-25 11:31:41,483 - INFO - Video thread started with source: Camera
2025-11-25 11:31:41,485 - INFO - Video thread started with source: Camera
2025-11-25 11:31:41,485 - ERROR - ❌ No camera found!
2025-11-25 11:31:41,486 - INFO - Video thread started with source: Camera
2025-11-25 11:31:41,486 - ERROR - ❌ No camera found!
2025-11-25 11:31:41,487 - INFO - Video thread started with source: Camera
2025-11-25 11:31:41,489 - ERROR - ❌ No camera found!
2025-11-25 11:31:41,491 - ERROR - ❌ No camera found!
2025-11-25 11:31:41,750 - INFO - Video thread started with source: Camera
2025-11-25 11:31:41,753 - INFO - Video thread started with source: Camera
2025-11-25 11:31:41,754 - ERROR - ❌ No camera found!
2025-11-25 11:31:41,754 - ERROR - ❌ No camera found!
2025-11-25 11:31:41,760 - INFO - Video thread started with source: Camera
2025-11-25 11:31:41,763 - ERROR - ❌ No camera found!
2025-11-25 11:31:41,764 - INFO - Video thread started with source: Camera
2025-11-25 11:31:41,764 - ERROR - ❌ No camera found!
2025-11-25 11:31:42,018 - INFO - Video thread started with source: Camera
2025-11-25 11:31:42,019 - INFO - Video thread started with source: Camera
2025-11-25 11:31:42,021 - ERROR - ❌ No camera found!
2025-11-25 11:31:42,021 - INFO - Video thread started with source: Camera
2025-11-25 11:31:42,022 - INFO - Video thread started with source: Camera
2025-11-25 11:31:42,022 - ERROR - ❌ No camera found!
2025-11-25 11:31:42,022 - ERROR - ❌ No camera found!
2025-11-25 11:31:42,023 - ERROR - ❌ No camera found!
2025-11-25 11:31:42,297 - INFO - Video thread started with source: Camera
2025-11-25 11:31:42,298 - INFO - Video thread started with source: Camera
2025-11-25 11:31:42,298 - ERROR - ❌ No camera found!
2025-11-25 11:31:42,298 - INFO - Video thread started with source: Camera
2025-11-25 11:31:42,299 - ERROR - ❌ No camera found!
2025-11-25 11:31:42,301 - ERROR - ❌ No camera found!
2025-11-25 11:31:42,307 - INFO - Video thread started with source: Camera
2025-11-25 11:31:42,309 - ERROR - ❌ No camera found!
2025-11-25 11:31:42,580 - INFO - Video thread started with source: Camera
2025-11-25 11:31:42,583 - INFO - Video thread started with source: Camera
2025-11-25 11:31:42,583 - ERROR - ❌ No camera found!
2025-11-25 11:31:42,584 - ERROR - ❌ No camera found!
2025-11-25 11:31:42,589 - INFO - Video thread started with source: Camera
2025-11-25 11:31:42,589 - INFO - Video thread started with source: Camera
2025-11-25 11:31:42,590 - ERROR - ❌ No camera found!
2025-11-25 11:31:42,590 - ERROR - ❌ No camera found!
2025-11-25 11:31:42,863 - INFO - Video thread started with source: Camera
2025-11-25 11:31:42,864 - INFO - Video thread started with source: Camera
2025-11-25 11:31:42,864 - INFO - Video thread started with source: Camera
2025-11-25 11:31:42,864 - ERROR - ❌ No camera found!
2025-11-25 11:31:42,865 - INFO - Video thread started with source: Camera
2025-11-25 11:31:42,865 - ERROR - ❌ No camera found!
2025-11-25 11:31:42,865 - ERROR - ❌ No camera found!
2025-11-25 11:31:42,865 - ERROR - ❌ No camera found!
2025-11-25 11:31:43,091 - INFO - Video thread started with source: Camera
2025-11-25 11:31:43,093 - INFO - Video thread started with source: Camera
2025-11-25 11:31:43,093 - ERROR - ❌ No camera found!
2025-11-25 11:31:43,094 - ERROR - ❌ No camera found!
2025-11-25 11:31:43,094 - ERROR - ❌ No camera found!
2025-11-25 11:31:43,097 - INFO - Video thread started with source: Camera
2025-11-25 11:31:43,102 - INFO - Video thread started with source: Camera
2025-11-25 11:31:43,103 - ERROR - ❌ No camera found!
2025-11-25 11:31:43,372 - INFO - Video thread started with source: Camera
2025-11-25 11:31:43,372 - INFO - Video thread started with source: Camera
2025-11-25 11:31:43,375 - ERROR - ❌ No camera found!
2025-11-25 11:31:43,375 - INFO - Video thread started with source: Camera
2025-11-25 11:31:43,376 - ERROR - ❌ No camera found!
2025-11-25 11:31:43,376 - ERROR - ❌ No camera found!
2025-11-25 11:31:43,376 - INFO - Video thread started with source: Camera
2025-11-25 11:31:43,376 - ERROR - ❌ No camera found!
2025-11-25 11:31:43,642 - INFO - Video thread started with source: Camera
2025-11-25 11:31:43,642 - INFO - Video thread started with source: Camera
2025-11-25 11:31:43,643 - ERROR - ❌ No camera found!
2025-11-25 11:31:43,648 - ERROR - ❌ No camera found!
2025-11-25 11:31:43,648 - INFO - Video thread started with source: Camera
2025-11-25 11:31:43,649 - INFO - Video thread started with source: Camera
2025-11-25 11:31:43,652 - ERROR - ❌ No camera found!
2025-11-25 11:31:43,653 - ERROR - ❌ No camera found!
2025-11-25 11:31:43,925 - INFO - Video thread started with source: Camera
2025-11-25 11:31:43,927 - INFO - Video thread started with source: Camera
2025-11-25 11:31:43,931 - ERROR - ❌ No camera found!
2025-11-25 11:31:43,931 - INFO - Video thread started with source: Camera
2025-11-25 11:31:43,931 - INFO - Video thread started with source: Camera
2025-11-25 11:31:43,931 - ERROR - ❌ No camera found!
2025-11-25 11:31:43,931 - ERROR - ❌ No camera found!
2025-11-25 11:31:43,931 - ERROR - ❌ No camera found!
2025-11-25 11:31:44,200 - INFO - Video thread started with source: Camera
2025-11-25 11:31:44,204 - INFO - Video thread started with source: Camera
2025-11-25 11:31:44,207 - INFO - Video thread started with source: Camera
2025-11-25 11:31:44,209 - ERROR - ❌ No camera found!
2025-11-25 11:31:44,209 - INFO - Video thread started with source: Camera
2025-11-25 11:31:44,209 - ERROR - ❌ No camera found!
2025-11-25 11:31:44,209 - ERROR - ❌ No camera found!
2025-11-25 11:31:44,211 - ERROR - ❌ No camera found!
2025-11-25 11:31:44,467 - INFO - Video thread started with source: Camera
2025-11-25 11:31:44,469 - INFO - Video thread started with source: Camera
2025-11-25 11:31:44,469 - ERROR - ❌ No camera found!
2025-11-25 11:31:44,469 - INFO - Video thread started with source: Camera
2025-11-25 11:31:44,470 - ERROR - ❌ No camera found!
2025-11-25 11:31:44,471 - ERROR - ❌ No camera found!
2025-11-25 11:31:44,474 - INFO - Video thread started with source: Camera
2025-11-25 11:31:44,479 - ERROR - ❌ No camera found!
2025-11-25 11:31:44,739 - INFO - Video thread started with source: Camera
2025-11-25 11:31:44,739 - INFO - Video thread started with source: Camera
2025-11-25 11:31:44,741 - ERROR - ❌ No camera found!
2025-11-25 11:31:44,741 - INFO - Video thread started with source: Camera
2025-11-25 11:31:44,742 - ERROR - ❌ No camera found!
2025-11-25 11:31:44,745 - ERROR - ❌ No camera found!
2025-11-25 11:31:44,745 - INFO - Video thread started with source: Camera
2025-11-25 11:31:44,747 - ERROR - ❌ No camera found!
2025-11-25 11:31:44,993 - INFO - Video thread started with source: Camera
2025-11-25 11:31:44,994 - INFO - Video thread started with source: Camera
2025-11-25 11:31:44,994 - ERROR - ❌ No camera found!
2025-11-25 11:31:44,996 - INFO - Video thread started with source: Camera
2025-11-25 11:31:44,996 - ERROR - ❌ No camera found!
2025-11-25 11:31:44,997 - ERROR - ❌ No camera found!
2025-11-25 11:31:44,997 - INFO - Video thread started with source: Camera
2025-11-25 11:31:44,997 - ERROR - ❌ No camera found!
2025-11-25 11:31:45,254 - INFO - Video thread started with source: Camera
2025-11-25 11:31:45,259 - INFO - Video thread started with source: Camera
2025-11-25 11:31:45,261 - INFO - Video thread started with source: Camera
2025-11-25 11:31:45,261 - ERROR - ❌ No camera found!
2025-11-25 11:31:45,261 - INFO - Video thread started with source: Camera
2025-11-25 11:31:45,262 - ERROR - ❌ No camera found!
2025-11-25 11:31:45,262 - ERROR - ❌ No camera found!
2025-11-25 11:31:45,262 - ERROR - ❌ No camera found!
2025-11-25 11:31:45,526 - INFO - Video thread started with source: Camera
2025-11-25 11:31:45,531 - INFO - Video thread started with source: Camera
2025-11-25 11:31:45,531 - INFO - Video thread started with source: Camera
2025-11-25 11:31:45,531 - ERROR - ❌ No camera found!
2025-11-25 11:31:45,531 - ERROR - ❌ No camera found!
2025-11-25 11:31:45,532 - ERROR - ❌ No camera found!
2025-11-25 11:31:45,533 - INFO - Video thread started with source: Camera
2025-11-25 11:31:45,535 - ERROR - ❌ No camera found!
2025-11-25 11:31:45,771 - INFO - Video thread started with source: Camera
2025-11-25 11:31:45,773 - INFO - Video thread started with source: Camera
2025-11-25 11:31:45,777 - INFO - Video thread started with source: Camera
2025-11-25 11:31:45,777 - ERROR - ❌ No camera found!
2025-11-25 11:31:45,777 - ERROR - ❌ No camera found!
2025-11-25 11:31:45,778 - ERROR - ❌ No camera found!
2025-11-25 11:31:45,778 - INFO - Video thread started with source: Camera
2025-11-25 11:31:45,781 - ERROR - ❌ No camera found!
2025-11-25 11:31:46,047 - INFO - Video thread started with source: Camera
2025-11-25 11:31:46,051 - ERROR - ❌ No camera found!
2025-11-25 11:31:46,052 - INFO - Video thread started with source: Camera
2025-11-25 11:31:46,054 - INFO - Video thread started with source: Camera
2025-11-25 11:31:46,055 - INFO - Video thread started with source: Camera
2025-11-25 11:31:46,055 - ERROR - ❌ No camera found!
2025-11-25 11:31:46,057 - ERROR - ❌ No camera found!
2025-11-25 11:31:46,057 - ERROR - ❌ No camera found!
2025-11-25 11:31:46,312 - INFO - Video thread started with source: Camera
2025-11-25 11:31:46,313 - ERROR - ❌ No camera found!
2025-11-25 11:31:46,312 - INFO - Video thread started with source: Camera
2025-11-25 11:31:46,316 - INFO - Video thread started with source: Camera
2025-11-25 11:31:46,318 - INFO - Video thread started with source: Camera
2025-11-25 11:31:46,318 - ERROR - ❌ No camera found!
2025-11-25 11:31:46,318 - ERROR - ❌ No camera found!
2025-11-25 11:31:46,319 - ERROR - ❌ No camera found!
2025-11-25 11:31:46,565 - INFO - Video thread started with source: Camera
2025-11-25 11:31:46,565 - INFO - Video thread started with source: Camera
2025-11-25 11:31:46,568 - INFO - Video thread started with source: Camera
2025-11-25 11:31:46,568 - ERROR - ❌ No camera found!
2025-11-25 11:31:46,568 - ERROR - ❌ No camera found!
2025-11-25 11:31:46,569 - ERROR - ❌ No camera found!
2025-11-25 11:31:46,572 - INFO - Video thread started with source: Camera
2025-11-25 11:31:46,574 - ERROR - ❌ No camera found!
2025-11-25 11:31:46,800 - INFO - Video thread started with source: Camera
2025-11-25 11:31:46,800 - INFO - Video thread started with source: Camera
2025-11-25 11:31:46,802 - INFO - Video thread started with source: Camera
2025-11-25 11:31:46,802 - ERROR - ❌ No camera found!
2025-11-25 11:31:46,803 - ERROR - ❌ No camera found!
2025-11-25 11:31:46,803 - ERROR - ❌ No camera found!
2025-11-25 11:31:46,806 - INFO - Video thread started with source: Camera
2025-11-25 11:31:46,807 - ERROR - ❌ No camera found!
2025-11-25 11:31:47,044 - INFO - Video thread started with source: Camera
2025-11-25 11:31:47,045 - INFO - Video thread started with source: Camera
2025-11-25 11:31:47,046 - INFO - Video thread started with source: Camera
2025-11-25 11:31:47,047 - ERROR - ❌ No camera found!
2025-11-25 11:31:47,047 - INFO - Video thread started with source: Camera
2025-11-25 11:31:47,048 - ERROR - ❌ No camera found!
2025-11-25 11:31:47,048 - ERROR - ❌ No camera found!
2025-11-25 11:31:47,048 - ERROR - ❌ No camera found!
2025-11-25 11:31:47,283 - INFO - Video thread started with source: Camera
2025-11-25 11:31:47,283 - INFO - Video thread started with source: Camera
2025-11-25 11:31:47,284 - ERROR - ❌ No camera found!
2025-11-25 11:31:47,286 - INFO - Video thread started with source: Camera
2025-11-25 11:31:47,286 - ERROR - ❌ No camera found!
2025-11-25 11:31:47,287 - ERROR - ❌ No camera found!
2025-11-25 11:31:47,290 - INFO - Video thread started with source: Camera
2025-11-25 11:31:47,295 - ERROR - ❌ No camera found!
2025-11-25 11:31:47,562 - INFO - Video thread started with source: Camera
2025-11-25 11:31:47,564 - INFO - Video thread started with source: Camera
2025-11-25 11:31:47,564 - ERROR - ❌ No camera found!
2025-11-25 11:31:47,567 - INFO - Video thread started with source: Camera
2025-11-25 11:31:47,570 - ERROR - ❌ No camera found!
2025-11-25 11:31:47,571 - ERROR - ❌ No camera found!
2025-11-25 11:31:47,578 - INFO - Video thread started with source: Camera
2025-11-25 11:31:47,580 - ERROR - ❌ No camera found!
2025-11-25 11:31:47,804 - INFO - Video thread started with source: Camera
2025-11-25 11:31:47,812 - INFO - Video thread started with source: Camera
2025-11-25 11:31:47,812 - ERROR - ❌ No camera found!
2025-11-25 11:31:47,813 - INFO - Video thread started with source: Camera
2025-11-25 11:31:47,813 - ERROR - ❌ No camera found!
2025-11-25 11:31:47,816 - ERROR - ❌ No camera found!
2025-11-25 11:31:47,816 - INFO - Video thread started with source: Camera
2025-11-25 11:31:47,816 - ERROR - ❌ No camera found!
2025-11-25 11:31:48,061 - INFO - Video thread started with source: Camera
2025-11-25 11:31:48,061 - INFO - Video thread started with source: Camera
2025-11-25 11:31:48,061 - INFO - Video thread started with source: Camera
2025-11-25 11:31:48,061 - INFO - Video thread started with source: Camera
2025-11-25 11:31:48,062 - ERROR - ❌ No camera found!
2025-11-25 11:31:48,062 - ERROR - ❌ No camera found!
2025-11-25 11:31:48,062 - ERROR - ❌ No camera found!
2025-11-25 11:31:48,063 - ERROR - ❌ No camera found!
2025-11-25 11:31:48,264 - INFO - Video thread started with source: Camera
2025-11-25 11:31:48,267 - ERROR - ❌ No camera found!
2025-11-25 11:31:48,268 - INFO - Video thread started with source: Camera
2025-11-25 11:31:48,326 - ERROR - ❌ No camera found!
2025-11-25 11:31:48,327 - INFO - Video thread started with source: Camera
2025-11-25 11:31:48,328 - ERROR - ❌ No camera found!
2025-11-25 11:31:48,331 - INFO - Video thread started with source: Camera
2025-11-25 11:31:48,333 - ERROR - ❌ No camera found!
2025-11-25 11:31:48,566 - INFO - Video thread started with source: Camera
2025-11-25 11:31:48,567 - INFO - Video thread started with source: Camera
2025-11-25 11:31:48,567 - ERROR - ❌ No camera found!
2025-11-25 11:31:48,568 - INFO - Video thread started with source: Camera
2025-11-25 11:31:48,568 - ERROR - ❌ No camera found!
2025-11-25 11:31:48,569 - ERROR - ❌ No camera found!
2025-11-25 11:31:48,575 - INFO - Video thread started with source: Camera
2025-11-25 11:31:48,583 - ERROR - ❌ No camera found!
2025-11-25 11:31:48,724 - INFO - Video thread started with source: Camera
2025-11-25 11:31:48,724 - ERROR - ❌ No camera found!
2025-11-25 11:31:48,840 - INFO - Video thread started with source: Camera
2025-11-25 11:31:48,842 - INFO - Video thread started with source: Camera
2025-11-25 11:31:48,843 - INFO - Video thread started with source: Camera
2025-11-25 11:31:48,843 - ERROR - ❌ No camera found!
2025-11-25 11:31:48,844 - ERROR - ❌ No camera found!
2025-11-25 11:31:48,844 - ERROR - ❌ No camera found!
2025-11-25 11:31:49,070 - INFO - Video thread started with source: Camera
2025-11-25 11:31:49,131 - INFO - Video thread started with source: Camera
2025-11-25 11:31:49,131 - ERROR - ❌ No camera found!
2025-11-25 11:31:49,132 - INFO - Video thread started with source: Camera
2025-11-25 11:31:49,132 - ERROR - ❌ No camera found!
2025-11-25 11:31:49,133 - ERROR - ❌ No camera found!
2025-11-25 11:31:49,136 - INFO - Video file uploaded: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-25 11:31:49,141 - INFO - Video thread started with source: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-25 11:31:49,152 - INFO - ✓ Video file opened: assets/temp_videos/Screen Recording 2025-11-24 at 5.54.50 PM.mov
2025-11-25 11:31:49,299 - INFO - Frame 0 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:49,300 - INFO - Video thread started with source: Camera
2025-11-25 11:31:49,302 - INFO - Video thread started with source: Camera
2025-11-25 11:31:49,305 - ERROR - ❌ No camera found!
2025-11-25 11:31:49,306 - INFO - Video thread started with source: Camera
2025-11-25 11:31:49,306 - ERROR - ❌ No camera found!
2025-11-25 11:31:49,307 - ERROR - ❌ No camera found!
2025-11-25 11:31:49,512 - INFO - Frame 2 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:49,572 - INFO - Video thread started with source: Camera
2025-11-25 11:31:49,576 - ERROR - ❌ No camera found!
2025-11-25 11:31:49,572 - INFO - Video thread started with source: Camera
2025-11-25 11:31:49,578 - INFO - Video thread started with source: Camera
2025-11-25 11:31:49,578 - ERROR - ❌ No camera found!
2025-11-25 11:31:49,579 - ERROR - ❌ No camera found!
2025-11-25 11:31:49,812 - INFO - Video thread started with source: Camera
2025-11-25 11:31:49,812 - INFO - Video thread started with source: Camera
2025-11-25 11:31:49,813 - INFO - Video thread started with source: Camera
2025-11-25 11:31:49,814 - ERROR - ❌ No camera found!
2025-11-25 11:31:49,818 - ERROR - ❌ No camera found!
2025-11-25 11:31:49,819 - ERROR - ❌ No camera found!
2025-11-25 11:31:49,826 - INFO - Frame 4 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:50,074 - INFO - Video thread started with source: Camera
2025-11-25 11:31:50,074 - INFO - Video thread started with source: Camera
2025-11-25 11:31:50,074 - INFO - Video thread started with source: Camera
2025-11-25 11:31:50,075 - ERROR - ❌ No camera found!
2025-11-25 11:31:50,075 - ERROR - ❌ No camera found!
2025-11-25 11:31:50,075 - ERROR - ❌ No camera found!
2025-11-25 11:31:50,076 - INFO - Frame 6 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:50,330 - INFO - Video thread started with source: Camera
2025-11-25 11:31:50,332 - INFO - Video thread started with source: Camera
2025-11-25 11:31:50,332 - ERROR - ❌ No camera found!
2025-11-25 11:31:50,332 - INFO - Video thread started with source: Camera
2025-11-25 11:31:50,337 - INFO - Frame 8 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:50,339 - ERROR - ❌ No camera found!
2025-11-25 11:31:50,339 - ERROR - ❌ No camera found!
2025-11-25 11:31:50,603 - INFO - Video thread started with source: Camera
2025-11-25 11:31:50,606 - INFO - Video thread started with source: Camera
2025-11-25 11:31:50,610 - ERROR - ❌ No camera found!
2025-11-25 11:31:50,613 - INFO - Frame 10 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:50,615 - ERROR - ❌ No camera found!
2025-11-25 11:31:50,615 - INFO - Video thread started with source: Camera
2025-11-25 11:31:50,619 - ERROR - ❌ No camera found!
2025-11-25 11:31:50,862 - INFO - Video thread started with source: Camera
2025-11-25 11:31:50,863 - INFO - Video thread started with source: Camera
2025-11-25 11:31:50,866 - ERROR - ❌ No camera found!
2025-11-25 11:31:50,868 - INFO - Video thread started with source: Camera
2025-11-25 11:31:50,872 - ERROR - ❌ No camera found!
2025-11-25 11:31:50,872 - ERROR - ❌ No camera found!
2025-11-25 11:31:50,872 - INFO - Frame 12 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:51,112 - INFO - Video thread started with source: Camera
2025-11-25 11:31:51,112 - INFO - Video thread started with source: Camera
2025-11-25 11:31:51,112 - INFO - Video thread started with source: Camera
2025-11-25 11:31:51,112 - ERROR - ❌ No camera found!
2025-11-25 11:31:51,113 - ERROR - ❌ No camera found!
2025-11-25 11:31:51,115 - ERROR - ❌ No camera found!
2025-11-25 11:31:51,118 - INFO - Frame 14 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:51,375 - INFO - Video thread started with source: Camera
2025-11-25 11:31:51,381 - ERROR - ❌ No camera found!
2025-11-25 11:31:51,383 - INFO - Video thread started with source: Camera
2025-11-25 11:31:51,383 - ERROR - ❌ No camera found!
2025-11-25 11:31:51,384 - INFO - Video thread started with source: Camera
2025-11-25 11:31:51,384 - ERROR - ❌ No camera found!
2025-11-25 11:31:51,390 - INFO - Frame 16 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:51,622 - INFO - Video thread started with source: Camera
2025-11-25 11:31:51,622 - INFO - Video thread started with source: Camera
2025-11-25 11:31:51,628 - INFO - Video thread started with source: Camera
2025-11-25 11:31:51,629 - ERROR - ❌ No camera found!
2025-11-25 11:31:51,629 - ERROR - ❌ No camera found!
2025-11-25 11:31:51,629 - ERROR - ❌ No camera found!
2025-11-25 11:31:51,643 - INFO - Frame 18 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:51,889 - INFO - Video thread started with source: Camera
2025-11-25 11:31:51,892 - INFO - Frame 20 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:51,892 - ERROR - ❌ No camera found!
2025-11-25 11:31:51,897 - INFO - Video thread started with source: Camera
2025-11-25 11:31:51,899 - INFO - Video thread started with source: Camera
2025-11-25 11:31:51,899 - ERROR - ❌ No camera found!
2025-11-25 11:31:51,900 - ERROR - ❌ No camera found!
2025-11-25 11:31:52,141 - INFO - Video thread started with source: Camera
2025-11-25 11:31:52,141 - INFO - Video thread started with source: Camera
2025-11-25 11:31:52,142 - INFO - Video thread started with source: Camera
2025-11-25 11:31:52,143 - ERROR - ❌ No camera found!
2025-11-25 11:31:52,143 - ERROR - ❌ No camera found!
2025-11-25 11:31:52,144 - ERROR - ❌ No camera found!
2025-11-25 11:31:52,146 - INFO - Frame 22 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:52,374 - INFO - Video thread started with source: Camera
2025-11-25 11:31:52,377 - INFO - Video thread started with source: Camera
2025-11-25 11:31:52,378 - INFO - Video thread started with source: Camera
2025-11-25 11:31:52,380 - ERROR - ❌ No camera found!
2025-11-25 11:31:52,383 - ERROR - ❌ No camera found!
2025-11-25 11:31:52,384 - ERROR - ❌ No camera found!
2025-11-25 11:31:52,403 - INFO - Frame 24 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:52,627 - INFO - Video thread started with source: Camera
2025-11-25 11:31:52,632 - ERROR - ❌ No camera found!
2025-11-25 11:31:52,632 - INFO - Video thread started with source: Camera
2025-11-25 11:31:52,632 - INFO - Video thread started with source: Camera
2025-11-25 11:31:52,633 - ERROR - ❌ No camera found!
2025-11-25 11:31:52,633 - ERROR - ❌ No camera found!
2025-11-25 11:31:52,657 - INFO - Frame 26 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:52,876 - INFO - Video thread started with source: Camera
2025-11-25 11:31:52,879 - INFO - Video thread started with source: Camera
2025-11-25 11:31:52,879 - INFO - Video thread started with source: Camera
2025-11-25 11:31:52,880 - ERROR - ❌ No camera found!
2025-11-25 11:31:52,880 - ERROR - ❌ No camera found!
2025-11-25 11:31:52,881 - ERROR - ❌ No camera found!
2025-11-25 11:31:52,907 - INFO - Frame 28 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:53,138 - INFO - Video thread started with source: Camera
2025-11-25 11:31:53,141 - ERROR - ❌ No camera found!
2025-11-25 11:31:53,141 - INFO - Video thread started with source: Camera
2025-11-25 11:31:53,144 - ERROR - ❌ No camera found!
2025-11-25 11:31:53,151 - INFO - Video thread started with source: Camera
2025-11-25 11:31:53,151 - ERROR - ❌ No camera found!
2025-11-25 11:31:53,166 - INFO - Frame 30 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:53,385 - INFO - Video thread started with source: Camera
2025-11-25 11:31:53,387 - INFO - Video thread started with source: Camera
2025-11-25 11:31:53,387 - INFO - Video thread started with source: Camera
2025-11-25 11:31:53,388 - ERROR - ❌ No camera found!
2025-11-25 11:31:53,393 - ERROR - ❌ No camera found!
2025-11-25 11:31:53,394 - ERROR - ❌ No camera found!
2025-11-25 11:31:53,411 - INFO - Frame 32 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:53,626 - INFO - Video thread started with source: Camera
2025-11-25 11:31:53,630 - INFO - Video thread started with source: Camera
2025-11-25 11:31:53,632 - INFO - Video thread started with source: Camera
2025-11-25 11:31:53,633 - ERROR - ❌ No camera found!
2025-11-25 11:31:53,633 - ERROR - ❌ No camera found!
2025-11-25 11:31:53,634 - ERROR - ❌ No camera found!
2025-11-25 11:31:53,661 - INFO - Frame 34 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:53,894 - INFO - Video thread started with source: Camera
2025-11-25 11:31:53,895 - INFO - Video thread started with source: Camera
2025-11-25 11:31:53,895 - ERROR - ❌ No camera found!
2025-11-25 11:31:53,895 - INFO - Video thread started with source: Camera
2025-11-25 11:31:53,895 - ERROR - ❌ No camera found!
2025-11-25 11:31:53,899 - ERROR - ❌ No camera found!
2025-11-25 11:31:53,922 - INFO - Frame 36 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:54,151 - INFO - Video thread started with source: Camera
2025-11-25 11:31:54,153 - ERROR - ❌ No camera found!
2025-11-25 11:31:54,154 - INFO - Video thread started with source: Camera
2025-11-25 11:31:54,157 - ERROR - ❌ No camera found!
2025-11-25 11:31:54,158 - INFO - Video thread started with source: Camera
2025-11-25 11:31:54,163 - ERROR - ❌ No camera found!
2025-11-25 11:31:54,183 - INFO - Frame 38 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:54,417 - INFO - Video thread started with source: Camera
2025-11-25 11:31:54,418 - INFO - Video thread started with source: Camera
2025-11-25 11:31:54,418 - ERROR - ❌ No camera found!
2025-11-25 11:31:54,420 - ERROR - ❌ No camera found!
2025-11-25 11:31:54,420 - INFO - Video thread started with source: Camera
2025-11-25 11:31:54,421 - ERROR - ❌ No camera found!
2025-11-25 11:31:54,447 - INFO - Frame 40 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:54,673 - INFO - Video thread started with source: Camera
2025-11-25 11:31:54,677 - INFO - Video thread started with source: Camera
2025-11-25 11:31:54,678 - ERROR - ❌ No camera found!
2025-11-25 11:31:54,681 - ERROR - ❌ No camera found!
2025-11-25 11:31:54,684 - INFO - Video thread started with source: Camera
2025-11-25 11:31:54,686 - ERROR - ❌ No camera found!
2025-11-25 11:31:54,704 - INFO - Frame 42 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:54,925 - INFO - Video thread started with source: Camera
2025-11-25 11:31:54,927 - INFO - Video thread started with source: Camera
2025-11-25 11:31:54,929 - ERROR - ❌ No camera found!
2025-11-25 11:31:54,931 - ERROR - ❌ No camera found!
2025-11-25 11:31:54,934 - INFO - Video thread started with source: Camera
2025-11-25 11:31:54,940 - ERROR - ❌ No camera found!
2025-11-25 11:31:54,951 - INFO - Frame 44 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:55,181 - INFO - Video thread started with source: Camera
2025-11-25 11:31:55,181 - INFO - Video thread started with source: Camera
2025-11-25 11:31:55,183 - ERROR - ❌ No camera found!
2025-11-25 11:31:55,184 - INFO - Video thread started with source: Camera
2025-11-25 11:31:55,184 - ERROR - ❌ No camera found!
2025-11-25 11:31:55,185 - ERROR - ❌ No camera found!
2025-11-25 11:31:55,186 - INFO - Frame 46 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:55,437 - INFO - Video thread started with source: Camera
2025-11-25 11:31:55,438 - ERROR - ❌ No camera found!
2025-11-25 11:31:55,438 - INFO - Video thread started with source: Camera
2025-11-25 11:31:55,440 - INFO - Video thread started with source: Camera
2025-11-25 11:31:55,440 - ERROR - ❌ No camera found!
2025-11-25 11:31:55,441 - ERROR - ❌ No camera found!
2025-11-25 11:31:55,448 - INFO - Frame 48 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:55,690 - INFO - Video thread started with source: Camera
2025-11-25 11:31:55,692 - INFO - Video thread started with source: Camera
2025-11-25 11:31:55,692 - INFO - Video thread started with source: Camera
2025-11-25 11:31:55,695 - ERROR - ❌ No camera found!
2025-11-25 11:31:55,696 - ERROR - ❌ No camera found!
2025-11-25 11:31:55,696 - ERROR - ❌ No camera found!
2025-11-25 11:31:55,699 - INFO - Frame 50 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:55,937 - INFO - Video thread started with source: Camera
2025-11-25 11:31:55,942 - INFO - Video thread started with source: Camera
2025-11-25 11:31:55,942 - INFO - Frame 52 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:55,946 - ERROR - ❌ No camera found!
2025-11-25 11:31:55,946 - INFO - Video thread started with source: Camera
2025-11-25 11:31:55,946 - ERROR - ❌ No camera found!
2025-11-25 11:31:55,948 - ERROR - ❌ No camera found!
2025-11-25 11:31:56,198 - INFO - Video thread started with source: Camera
2025-11-25 11:31:56,201 - ERROR - ❌ No camera found!
2025-11-25 11:31:56,201 - INFO - Frame 54 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:56,201 - INFO - Video thread started with source: Camera
2025-11-25 11:31:56,207 - ERROR - ❌ No camera found!
2025-11-25 11:31:56,212 - INFO - Video thread started with source: Camera
2025-11-25 11:31:56,213 - ERROR - ❌ No camera found!
2025-11-25 11:31:56,386 - INFO - Video thread started with source: Camera
2025-11-25 11:31:56,446 - INFO - Video thread started with source: Camera
2025-11-25 11:31:56,449 - INFO - Video thread started with source: Camera
2025-11-25 11:31:56,449 - INFO - Frame 56 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:56,450 - ERROR - ❌ No camera found!
2025-11-25 11:31:56,451 - ERROR - ❌ No camera found!
2025-11-25 11:31:56,451 - ERROR - ❌ No camera found!
2025-11-25 11:31:56,649 - INFO - Video thread started with source: Camera
2025-11-25 11:31:56,653 - INFO - Video thread started with source: Camera
2025-11-25 11:31:56,654 - ERROR - ❌ No camera found!
2025-11-25 11:31:56,655 - INFO - Video thread started with source: Camera
2025-11-25 11:31:56,714 - ERROR - ❌ No camera found!
2025-11-25 11:31:56,716 - ERROR - ❌ No camera found!
2025-11-25 11:31:56,716 - INFO - Frame 58 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:56,953 - INFO - Video thread started with source: Camera
2025-11-25 11:31:56,958 - ERROR - ❌ No camera found!
2025-11-25 11:31:56,958 - INFO - Video thread started with source: Camera
2025-11-25 11:31:56,959 - INFO - Video thread started with source: Camera
2025-11-25 11:31:56,960 - ERROR - ❌ No camera found!
2025-11-25 11:31:56,961 - ERROR - ❌ No camera found!
2025-11-25 11:31:56,973 - INFO - Frame 60 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:57,201 - INFO - Video thread started with source: Camera
2025-11-25 11:31:57,206 - ERROR - ❌ No camera found!
2025-11-25 11:31:57,210 - INFO - Video thread started with source: Camera
2025-11-25 11:31:57,210 - INFO - Video thread started with source: Camera
2025-11-25 11:31:57,213 - INFO - Frame 62 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:57,218 - ERROR - ❌ No camera found!
2025-11-25 11:31:57,218 - ERROR - ❌ No camera found!
2025-11-25 11:31:57,461 - INFO - Video thread started with source: Camera
2025-11-25 11:31:57,461 - INFO - Video thread started with source: Camera
2025-11-25 11:31:57,461 - INFO - Video thread started with source: Camera
2025-11-25 11:31:57,462 - ERROR - ❌ No camera found!
2025-11-25 11:31:57,462 - ERROR - ❌ No camera found!
2025-11-25 11:31:57,462 - ERROR - ❌ No camera found!
2025-11-25 11:31:57,463 - INFO - Frame 64 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:57,701 - INFO - Video thread started with source: Camera
2025-11-25 11:31:57,702 - INFO - Video thread started with source: Camera
2025-11-25 11:31:57,707 - INFO - Video thread started with source: Camera
2025-11-25 11:31:57,708 - ERROR - ❌ No camera found!
2025-11-25 11:31:57,708 - ERROR - ❌ No camera found!
2025-11-25 11:31:57,709 - INFO - Frame 66 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:57,709 - ERROR - ❌ No camera found!
2025-11-25 11:31:57,957 - INFO - Video thread started with source: Camera
2025-11-25 11:31:57,959 - INFO - Video thread started with source: Camera
2025-11-25 11:31:57,965 - ERROR - ❌ No camera found!
2025-11-25 11:31:57,965 - INFO - Video thread started with source: Camera
2025-11-25 11:31:57,965 - ERROR - ❌ No camera found!
2025-11-25 11:31:57,965 - INFO - Frame 68 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:57,965 - ERROR - ❌ No camera found!
2025-11-25 11:31:58,203 - INFO - Video thread started with source: Camera
2025-11-25 11:31:58,204 - INFO - Video thread started with source: Camera
2025-11-25 11:31:58,204 - ERROR - ❌ No camera found!
2025-11-25 11:31:58,206 - ERROR - ❌ No camera found!
2025-11-25 11:31:58,209 - INFO - Video thread started with source: Camera
2025-11-25 11:31:58,209 - INFO - Frame 70 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:58,210 - ERROR - ❌ No camera found!
2025-11-25 11:31:58,396 - INFO - Video thread started with source: Camera
2025-11-25 11:31:58,453 - ERROR - ❌ No camera found!
2025-11-25 11:31:58,453 - INFO - Video thread started with source: Camera
2025-11-25 11:31:58,462 - ERROR - ❌ No camera found!
2025-11-25 11:31:58,462 - INFO - Frame 72 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:58,465 - INFO - Video thread started with source: Camera
2025-11-25 11:31:58,466 - ERROR - ❌ No camera found!
2025-11-25 11:31:58,700 - INFO - Video thread started with source: Camera
2025-11-25 11:31:58,704 - INFO - Video thread started with source: Camera
2025-11-25 11:31:58,705 - INFO - Video thread started with source: Camera
2025-11-25 11:31:58,705 - ERROR - ❌ No camera found!
2025-11-25 11:31:58,707 - ERROR - ❌ No camera found!
2025-11-25 11:31:58,712 - ERROR - ❌ No camera found!
2025-11-25 11:31:58,714 - INFO - Frame 74 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:58,957 - INFO - Video thread started with source: Camera
2025-11-25 11:31:58,960 - INFO - Video thread started with source: Camera
2025-11-25 11:31:58,960 - INFO - Video thread started with source: Camera
2025-11-25 11:31:58,960 - ERROR - ❌ No camera found!
2025-11-25 11:31:58,960 - ERROR - ❌ No camera found!
2025-11-25 11:31:58,964 - ERROR - ❌ No camera found!
2025-11-25 11:31:58,964 - INFO - Frame 76 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:59,205 - INFO - Video thread started with source: Camera
2025-11-25 11:31:59,205 - ERROR - ❌ No camera found!
2025-11-25 11:31:59,207 - INFO - Video thread started with source: Camera
2025-11-25 11:31:59,209 - ERROR - ❌ No camera found!
2025-11-25 11:31:59,216 - INFO - Video thread started with source: Camera
2025-11-25 11:31:59,218 - ERROR - ❌ No camera found!
2025-11-25 11:31:59,222 - INFO - Frame 78 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:59,451 - INFO - Video thread started with source: Camera
2025-11-25 11:31:59,451 - INFO - Video thread started with source: Camera
2025-11-25 11:31:59,451 - INFO - Video thread started with source: Camera
2025-11-25 11:31:59,452 - ERROR - ❌ No camera found!
2025-11-25 11:31:59,452 - INFO - Frame 80 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:59,455 - ERROR - ❌ No camera found!
2025-11-25 11:31:59,455 - ERROR - ❌ No camera found!
2025-11-25 11:31:59,713 - INFO - Video thread started with source: Camera
2025-11-25 11:31:59,716 - ERROR - ❌ No camera found!
2025-11-25 11:31:59,719 - INFO - Video thread started with source: Camera
2025-11-25 11:31:59,723 - ERROR - ❌ No camera found!
2025-11-25 11:31:59,724 - INFO - Frame 82 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:59,730 - INFO - Video thread started with source: Camera
2025-11-25 11:31:59,732 - ERROR - ❌ No camera found!
2025-11-25 11:31:59,976 - INFO - Video thread started with source: Camera
2025-11-25 11:31:59,984 - INFO - Video thread started with source: Camera
2025-11-25 11:31:59,984 - ERROR - ❌ No camera found!
2025-11-25 11:31:59,985 - ERROR - ❌ No camera found!
2025-11-25 11:31:59,986 - INFO - Video thread started with source: Camera
2025-11-25 11:31:59,986 - INFO - Frame 84 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:31:59,986 - ERROR - ❌ No camera found!
2025-11-25 11:32:00,237 - INFO - Video thread started with source: Camera
2025-11-25 11:32:00,238 - INFO - Video thread started with source: Camera
2025-11-25 11:32:00,243 - INFO - Video thread started with source: Camera
2025-11-25 11:32:00,243 - ERROR - ❌ No camera found!
2025-11-25 11:32:00,244 - ERROR - ❌ No camera found!
2025-11-25 11:32:00,247 - ERROR - ❌ No camera found!
2025-11-25 11:32:00,253 - INFO - Frame 86 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:00,505 - INFO - Video thread started with source: Camera
2025-11-25 11:32:00,505 - INFO - Video thread started with source: Camera
2025-11-25 11:32:00,505 - INFO - Video thread started with source: Camera
2025-11-25 11:32:00,506 - ERROR - ❌ No camera found!
2025-11-25 11:32:00,509 - ERROR - ❌ No camera found!
2025-11-25 11:32:00,509 - INFO - Frame 88 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:00,509 - ERROR - ❌ No camera found!
2025-11-25 11:32:00,754 - INFO - Video thread started with source: Camera
2025-11-25 11:32:00,755 - ERROR - ❌ No camera found!
2025-11-25 11:32:00,759 - INFO - Video thread started with source: Camera
2025-11-25 11:32:00,759 - ERROR - ❌ No camera found!
2025-11-25 11:32:00,760 - INFO - Video thread started with source: Camera
2025-11-25 11:32:00,764 - INFO - Frame 90 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:00,765 - ERROR - ❌ No camera found!
2025-11-25 11:32:01,017 - INFO - Video thread started with source: Camera
2025-11-25 11:32:01,020 - INFO - Video thread started with source: Camera
2025-11-25 11:32:01,020 - ERROR - ❌ No camera found!
2025-11-25 11:32:01,020 - INFO - Frame 92 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:01,021 - ERROR - ❌ No camera found!
2025-11-25 11:32:01,021 - INFO - Video thread started with source: Camera
2025-11-25 11:32:01,026 - ERROR - ❌ No camera found!
2025-11-25 11:32:01,265 - INFO - Frame 94 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:01,272 - INFO - Video thread started with source: Camera
2025-11-25 11:32:01,274 - ERROR - ❌ No camera found!
2025-11-25 11:32:01,278 - INFO - Video thread started with source: Camera
2025-11-25 11:32:01,280 - INFO - Video thread started with source: Camera
2025-11-25 11:32:01,283 - ERROR - ❌ No camera found!
2025-11-25 11:32:01,285 - ERROR - ❌ No camera found!
2025-11-25 11:32:01,519 - INFO - Frame 96 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:01,529 - INFO - Video thread started with source: Camera
2025-11-25 11:32:01,533 - INFO - Video thread started with source: Camera
2025-11-25 11:32:01,537 - ERROR - ❌ No camera found!
2025-11-25 11:32:01,537 - ERROR - ❌ No camera found!
2025-11-25 11:32:01,537 - INFO - Video thread started with source: Camera
2025-11-25 11:32:01,539 - ERROR - ❌ No camera found!
2025-11-25 11:32:01,765 - INFO - Frame 98 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:01,769 - INFO - Video thread started with source: Camera
2025-11-25 11:32:01,770 - INFO - Video thread started with source: Camera
2025-11-25 11:32:01,772 - INFO - Video thread started with source: Camera
2025-11-25 11:32:01,774 - ERROR - ❌ No camera found!
2025-11-25 11:32:01,774 - ERROR - ❌ No camera found!
2025-11-25 11:32:01,774 - ERROR - ❌ No camera found!
2025-11-25 11:32:02,054 - INFO - Video thread started with source: Camera
2025-11-25 11:32:02,055 - INFO - Frame 100 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:02,060 - INFO - Video thread started with source: Camera
2025-11-25 11:32:02,061 - ERROR - ❌ No camera found!
2025-11-25 11:32:02,068 - ERROR - ❌ No camera found!
2025-11-25 11:32:02,073 - INFO - Video thread started with source: Camera
2025-11-25 11:32:02,074 - ERROR - ❌ No camera found!
2025-11-25 11:32:02,286 - INFO - Frame 102 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:02,289 - INFO - Video thread started with source: Camera
2025-11-25 11:32:02,293 - ERROR - ❌ No camera found!
2025-11-25 11:32:02,297 - INFO - Video thread started with source: Camera
2025-11-25 11:32:02,298 - ERROR - ❌ No camera found!
2025-11-25 11:32:02,301 - INFO - Video thread started with source: Camera
2025-11-25 11:32:02,306 - ERROR - ❌ No camera found!
2025-11-25 11:32:02,538 - INFO - Video thread started with source: Camera
2025-11-25 11:32:02,540 - INFO - Frame 104 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:02,542 - INFO - Video thread started with source: Camera
2025-11-25 11:32:02,542 - INFO - Video thread started with source: Camera
2025-11-25 11:32:02,543 - ERROR - ❌ No camera found!
2025-11-25 11:32:02,543 - ERROR - ❌ No camera found!
2025-11-25 11:32:02,551 - ERROR - ❌ No camera found!
2025-11-25 11:32:02,787 - INFO - Video thread started with source: Camera
2025-11-25 11:32:02,787 - INFO - Video thread started with source: Camera
2025-11-25 11:32:02,787 - INFO - Video thread started with source: Camera
2025-11-25 11:32:02,788 - ERROR - ❌ No camera found!
2025-11-25 11:32:02,788 - ERROR - ❌ No camera found!
2025-11-25 11:32:02,789 - ERROR - ❌ No camera found!
2025-11-25 11:32:02,799 - INFO - Frame 106 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:03,034 - INFO - Video thread started with source: Camera
2025-11-25 11:32:03,042 - ERROR - ❌ No camera found!
2025-11-25 11:32:03,043 - INFO - Video thread started with source: Camera
2025-11-25 11:32:03,045 - ERROR - ❌ No camera found!
2025-11-25 11:32:03,045 - INFO - Video thread started with source: Camera
2025-11-25 11:32:03,045 - ERROR - ❌ No camera found!
2025-11-25 11:32:03,053 - INFO - Frame 108 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:03,291 - INFO - Video thread started with source: Camera
2025-11-25 11:32:03,292 - INFO - Video thread started with source: Camera
2025-11-25 11:32:03,293 - ERROR - ❌ No camera found!
2025-11-25 11:32:03,294 - INFO - Video thread started with source: Camera
2025-11-25 11:32:03,294 - ERROR - ❌ No camera found!
2025-11-25 11:32:03,297 - ERROR - ❌ No camera found!
2025-11-25 11:32:03,304 - INFO - Frame 110 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:03,533 - INFO - Video thread started with source: Camera
2025-11-25 11:32:03,536 - INFO - Video thread started with source: Camera
2025-11-25 11:32:03,537 - ERROR - ❌ No camera found!
2025-11-25 11:32:03,538 - INFO - Video thread started with source: Camera
2025-11-25 11:32:03,538 - ERROR - ❌ No camera found!
2025-11-25 11:32:03,541 - ERROR - ❌ No camera found!
2025-11-25 11:32:03,546 - INFO - Frame 112 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:03,776 - INFO - Video thread started with source: Camera
2025-11-25 11:32:03,777 - INFO - Video thread started with source: Camera
2025-11-25 11:32:03,779 - ERROR - ❌ No camera found!
2025-11-25 11:32:03,780 - ERROR - ❌ No camera found!
2025-11-25 11:32:03,782 - INFO - Video thread started with source: Camera
2025-11-25 11:32:03,782 - INFO - Frame 114 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:03,782 - ERROR - ❌ No camera found!
2025-11-25 11:32:04,047 - INFO - Video thread started with source: Camera
2025-11-25 11:32:04,053 - ERROR - ❌ No camera found!
2025-11-25 11:32:04,054 - INFO - Video thread started with source: Camera
2025-11-25 11:32:04,056 - INFO - Video thread started with source: Camera
2025-11-25 11:32:04,056 - ERROR - ❌ No camera found!
2025-11-25 11:32:04,057 - INFO - Frame 116 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:04,060 - ERROR - ❌ No camera found!
2025-11-25 11:32:04,303 - INFO - Video thread started with source: Camera
2025-11-25 11:32:04,307 - INFO - Video thread started with source: Camera
2025-11-25 11:32:04,308 - ERROR - ❌ No camera found!
2025-11-25 11:32:04,312 - INFO - Frame 118 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:04,313 - INFO - Video thread started with source: Camera
2025-11-25 11:32:04,314 - ERROR - ❌ No camera found!
2025-11-25 11:32:04,317 - ERROR - ❌ No camera found!
2025-11-25 11:32:04,554 - INFO - Video thread started with source: Camera
2025-11-25 11:32:04,558 - INFO - Video thread started with source: Camera
2025-11-25 11:32:04,559 - ERROR - ❌ No camera found!
2025-11-25 11:32:04,562 - INFO - Video thread started with source: Camera
2025-11-25 11:32:04,565 - ERROR - ❌ No camera found!
2025-11-25 11:32:04,567 - ERROR - ❌ No camera found!
2025-11-25 11:32:04,567 - INFO - Frame 120 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:04,799 - INFO - Video thread started with source: Camera
2025-11-25 11:32:04,803 - ERROR - ❌ No camera found!
2025-11-25 11:32:04,803 - INFO - Video thread started with source: Camera
2025-11-25 11:32:04,807 - INFO - Video thread started with source: Camera
2025-11-25 11:32:04,807 - ERROR - ❌ No camera found!
2025-11-25 11:32:04,808 - ERROR - ❌ No camera found!
2025-11-25 11:32:04,816 - INFO - Frame 122 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:05,060 - INFO - Video thread started with source: Camera
2025-11-25 11:32:05,063 - INFO - Video thread started with source: Camera
2025-11-25 11:32:05,064 - INFO - Frame 124 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:05,065 - ERROR - ❌ No camera found!
2025-11-25 11:32:05,065 - ERROR - ❌ No camera found!
2025-11-25 11:32:05,066 - INFO - Video thread started with source: Camera
2025-11-25 11:32:05,066 - ERROR - ❌ No camera found!
2025-11-25 11:32:05,304 - INFO - Video thread started with source: Camera
2025-11-25 11:32:05,308 - ERROR - ❌ No camera found!
2025-11-25 11:32:05,311 - INFO - Frame 126 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:05,316 - INFO - Video thread started with source: Camera
2025-11-25 11:32:05,320 - INFO - Video thread started with source: Camera
2025-11-25 11:32:05,321 - ERROR - ❌ No camera found!
2025-11-25 11:32:05,323 - ERROR - ❌ No camera found!
2025-11-25 11:32:05,497 - INFO - Frame 128 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:05,557 - INFO - Video thread started with source: Camera
2025-11-25 11:32:05,560 - ERROR - ❌ No camera found!
2025-11-25 11:32:05,562 - INFO - Video thread started with source: Camera
2025-11-25 11:32:05,563 - INFO - Video thread started with source: Camera
2025-11-25 11:32:05,566 - ERROR - ❌ No camera found!
2025-11-25 11:32:05,571 - ERROR - ❌ No camera found!
2025-11-25 11:32:05,746 - INFO - Frame 130 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:05,806 - INFO - Video thread started with source: Camera
2025-11-25 11:32:05,806 - INFO - Video thread started with source: Camera
2025-11-25 11:32:05,807 - ERROR - ❌ No camera found!
2025-11-25 11:32:05,809 - ERROR - ❌ No camera found!
2025-11-25 11:32:05,809 - INFO - Video thread started with source: Camera
2025-11-25 11:32:05,810 - ERROR - ❌ No camera found!
2025-11-25 11:32:05,829 - INFO - Frame 132 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:06,059 - INFO - Video thread started with source: Camera
2025-11-25 11:32:06,061 - INFO - Video thread started with source: Camera
2025-11-25 11:32:06,061 - INFO - Video thread started with source: Camera
2025-11-25 11:32:06,061 - ERROR - ❌ No camera found!
2025-11-25 11:32:06,066 - ERROR - ❌ No camera found!
2025-11-25 11:32:06,066 - ERROR - ❌ No camera found!
2025-11-25 11:32:06,076 - INFO - Frame 134 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:06,334 - INFO - Video thread started with source: Camera
2025-11-25 11:32:06,335 - INFO - Video thread started with source: Camera
2025-11-25 11:32:06,335 - ERROR - ❌ No camera found!
2025-11-25 11:32:06,336 - ERROR - ❌ No camera found!
2025-11-25 11:32:06,337 - INFO - Video thread started with source: Camera
2025-11-25 11:32:06,340 - ERROR - ❌ No camera found!
2025-11-25 11:32:06,341 - INFO - Frame 136 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:06,583 - INFO - Video thread started with source: Camera
2025-11-25 11:32:06,585 - INFO - Video thread started with source: Camera
2025-11-25 11:32:06,585 - INFO - Video thread started with source: Camera
2025-11-25 11:32:06,585 - INFO - Frame 138 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:06,585 - ERROR - ❌ No camera found!
2025-11-25 11:32:06,585 - ERROR - ❌ No camera found!
2025-11-25 11:32:06,588 - ERROR - ❌ No camera found!
2025-11-25 11:32:06,827 - INFO - Video thread started with source: Camera
2025-11-25 11:32:06,829 - INFO - Video thread started with source: Camera
2025-11-25 11:32:06,829 - ERROR - ❌ No camera found!
2025-11-25 11:32:06,832 - ERROR - ❌ No camera found!
2025-11-25 11:32:06,835 - INFO - Video thread started with source: Camera
2025-11-25 11:32:06,840 - ERROR - ❌ No camera found!
2025-11-25 11:32:06,843 - INFO - Frame 140 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:07,084 - INFO - Video thread started with source: Camera
2025-11-25 11:32:07,093 - ERROR - ❌ No camera found!
2025-11-25 11:32:07,094 - INFO - Video thread started with source: Camera
2025-11-25 11:32:07,103 - INFO - Video thread started with source: Camera
2025-11-25 11:32:07,106 - ERROR - ❌ No camera found!
2025-11-25 11:32:07,107 - ERROR - ❌ No camera found!
2025-11-25 11:32:07,116 - INFO - Frame 142 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:07,352 - INFO - Frame 144 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:07,354 - INFO - Video thread started with source: Camera
2025-11-25 11:32:07,354 - INFO - Video thread started with source: Camera
2025-11-25 11:32:07,357 - ERROR - ❌ No camera found!
2025-11-25 11:32:07,360 - INFO - Video thread started with source: Camera
2025-11-25 11:32:07,360 - ERROR - ❌ No camera found!
2025-11-25 11:32:07,360 - ERROR - ❌ No camera found!
2025-11-25 11:32:07,538 - INFO - Frame 146 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:07,597 - INFO - Video thread started with source: Camera
2025-11-25 11:32:07,603 - INFO - Video thread started with source: Camera
2025-11-25 11:32:07,605 - INFO - Video thread started with source: Camera
2025-11-25 11:32:07,605 - ERROR - ❌ No camera found!
2025-11-25 11:32:07,606 - ERROR - ❌ No camera found!
2025-11-25 11:32:07,610 - ERROR - ❌ No camera found!
2025-11-25 11:32:07,842 - INFO - Video thread started with source: Camera
2025-11-25 11:32:07,844 - INFO - Frame 148 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:07,846 - INFO - Video thread started with source: Camera
2025-11-25 11:32:07,847 - ERROR - ❌ No camera found!
2025-11-25 11:32:07,847 - ERROR - ❌ No camera found!
2025-11-25 11:32:07,848 - INFO - Video thread started with source: Camera
2025-11-25 11:32:07,849 - ERROR - ❌ No camera found!
2025-11-25 11:32:08,086 - INFO - Video thread started with source: Camera
2025-11-25 11:32:08,086 - INFO - Video thread started with source: Camera
2025-11-25 11:32:08,087 - ERROR - ❌ No camera found!
2025-11-25 11:32:08,087 - INFO - Video thread started with source: Camera
2025-11-25 11:32:08,089 - ERROR - ❌ No camera found!
2025-11-25 11:32:08,090 - ERROR - ❌ No camera found!
2025-11-25 11:32:08,101 - INFO - Frame 150 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:08,327 - INFO - Video thread started with source: Camera
2025-11-25 11:32:08,330 - ERROR - ❌ No camera found!
2025-11-25 11:32:08,330 - INFO - Video thread started with source: Camera
2025-11-25 11:32:08,332 - INFO - Video thread started with source: Camera
2025-11-25 11:32:08,338 - ERROR - ❌ No camera found!
2025-11-25 11:32:08,340 - ERROR - ❌ No camera found!
2025-11-25 11:32:08,343 - INFO - Frame 152 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:08,588 - INFO - Video thread started with source: Camera
2025-11-25 11:32:08,588 - INFO - Video thread started with source: Camera
2025-11-25 11:32:08,590 - INFO - Video thread started with source: Camera
2025-11-25 11:32:08,590 - ERROR - ❌ No camera found!
2025-11-25 11:32:08,591 - ERROR - ❌ No camera found!
2025-11-25 11:32:08,591 - ERROR - ❌ No camera found!
2025-11-25 11:32:08,598 - INFO - Frame 154 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:08,847 - INFO - Video thread started with source: Camera
2025-11-25 11:32:08,849 - INFO - Video thread started with source: Camera
2025-11-25 11:32:08,849 - INFO - Video thread started with source: Camera
2025-11-25 11:32:08,850 - INFO - Frame 156 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:08,850 - ERROR - ❌ No camera found!
2025-11-25 11:32:08,850 - ERROR - ❌ No camera found!
2025-11-25 11:32:08,851 - ERROR - ❌ No camera found!
2025-11-25 11:32:09,096 - INFO - Video thread started with source: Camera
2025-11-25 11:32:09,098 - INFO - Video thread started with source: Camera
2025-11-25 11:32:09,099 - ERROR - ❌ No camera found!
2025-11-25 11:32:09,100 - INFO - Video thread started with source: Camera
2025-11-25 11:32:09,100 - ERROR - ❌ No camera found!
2025-11-25 11:32:09,101 - ERROR - ❌ No camera found!
2025-11-25 11:32:09,101 - INFO - Frame 158 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:09,359 - INFO - Video thread started with source: Camera
2025-11-25 11:32:09,361 - INFO - Video thread started with source: Camera
2025-11-25 11:32:09,361 - INFO - Video thread started with source: Camera
2025-11-25 11:32:09,362 - ERROR - ❌ No camera found!
2025-11-25 11:32:09,362 - ERROR - ❌ No camera found!
2025-11-25 11:32:09,362 - ERROR - ❌ No camera found!
2025-11-25 11:32:09,362 - INFO - Frame 160 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:09,602 - INFO - Video thread started with source: Camera
2025-11-25 11:32:09,605 - ERROR - ❌ No camera found!
2025-11-25 11:32:09,607 - INFO - Video thread started with source: Camera
2025-11-25 11:32:09,607 - ERROR - ❌ No camera found!
2025-11-25 11:32:09,610 - INFO - Video thread started with source: Camera
2025-11-25 11:32:09,610 - ERROR - ❌ No camera found!
2025-11-25 11:32:09,615 - INFO - Frame 162 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:09,865 - INFO - Video thread started with source: Camera
2025-11-25 11:32:09,865 - INFO - Video thread started with source: Camera
2025-11-25 11:32:09,872 - ERROR - ❌ No camera found!
2025-11-25 11:32:09,875 - ERROR - ❌ No camera found!
2025-11-25 11:32:09,875 - INFO - Video thread started with source: Camera
2025-11-25 11:32:09,875 - INFO - Frame 164 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:09,878 - ERROR - ❌ No camera found!
2025-11-25 11:32:10,116 - INFO - Video thread started with source: Camera
2025-11-25 11:32:10,116 - ERROR - ❌ No camera found!
2025-11-25 11:32:10,126 - INFO - Video thread started with source: Camera
2025-11-25 11:32:10,127 - ERROR - ❌ No camera found!
2025-11-25 11:32:10,133 - INFO - Video thread started with source: Camera
2025-11-25 11:32:10,135 - ERROR - ❌ No camera found!
2025-11-25 11:32:10,394 - INFO - Video thread started with source: Camera
2025-11-25 11:32:10,402 - INFO - Video thread started with source: Camera
2025-11-25 11:32:10,405 - ERROR - ❌ No camera found!
2025-11-25 11:32:10,407 - ERROR - ❌ No camera found!
2025-11-25 11:32:10,408 - INFO - Frame 166 | PERCLOS: 0.00 | Yaw: -1.8° | Alerts: 0
2025-11-25 11:32:10,410 - INFO - Video thread started with source: Camera
2025-11-25 11:32:10,413 - ERROR - ❌ No camera found!
2025-11-25 11:32:10,659 - INFO - Video thread started with source: Camera
2025-11-25 11:32:10,659 - INFO - Video thread started with source: Camera
2025-11-25 11:32:10,660 - ERROR - ❌ No camera found!
2025-11-25 11:32:10,660 - ERROR - ❌ No camera found!
2025-11-25 11:32:10,664 - INFO - Video thread started with source: Camera
2025-11-25 11:32:10,665 - ERROR - ❌ No camera found!
2025-11-25 11:32:10,665 - INFO - Frame 168 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:10,910 - INFO - Video thread started with source: Camera
2025-11-25 11:32:10,911 - INFO - Video thread started with source: Camera
2025-11-25 11:32:10,916 - ERROR - ❌ No camera found!
2025-11-25 11:32:10,916 - ERROR - ❌ No camera found!
2025-11-25 11:32:10,918 - INFO - Video thread started with source: Camera
2025-11-25 11:32:10,918 - INFO - Frame 170 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:10,921 - ERROR - ❌ No camera found!
2025-11-25 11:32:11,154 - INFO - Video thread started with source: Camera
2025-11-25 11:32:11,154 - INFO - Video thread started with source: Camera
2025-11-25 11:32:11,155 - ERROR - ❌ No camera found!
2025-11-25 11:32:11,159 - ERROR - ❌ No camera found!
2025-11-25 11:32:11,159 - INFO - Frame 172 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:11,159 - INFO - Video thread started with source: Camera
2025-11-25 11:32:11,161 - ERROR - ❌ No camera found!
2025-11-25 11:32:11,409 - INFO - Video thread started with source: Camera
2025-11-25 11:32:11,410 - INFO - Video thread started with source: Camera
2025-11-25 11:32:11,410 - ERROR - ❌ No camera found!
2025-11-25 11:32:11,410 - INFO - Video thread started with source: Camera
2025-11-25 11:32:11,411 - ERROR - ❌ No camera found!
2025-11-25 11:32:11,411 - ERROR - ❌ No camera found!
2025-11-25 11:32:11,424 - INFO - Frame 174 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:11,651 - INFO - Video thread started with source: Camera
2025-11-25 11:32:11,655 - ERROR - ❌ No camera found!
2025-11-25 11:32:11,659 - INFO - Video thread started with source: Camera
2025-11-25 11:32:11,665 - INFO - Video thread started with source: Camera
2025-11-25 11:32:11,665 - ERROR - ❌ No camera found!
2025-11-25 11:32:11,665 - INFO - Frame 176 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:11,666 - ERROR - ❌ No camera found!
2025-11-25 11:32:11,911 - INFO - Video thread started with source: Camera
2025-11-25 11:32:11,917 - INFO - Video thread started with source: Camera
2025-11-25 11:32:11,917 - ERROR - ❌ No camera found!
2025-11-25 11:32:11,917 - INFO - Frame 178 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:11,925 - INFO - Video thread started with source: Camera
2025-11-25 11:32:11,925 - ERROR - ❌ No camera found!
2025-11-25 11:32:11,926 - ERROR - ❌ No camera found!
2025-11-25 11:32:12,172 - INFO - Frame 180 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:12,172 - INFO - Video thread started with source: Camera
2025-11-25 11:32:12,175 - ERROR - ❌ No camera found!
2025-11-25 11:32:12,185 - INFO - Video thread started with source: Camera
2025-11-25 11:32:12,185 - INFO - Video thread started with source: Camera
2025-11-25 11:32:12,185 - ERROR - ❌ No camera found!
2025-11-25 11:32:12,187 - ERROR - ❌ No camera found!
2025-11-25 11:32:12,436 - INFO - Frame 182 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:12,441 - INFO - Video thread started with source: Camera
2025-11-25 11:32:12,441 - ERROR - ❌ No camera found!
2025-11-25 11:32:12,442 - INFO - Video thread started with source: Camera
2025-11-25 11:32:12,442 - ERROR - ❌ No camera found!
2025-11-25 11:32:12,451 - INFO - Video thread started with source: Camera
2025-11-25 11:32:12,452 - ERROR - ❌ No camera found!
2025-11-25 11:32:12,681 - INFO - Video thread started with source: Camera
2025-11-25 11:32:12,682 - INFO - Video thread started with source: Camera
2025-11-25 11:32:12,684 - ERROR - ❌ No camera found!
2025-11-25 11:32:12,688 - INFO - Frame 184 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:12,688 - INFO - Video thread started with source: Camera
2025-11-25 11:32:12,688 - ERROR - ❌ No camera found!
2025-11-25 11:32:12,693 - ERROR - ❌ No camera found!
2025-11-25 11:32:12,936 - INFO - Video thread started with source: Camera
2025-11-25 11:32:12,940 - INFO - Video thread started with source: Camera
2025-11-25 11:32:12,940 - INFO - Frame 186 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:12,941 - INFO - Video thread started with source: Camera
2025-11-25 11:32:12,942 - ERROR - ❌ No camera found!
2025-11-25 11:32:12,942 - ERROR - ❌ No camera found!
2025-11-25 11:32:12,943 - ERROR - ❌ No camera found!
2025-11-25 11:32:13,180 - INFO - Video thread started with source: Camera
2025-11-25 11:32:13,181 - INFO - Video thread started with source: Camera
2025-11-25 11:32:13,182 - INFO - Frame 188 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:13,184 - INFO - Video thread started with source: Camera
2025-11-25 11:32:13,184 - ERROR - ❌ No camera found!
2025-11-25 11:32:13,184 - ERROR - ❌ No camera found!
2025-11-25 11:32:13,189 - ERROR - ❌ No camera found!
2025-11-25 11:32:13,424 - INFO - Video thread started with source: Camera
2025-11-25 11:32:13,426 - INFO - Video thread started with source: Camera
2025-11-25 11:32:13,427 - INFO - Video thread started with source: Camera
2025-11-25 11:32:13,427 - ERROR - ❌ No camera found!
2025-11-25 11:32:13,428 - INFO - Frame 190 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:13,428 - ERROR - ❌ No camera found!
2025-11-25 11:32:13,429 - ERROR - ❌ No camera found!
2025-11-25 11:32:13,669 - INFO - Video thread started with source: Camera
2025-11-25 11:32:13,672 - ERROR - ❌ No camera found!
2025-11-25 11:32:13,672 - INFO - Video thread started with source: Camera
2025-11-25 11:32:13,673 - ERROR - ❌ No camera found!
2025-11-25 11:32:13,673 - INFO - Frame 192 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:13,675 - INFO - Video thread started with source: Camera
2025-11-25 11:32:13,678 - ERROR - ❌ No camera found!
2025-11-25 11:32:13,910 - INFO - Video thread started with source: Camera
2025-11-25 11:32:13,918 - ERROR - ❌ No camera found!
2025-11-25 11:32:13,926 - INFO - Video thread started with source: Camera
2025-11-25 11:32:13,928 - INFO - Frame 194 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:13,930 - INFO - Video thread started with source: Camera
2025-11-25 11:32:13,930 - ERROR - ❌ No camera found!
2025-11-25 11:32:13,931 - ERROR - ❌ No camera found!
2025-11-25 11:32:14,156 - INFO - Video thread started with source: Camera
2025-11-25 11:32:14,160 - INFO - Video thread started with source: Camera
2025-11-25 11:32:14,168 - ERROR - ❌ No camera found!
2025-11-25 11:32:14,171 - ERROR - ❌ No camera found!
2025-11-25 11:32:14,173 - ERROR - ❌ No camera found!
2025-11-25 11:32:14,175 - INFO - Video thread started with source: Camera
2025-11-25 11:32:14,175 - INFO - Frame 196 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:14,428 - INFO - Video thread started with source: Camera
2025-11-25 11:32:14,430 - ERROR - ❌ No camera found!
2025-11-25 11:32:14,432 - INFO - Video thread started with source: Camera
2025-11-25 11:32:14,434 - INFO - Video thread started with source: Camera
2025-11-25 11:32:14,437 - ERROR - ❌ No camera found!
2025-11-25 11:32:14,439 - INFO - Frame 198 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:14,440 - ERROR - ❌ No camera found!
2025-11-25 11:32:14,680 - INFO - Video thread started with source: Camera
2025-11-25 11:32:14,685 - INFO - Video thread started with source: Camera
2025-11-25 11:32:14,686 - ERROR - ❌ No camera found!
2025-11-25 11:32:14,686 - ERROR - ❌ No camera found!
2025-11-25 11:32:14,688 - INFO - Video thread started with source: Camera
2025-11-25 11:32:14,688 - INFO - Frame 200 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:14,689 - ERROR - ❌ No camera found!
2025-11-25 11:32:14,941 - INFO - Video thread started with source: Camera
2025-11-25 11:32:14,941 - INFO - Video thread started with source: Camera
2025-11-25 11:32:14,942 - ERROR - ❌ No camera found!
2025-11-25 11:32:14,943 - ERROR - ❌ No camera found!
2025-11-25 11:32:14,944 - INFO - Frame 202 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:14,946 - INFO - Video thread started with source: Camera
2025-11-25 11:32:14,952 - ERROR - ❌ No camera found!
2025-11-25 11:32:15,193 - INFO - Video thread started with source: Camera
2025-11-25 11:32:15,200 - INFO - Video thread started with source: Camera
2025-11-25 11:32:15,200 - ERROR - ❌ No camera found!
2025-11-25 11:32:15,200 - INFO - Video thread started with source: Camera
2025-11-25 11:32:15,200 - ERROR - ❌ No camera found!
2025-11-25 11:32:15,204 - ERROR - ❌ No camera found!
2025-11-25 11:32:15,210 - INFO - Frame 204 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:15,456 - INFO - Video thread started with source: Camera
2025-11-25 11:32:15,456 - INFO - Video thread started with source: Camera
2025-11-25 11:32:15,459 - ERROR - ❌ No camera found!
2025-11-25 11:32:15,459 - INFO - Video thread started with source: Camera
2025-11-25 11:32:15,460 - INFO - Frame 206 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:15,460 - ERROR - ❌ No camera found!
2025-11-25 11:32:15,460 - ERROR - ❌ No camera found!
2025-11-25 11:32:15,701 - INFO - Video thread started with source: Camera
2025-11-25 11:32:15,702 - ERROR - ❌ No camera found!
2025-11-25 11:32:15,702 - INFO - Video thread started with source: Camera
2025-11-25 11:32:15,703 - ERROR - ❌ No camera found!
2025-11-25 11:32:15,713 - INFO - Video thread started with source: Camera
2025-11-25 11:32:15,713 - INFO - Frame 208 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:15,716 - ERROR - ❌ No camera found!
2025-11-25 11:32:15,962 - INFO - Video thread started with source: Camera
2025-11-25 11:32:15,964 - ERROR - ❌ No camera found!
2025-11-25 11:32:15,969 - INFO - Video thread started with source: Camera
2025-11-25 11:32:15,974 - INFO - Video thread started with source: Camera
2025-11-25 11:32:15,976 - ERROR - ❌ No camera found!
2025-11-25 11:32:15,979 - ERROR - ❌ No camera found!
2025-11-25 11:32:15,979 - INFO - Frame 210 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:16,210 - INFO - Video thread started with source: Camera
2025-11-25 11:32:16,210 - INFO - Video thread started with source: Camera
2025-11-25 11:32:16,213 - INFO - Video thread started with source: Camera
2025-11-25 11:32:16,214 - ERROR - ❌ No camera found!
2025-11-25 11:32:16,214 - ERROR - ❌ No camera found!
2025-11-25 11:32:16,214 - ERROR - ❌ No camera found!
2025-11-25 11:32:16,223 - INFO - Frame 212 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:16,462 - INFO - Video thread started with source: Camera
2025-11-25 11:32:16,462 - INFO - Video thread started with source: Camera
2025-11-25 11:32:16,467 - ERROR - ❌ No camera found!
2025-11-25 11:32:16,468 - ERROR - ❌ No camera found!
2025-11-25 11:32:16,474 - INFO - Frame 214 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:16,474 - INFO - Video thread started with source: Camera
2025-11-25 11:32:16,475 - ERROR - ❌ No camera found!
2025-11-25 11:32:16,709 - INFO - Video thread started with source: Camera
2025-11-25 11:32:16,714 - INFO - Video thread started with source: Camera
2025-11-25 11:32:16,714 - ERROR - ❌ No camera found!
2025-11-25 11:32:16,717 - INFO - Video thread started with source: Camera
2025-11-25 11:32:16,718 - INFO - Frame 216 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:16,719 - ERROR - ❌ No camera found!
2025-11-25 11:32:16,719 - ERROR - ❌ No camera found!
2025-11-25 11:32:16,964 - INFO - Video thread started with source: Camera
2025-11-25 11:32:16,968 - INFO - Video thread started with source: Camera
2025-11-25 11:32:16,972 - ERROR - ❌ No camera found!
2025-11-25 11:32:16,974 - ERROR - ❌ No camera found!
2025-11-25 11:32:16,975 - INFO - Video thread started with source: Camera
2025-11-25 11:32:16,975 - INFO - Frame 218 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:16,979 - ERROR - ❌ No camera found!
2025-11-25 11:32:17,206 - INFO - Video thread started with source: Camera
2025-11-25 11:32:17,207 - INFO - Video thread started with source: Camera
2025-11-25 11:32:17,208 - ERROR - ❌ No camera found!
2025-11-25 11:32:17,208 - ERROR - ❌ No camera found!
2025-11-25 11:32:17,213 - INFO - Video thread started with source: Camera
2025-11-25 11:32:17,215 - ERROR - ❌ No camera found!
2025-11-25 11:32:17,219 - INFO - Frame 220 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:17,445 - INFO - Video thread started with source: Camera
2025-11-25 11:32:17,445 - INFO - Video thread started with source: Camera
2025-11-25 11:32:17,448 - ERROR - ❌ No camera found!
2025-11-25 11:32:17,448 - INFO - Video thread started with source: Camera
2025-11-25 11:32:17,448 - ERROR - ❌ No camera found!
2025-11-25 11:32:17,455 - ERROR - ❌ No camera found!
2025-11-25 11:32:17,460 - INFO - Frame 222 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:17,707 - INFO - Frame 224 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:17,707 - INFO - Video thread started with source: Camera
2025-11-25 11:32:17,708 - INFO - Video thread started with source: Camera
2025-11-25 11:32:17,709 - ERROR - ❌ No camera found!
2025-11-25 11:32:17,709 - INFO - Video thread started with source: Camera
2025-11-25 11:32:17,715 - ERROR - ❌ No camera found!
2025-11-25 11:32:17,715 - ERROR - ❌ No camera found!
2025-11-25 11:32:17,959 - INFO - Video thread started with source: Camera
2025-11-25 11:32:17,962 - INFO - Video thread started with source: Camera
2025-11-25 11:32:17,962 - INFO - Video thread started with source: Camera
2025-11-25 11:32:17,964 - ERROR - ❌ No camera found!
2025-11-25 11:32:17,964 - ERROR - ❌ No camera found!
2025-11-25 11:32:17,964 - ERROR - ❌ No camera found!
2025-11-25 11:32:17,965 - INFO - Frame 226 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:18,204 - INFO - Video thread started with source: Camera
2025-11-25 11:32:18,206 - ERROR - ❌ No camera found!
2025-11-25 11:32:18,210 - INFO - Frame 228 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:18,210 - INFO - Video thread started with source: Camera
2025-11-25 11:32:18,213 - INFO - Video thread started with source: Camera
2025-11-25 11:32:18,216 - ERROR - ❌ No camera found!
2025-11-25 11:32:18,217 - ERROR - ❌ No camera found!
2025-11-25 11:32:18,466 - INFO - Video thread started with source: Camera
2025-11-25 11:32:18,466 - ERROR - ❌ No camera found!
2025-11-25 11:32:18,467 - INFO - Video thread started with source: Camera
2025-11-25 11:32:18,476 - INFO - Video thread started with source: Camera
2025-11-25 11:32:18,477 - ERROR - ❌ No camera found!
2025-11-25 11:32:18,479 - ERROR - ❌ No camera found!
2025-11-25 11:32:18,479 - INFO - Frame 230 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:18,734 - INFO - Video thread started with source: Camera
2025-11-25 11:32:18,739 - ERROR - ❌ No camera found!
2025-11-25 11:32:18,739 - INFO - Frame 232 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:18,740 - INFO - Video thread started with source: Camera
2025-11-25 11:32:18,741 - ERROR - ❌ No camera found!
2025-11-25 11:32:18,754 - INFO - Video thread started with source: Camera
2025-11-25 11:32:18,756 - ERROR - ❌ No camera found!
2025-11-25 11:32:18,990 - INFO - Video thread started with source: Camera
2025-11-25 11:32:18,994 - INFO - Video thread started with source: Camera
2025-11-25 11:32:18,994 - INFO - Video thread started with source: Camera
2025-11-25 11:32:18,994 - ERROR - ❌ No camera found!
2025-11-25 11:32:18,995 - ERROR - ❌ No camera found!
2025-11-25 11:32:18,995 - INFO - Frame 234 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:18,996 - ERROR - ❌ No camera found!
2025-11-25 11:32:19,237 - INFO - Video thread started with source: Camera
2025-11-25 11:32:19,237 - INFO - Video thread started with source: Camera
2025-11-25 11:32:19,239 - INFO - Frame 236 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:19,240 - INFO - Video thread started with source: Camera
2025-11-25 11:32:19,241 - ERROR - ❌ No camera found!
2025-11-25 11:32:19,241 - ERROR - ❌ No camera found!
2025-11-25 11:32:19,241 - ERROR - ❌ No camera found!
2025-11-25 11:32:19,480 - INFO - Video thread started with source: Camera
2025-11-25 11:32:19,480 - INFO - Video thread started with source: Camera
2025-11-25 11:32:19,482 - ERROR - ❌ No camera found!
2025-11-25 11:32:19,483 - ERROR - ❌ No camera found!
2025-11-25 11:32:19,490 - INFO - Frame 238 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:19,496 - INFO - Video thread started with source: Camera
2025-11-25 11:32:19,497 - ERROR - ❌ No camera found!
2025-11-25 11:32:19,734 - INFO - Video thread started with source: Camera
2025-11-25 11:32:19,734 - ERROR - ❌ No camera found!
2025-11-25 11:32:19,734 - INFO - Video thread started with source: Camera
2025-11-25 11:32:19,734 - INFO - Video thread started with source: Camera
2025-11-25 11:32:19,735 - INFO - Frame 240 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:19,735 - ERROR - ❌ No camera found!
2025-11-25 11:32:19,736 - ERROR - ❌ No camera found!
2025-11-25 11:32:19,981 - INFO - Video thread started with source: Camera
2025-11-25 11:32:19,986 - ERROR - ❌ No camera found!
2025-11-25 11:32:19,986 - INFO - Video thread started with source: Camera
2025-11-25 11:32:19,990 - ERROR - ❌ No camera found!
2025-11-25 11:32:19,998 - INFO - Video thread started with source: Camera
2025-11-25 11:32:20,000 - INFO - Frame 242 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:20,000 - ERROR - ❌ No camera found!
2025-11-25 11:32:20,252 - INFO - Video thread started with source: Camera
2025-11-25 11:32:20,257 - INFO - Video thread started with source: Camera
2025-11-25 11:32:20,258 - ERROR - ❌ No camera found!
2025-11-25 11:32:20,259 - INFO - Video thread started with source: Camera
2025-11-25 11:32:20,259 - ERROR - ❌ No camera found!
2025-11-25 11:32:20,259 - ERROR - ❌ No camera found!
2025-11-25 11:32:20,271 - INFO - Frame 244 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:20,527 - INFO - Video thread started with source: Camera
2025-11-25 11:32:20,530 - ERROR - ❌ No camera found!
2025-11-25 11:32:20,530 - ERROR - ❌ No camera found!
2025-11-25 11:32:20,530 - INFO - Frame 246 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:20,531 - INFO - Video thread started with source: Camera
2025-11-25 11:32:20,532 - INFO - Video thread started with source: Camera
2025-11-25 11:32:20,538 - ERROR - ❌ No camera found!
2025-11-25 11:32:20,784 - INFO - Video thread started with source: Camera
2025-11-25 11:32:20,784 - INFO - Video thread started with source: Camera
2025-11-25 11:32:20,788 - INFO - Frame 248 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:20,789 - ERROR - ❌ No camera found!
2025-11-25 11:32:20,789 - ERROR - ❌ No camera found!
2025-11-25 11:32:20,789 - INFO - Video thread started with source: Camera
2025-11-25 11:32:20,790 - ERROR - ❌ No camera found!
2025-11-25 11:32:21,023 - INFO - Video thread started with source: Camera
2025-11-25 11:32:21,024 - ERROR - ❌ No camera found!
2025-11-25 11:32:21,029 - ERROR - ❌ No camera found!
2025-11-25 11:32:21,029 - INFO - Video thread started with source: Camera
2025-11-25 11:32:21,030 - INFO - Frame 250 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:21,037 - INFO - Video thread started with source: Camera
2025-11-25 11:32:21,038 - ERROR - ❌ No camera found!
2025-11-25 11:32:21,273 - INFO - Video thread started with source: Camera
2025-11-25 11:32:21,278 - INFO - Video thread started with source: Camera
2025-11-25 11:32:21,278 - INFO - Frame 252 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:21,278 - ERROR - ❌ No camera found!
2025-11-25 11:32:21,278 - ERROR - ❌ No camera found!
2025-11-25 11:32:21,285 - INFO - Video thread started with source: Camera
2025-11-25 11:32:21,294 - ERROR - ❌ No camera found!
2025-11-25 11:32:21,532 - INFO - Frame 254 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:21,534 - INFO - Video thread started with source: Camera
2025-11-25 11:32:21,538 - INFO - Video thread started with source: Camera
2025-11-25 11:32:21,539 - ERROR - ❌ No camera found!
2025-11-25 11:32:21,539 - ERROR - ❌ No camera found!
2025-11-25 11:32:21,539 - INFO - Video thread started with source: Camera
2025-11-25 11:32:21,541 - ERROR - ❌ No camera found!
2025-11-25 11:32:21,578 - INFO - Frame 256 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:21,786 - INFO - Video thread started with source: Camera
2025-11-25 11:32:21,791 - ERROR - ❌ No camera found!
2025-11-25 11:32:21,793 - INFO - Video thread started with source: Camera
2025-11-25 11:32:21,801 - ERROR - ❌ No camera found!
2025-11-25 11:32:21,801 - INFO - Video thread started with source: Camera
2025-11-25 11:32:21,804 - ERROR - ❌ No camera found!
2025-11-25 11:32:21,814 - INFO - Frame 258 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:21,987 - INFO - Video thread started with source: Camera
2025-11-25 11:32:22,043 - INFO - Video thread started with source: Camera
2025-11-25 11:32:22,045 - INFO - Frame 260 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:22,045 - ERROR - ❌ No camera found!
2025-11-25 11:32:22,045 - INFO - Video thread started with source: Camera
2025-11-25 11:32:22,051 - ERROR - ❌ No camera found!
2025-11-25 11:32:22,052 - ERROR - ❌ No camera found!
2025-11-25 11:32:22,283 - ERROR - ❌ No camera found!
2025-11-25 11:32:22,283 - INFO - Video thread started with source: Camera
2025-11-25 11:32:22,291 - INFO - Video thread started with source: Camera
2025-11-25 11:32:22,293 - INFO - Video thread started with source: Camera
2025-11-25 11:32:22,295 - INFO - Frame 262 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:22,297 - ERROR - ❌ No camera found!
2025-11-25 11:32:22,297 - ERROR - ❌ No camera found!
2025-11-25 11:32:22,538 - INFO - Video thread started with source: Camera
2025-11-25 11:32:22,543 - ERROR - ❌ No camera found!
2025-11-25 11:32:22,547 - INFO - Video thread started with source: Camera
2025-11-25 11:32:22,547 - INFO - Video thread started with source: Camera
2025-11-25 11:32:22,550 - ERROR - ❌ No camera found!
2025-11-25 11:32:22,550 - INFO - Frame 264 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:22,552 - ERROR - ❌ No camera found!
2025-11-25 11:32:22,735 - INFO - Video thread started with source: Camera
2025-11-25 11:32:22,798 - INFO - Video thread started with source: Camera
2025-11-25 11:32:22,799 - INFO - Video thread started with source: Camera
2025-11-25 11:32:22,800 - ERROR - ❌ No camera found!
2025-11-25 11:32:22,800 - ERROR - ❌ No camera found!
2025-11-25 11:32:22,800 - ERROR - ❌ No camera found!
2025-11-25 11:32:22,802 - INFO - Frame 266 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:23,048 - INFO - Video thread started with source: Camera
2025-11-25 11:32:23,050 - INFO - Video thread started with source: Camera
2025-11-25 11:32:23,052 - ERROR - ❌ No camera found!
2025-11-25 11:32:23,052 - ERROR - ❌ No camera found!
2025-11-25 11:32:23,059 - INFO - Frame 268 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:23,059 - INFO - Video thread started with source: Camera
2025-11-25 11:32:23,064 - ERROR - ❌ No camera found!
2025-11-25 11:32:23,332 - INFO - Video thread started with source: Camera
2025-11-25 11:32:23,334 - INFO - Video thread started with source: Camera
2025-11-25 11:32:23,336 - INFO - Frame 270 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:23,336 - ERROR - ❌ No camera found!
2025-11-25 11:32:23,339 - ERROR - ❌ No camera found!
2025-11-25 11:32:23,342 - INFO - Video thread started with source: Camera
2025-11-25 11:32:23,342 - ERROR - ❌ No camera found!
2025-11-25 11:32:23,567 - INFO - Video thread started with source: Camera
2025-11-25 11:32:23,574 - INFO - Video thread started with source: Camera
2025-11-25 11:32:23,574 - ERROR - ❌ No camera found!
2025-11-25 11:32:23,579 - INFO - Frame 272 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:23,580 - ERROR - ❌ No camera found!
2025-11-25 11:32:23,580 - INFO - Video thread started with source: Camera
2025-11-25 11:32:23,584 - ERROR - ❌ No camera found!
2025-11-25 11:32:23,828 - INFO - Video thread started with source: Camera
2025-11-25 11:32:23,831 - ERROR - ❌ No camera found!
2025-11-25 11:32:23,831 - INFO - Video thread started with source: Camera
2025-11-25 11:32:23,831 - INFO - Frame 274 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:23,838 - INFO - Video thread started with source: Camera
2025-11-25 11:32:23,838 - ERROR - ❌ No camera found!
2025-11-25 11:32:23,841 - ERROR - ❌ No camera found!
2025-11-25 11:32:24,086 - INFO - Video thread started with source: Camera
2025-11-25 11:32:24,089 - INFO - Video thread started with source: Camera
2025-11-25 11:32:24,092 - ERROR - ❌ No camera found!
2025-11-25 11:32:24,092 - ERROR - ❌ No camera found!
2025-11-25 11:32:24,100 - INFO - Video thread started with source: Camera
2025-11-25 11:32:24,103 - INFO - Frame 276 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:24,103 - ERROR - ❌ No camera found!
2025-11-25 11:32:24,341 - INFO - Video thread started with source: Camera
2025-11-25 11:32:24,345 - ERROR - ❌ No camera found!
2025-11-25 11:32:24,345 - INFO - Video thread started with source: Camera
2025-11-25 11:32:24,347 - ERROR - ❌ No camera found!
2025-11-25 11:32:24,348 - INFO - Frame 278 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:24,348 - INFO - Video thread started with source: Camera
2025-11-25 11:32:24,356 - ERROR - ❌ No camera found!
2025-11-25 11:32:24,606 - INFO - Video thread started with source: Camera
2025-11-25 11:32:24,606 - INFO - Video thread started with source: Camera
2025-11-25 11:32:24,608 - ERROR - ❌ No camera found!
2025-11-25 11:32:24,608 - ERROR - ❌ No camera found!
2025-11-25 11:32:24,616 - INFO - Frame 280 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:24,616 - INFO - Video thread started with source: Camera
2025-11-25 11:32:24,616 - ERROR - ❌ No camera found!
2025-11-25 11:32:24,878 - INFO - Video thread started with source: Camera
2025-11-25 11:32:24,882 - INFO - Video thread started with source: Camera
2025-11-25 11:32:24,886 - ERROR - ❌ No camera found!
2025-11-25 11:32:24,887 - INFO - Video thread started with source: Camera
2025-11-25 11:32:24,888 - ERROR - ❌ No camera found!
2025-11-25 11:32:24,888 - ERROR - ❌ No camera found!
2025-11-25 11:32:24,895 - INFO - Frame 282 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:25,136 - INFO - Video thread started with source: Camera
2025-11-25 11:32:25,136 - INFO - Video thread started with source: Camera
2025-11-25 11:32:25,137 - ERROR - ❌ No camera found!
2025-11-25 11:32:25,139 - ERROR - ❌ No camera found!
2025-11-25 11:32:25,147 - INFO - Frame 284 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:25,148 - INFO - Video thread started with source: Camera
2025-11-25 11:32:25,153 - ERROR - ❌ No camera found!
2025-11-25 11:32:25,393 - INFO - Video thread started with source: Camera
2025-11-25 11:32:25,397 - INFO - Video thread started with source: Camera
2025-11-25 11:32:25,398 - INFO - Video thread started with source: Camera
2025-11-25 11:32:25,398 - ERROR - ❌ No camera found!
2025-11-25 11:32:25,398 - ERROR - ❌ No camera found!
2025-11-25 11:32:25,398 - INFO - Frame 286 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:25,401 - ERROR - ❌ No camera found!
2025-11-25 11:32:25,662 - INFO - Frame 288 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:25,664 - INFO - Video thread started with source: Camera
2025-11-25 11:32:25,666 - INFO - Video thread started with source: Camera
2025-11-25 11:32:25,666 - ERROR - ❌ No camera found!
2025-11-25 11:32:25,667 - ERROR - ❌ No camera found!
2025-11-25 11:32:25,670 - INFO - Video thread started with source: Camera
2025-11-25 11:32:25,670 - ERROR - ❌ No camera found!
2025-11-25 11:32:25,915 - INFO - Video thread started with source: Camera
2025-11-25 11:32:25,915 - INFO - Frame 290 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:25,917 - INFO - Video thread started with source: Camera
2025-11-25 11:32:25,917 - ERROR - ❌ No camera found!
2025-11-25 11:32:25,921 - INFO - Video thread started with source: Camera
2025-11-25 11:32:25,924 - ERROR - ❌ No camera found!
2025-11-25 11:32:25,925 - ERROR - ❌ No camera found!
2025-11-25 11:32:26,188 - INFO - Video thread started with source: Camera
2025-11-25 11:32:26,193 - INFO - Frame 292 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:26,194 - INFO - Video thread started with source: Camera
2025-11-25 11:32:26,194 - ERROR - ❌ No camera found!
2025-11-25 11:32:26,195 - ERROR - ❌ No camera found!
2025-11-25 11:32:26,199 - INFO - Video thread started with source: Camera
2025-11-25 11:32:26,203 - ERROR - ❌ No camera found!
2025-11-25 11:32:26,464 - INFO - Video thread started with source: Camera
2025-11-25 11:32:26,466 - INFO - Video thread started with source: Camera
2025-11-25 11:32:26,466 - INFO - Video thread started with source: Camera
2025-11-25 11:32:26,467 - ERROR - ❌ No camera found!
2025-11-25 11:32:26,467 - ERROR - ❌ No camera found!
2025-11-25 11:32:26,469 - INFO - Frame 294 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:26,475 - ERROR - ❌ No camera found!
2025-11-25 11:32:26,732 - INFO - Video thread started with source: Camera
2025-11-25 11:32:26,735 - INFO - Video thread started with source: Camera
2025-11-25 11:32:26,735 - ERROR - ❌ No camera found!
2025-11-25 11:32:26,737 - ERROR - ❌ No camera found!
2025-11-25 11:32:26,741 - INFO - Video thread started with source: Camera
2025-11-25 11:32:26,741 - INFO - Frame 296 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:26,742 - ERROR - ❌ No camera found!
2025-11-25 11:32:27,080 - INFO - Video thread started with source: Camera
2025-11-25 11:32:27,084 - INFO - Frame 298 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:27,088 - ERROR - ❌ No camera found!
2025-11-25 11:32:27,091 - INFO - Video thread started with source: Camera
2025-11-25 11:32:27,092 - ERROR - ❌ No camera found!
2025-11-25 11:32:27,096 - INFO - Video thread started with source: Camera
2025-11-25 11:32:27,099 - ERROR - ❌ No camera found!
2025-11-25 11:32:27,272 - INFO - Video thread started with source: Camera
2025-11-25 11:32:27,329 - INFO - Video thread started with source: Camera
2025-11-25 11:32:27,329 - INFO - Video thread started with source: Camera
2025-11-25 11:32:27,329 - ERROR - ❌ No camera found!
2025-11-25 11:32:27,331 - ERROR - ❌ No camera found!
2025-11-25 11:32:27,331 - INFO - Frame 300 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:27,337 - ERROR - ❌ No camera found!
2025-11-25 11:32:27,578 - INFO - Video thread started with source: Camera
2025-11-25 11:32:27,578 - INFO - Video thread started with source: Camera
2025-11-25 11:32:27,578 - INFO - Video thread started with source: Camera
2025-11-25 11:32:27,578 - ERROR - ❌ No camera found!
2025-11-25 11:32:27,579 - ERROR - ❌ No camera found!
2025-11-25 11:32:27,579 - INFO - Frame 302 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:27,585 - ERROR - ❌ No camera found!
2025-11-25 11:32:27,847 - INFO - Video thread started with source: Camera
2025-11-25 11:32:27,847 - INFO - Video thread started with source: Camera
2025-11-25 11:32:27,852 - ERROR - ❌ No camera found!
2025-11-25 11:32:27,852 - INFO - Frame 304 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:27,853 - ERROR - ❌ No camera found!
2025-11-25 11:32:27,862 - INFO - Video thread started with source: Camera
2025-11-25 11:32:27,862 - ERROR - ❌ No camera found!
2025-11-25 11:32:28,105 - INFO - Video thread started with source: Camera
2025-11-25 11:32:28,105 - INFO - Video thread started with source: Camera
2025-11-25 11:32:28,106 - ERROR - ❌ No camera found!
2025-11-25 11:32:28,106 - ERROR - ❌ No camera found!
2025-11-25 11:32:28,106 - INFO - Video thread started with source: Camera
2025-11-25 11:32:28,107 - ERROR - ❌ No camera found!
2025-11-25 11:32:28,115 - INFO - Frame 306 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:28,355 - INFO - Video thread started with source: Camera
2025-11-25 11:32:28,356 - INFO - Video thread started with source: Camera
2025-11-25 11:32:28,356 - ERROR - ❌ No camera found!
2025-11-25 11:32:28,356 - ERROR - ❌ No camera found!
2025-11-25 11:32:28,356 - INFO - Video thread started with source: Camera
2025-11-25 11:32:28,357 - ERROR - ❌ No camera found!
2025-11-25 11:32:28,363 - INFO - Frame 308 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:28,608 - INFO - Video thread started with source: Camera
2025-11-25 11:32:28,609 - ERROR - ❌ No camera found!
2025-11-25 11:32:28,611 - INFO - Video thread started with source: Camera
2025-11-25 11:32:28,613 - INFO - Video thread started with source: Camera
2025-11-25 11:32:28,613 - INFO - Frame 310 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:28,613 - ERROR - ❌ No camera found!
2025-11-25 11:32:28,615 - ERROR - ❌ No camera found!
2025-11-25 11:32:28,866 - INFO - Video thread started with source: Camera
2025-11-25 11:32:28,869 - INFO - Frame 312 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:28,870 - ERROR - ❌ No camera found!
2025-11-25 11:32:28,870 - INFO - Video thread started with source: Camera
2025-11-25 11:32:28,870 - ERROR - ❌ No camera found!
2025-11-25 11:32:28,871 - INFO - Video thread started with source: Camera
2025-11-25 11:32:28,874 - ERROR - ❌ No camera found!
2025-11-25 11:32:29,115 - INFO - Video thread started with source: Camera
2025-11-25 11:32:29,117 - INFO - Video thread started with source: Camera
2025-11-25 11:32:29,118 - ERROR - ❌ No camera found!
2025-11-25 11:32:29,118 - ERROR - ❌ No camera found!
2025-11-25 11:32:29,122 - INFO - Frame 314 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:29,127 - INFO - Video thread started with source: Camera
2025-11-25 11:32:29,129 - ERROR - ❌ No camera found!
2025-11-25 11:32:29,419 - INFO - Video thread started with source: Camera
2025-11-25 11:32:29,421 - INFO - Video thread started with source: Camera
2025-11-25 11:32:29,422 - ERROR - ❌ No camera found!
2025-11-25 11:32:29,426 - INFO - Video thread started with source: Camera
2025-11-25 11:32:29,426 - INFO - Frame 316 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:29,427 - ERROR - ❌ No camera found!
2025-11-25 11:32:29,428 - ERROR - ❌ No camera found!
2025-11-25 11:32:29,616 - INFO - Video file uploaded: assets/temp_videos/Screen Recording 2025-11-24 at 6.07.31 PM.mov
2025-11-25 11:32:29,671 - INFO - Video thread started with source: Camera
2025-11-25 11:32:29,673 - INFO - Video thread started with source: assets/temp_videos/Screen Recording 2025-11-24 at 6.07.31 PM.mov
2025-11-25 11:32:29,677 - ERROR - ❌ No camera found!
2025-11-25 11:32:29,678 - INFO - Frame 318 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:29,679 - INFO - Video thread started with source: Camera
2025-11-25 11:32:29,679 - INFO - Video thread started with source: Camera
2025-11-25 11:32:29,680 - ERROR - ❌ No camera found!
2025-11-25 11:32:29,682 - ERROR - ❌ No camera found!
2025-11-25 11:32:29,700 - INFO - ✓ Video file opened: assets/temp_videos/Screen Recording 2025-11-24 at 6.07.31 PM.mov
2025-11-25 11:32:29,952 - INFO - Video thread started with source: Camera
2025-11-25 11:32:29,956 - INFO - Video thread started with source: Camera
2025-11-25 11:32:29,957 - ERROR - ❌ No camera found!
2025-11-25 11:32:29,959 - ERROR - ❌ No camera found!
2025-11-25 11:32:29,961 - INFO - Frame 320 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:29,966 - INFO - Video thread started with source: Camera
2025-11-25 11:32:29,966 - INFO - Frame 0 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:29,969 - ERROR - ❌ No camera found!
2025-11-25 11:32:30,208 - INFO - Video thread started with source: Camera
2025-11-25 11:32:30,221 - ERROR - ❌ No camera found!
2025-11-25 11:32:30,226 - INFO - Frame 322 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:30,226 - INFO - Video thread started with source: Camera
2025-11-25 11:32:30,226 - INFO - Video thread started with source: Camera
2025-11-25 11:32:30,227 - ERROR - ❌ No camera found!
2025-11-25 11:32:30,227 - ERROR - ❌ No camera found!
2025-11-25 11:32:30,449 - INFO - Video thread started with source: Camera
2025-11-25 11:32:30,450 - INFO - Frame 2 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:30,452 - INFO - Frame 324 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:30,452 - INFO - Video thread started with source: Camera
2025-11-25 11:32:30,453 - ERROR - ❌ No camera found!
2025-11-25 11:32:30,454 - ERROR - ❌ No camera found!
2025-11-25 11:32:30,460 - INFO - Video thread started with source: Camera
2025-11-25 11:32:30,461 - ERROR - ❌ No camera found!
2025-11-25 11:32:30,706 - INFO - Video thread started with source: Camera
2025-11-25 11:32:30,707 - INFO - Frame 326 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:30,707 - INFO - Video thread started with source: Camera
2025-11-25 11:32:30,709 - INFO - Video thread started with source: Camera
2025-11-25 11:32:30,721 - ERROR - ❌ No camera found!
2025-11-25 11:32:30,721 - ERROR - ❌ No camera found!
2025-11-25 11:32:30,725 - ERROR - ❌ No camera found!
2025-11-25 11:32:30,961 - INFO - Frame 4 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:30,962 - INFO - Frame 328 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:30,965 - INFO - Video thread started with source: Camera
2025-11-25 11:32:30,967 - INFO - Video thread started with source: Camera
2025-11-25 11:32:30,967 - ERROR - ❌ No camera found!
2025-11-25 11:32:30,970 - INFO - Video thread started with source: Camera
2025-11-25 11:32:30,971 - ERROR - ❌ No camera found!
2025-11-25 11:32:30,971 - ERROR - ❌ No camera found!
2025-11-25 11:32:31,011 - INFO - Frame 330 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:31,193 - INFO - Video thread started with source: Camera
2025-11-25 11:32:31,196 - INFO - Video thread started with source: Camera
2025-11-25 11:32:31,197 - ERROR - ❌ No camera found!
2025-11-25 11:32:31,198 - ERROR - ❌ No camera found!
2025-11-25 11:32:31,200 - INFO - Video thread started with source: Camera
2025-11-25 11:32:31,211 - ERROR - ❌ No camera found!
2025-11-25 11:32:31,215 - INFO - Frame 6 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:31,469 - INFO - Video thread started with source: Camera
2025-11-25 11:32:31,470 - INFO - Video thread started with source: Camera
2025-11-25 11:32:31,473 - ERROR - ❌ No camera found!
2025-11-25 11:32:31,473 - INFO - Video thread started with source: Camera
2025-11-25 11:32:31,474 - ERROR - ❌ No camera found!
2025-11-25 11:32:31,474 - ERROR - ❌ No camera found!
2025-11-25 11:32:31,483 - INFO - Frame 332 | PERCLOS: 0.00 | Yaw: 0.0° | Alerts: 1
2025-11-25 11:32:31,754 - INFO - Video thread started with source: Camera
2025-11-25 11:32:31,755 - ERROR - Error processing frame: CalculatorGraph::Run() failed: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:31,755 - ERROR - Error processing frame: CalculatorGraph::Run() failed: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:31,756 - INFO - Video thread started with source: Camera
2025-11-25 11:32:31,756 - ERROR - ❌ No camera found!
2025-11-25 11:32:31,756 - ERROR - ❌ No camera found!
2025-11-25 11:32:31,762 - INFO - Video thread started with source: Camera
2025-11-25 11:32:31,765 - ERROR - ❌ No camera found!
2025-11-25 11:32:32,018 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:32,020 - INFO - Video thread started with source: Camera
2025-11-25 11:32:32,020 - INFO - Video thread started with source: Camera
2025-11-25 11:32:32,028 - ERROR - ❌ No camera found!
2025-11-25 11:32:32,030 - ERROR - ❌ No camera found!
2025-11-25 11:32:32,031 - INFO - Video thread started with source: Camera
2025-11-25 11:32:32,033 - ERROR - ❌ No camera found!
2025-11-25 11:32:32,130 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:32,131 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:32,259 - INFO - Video thread started with source: Camera
2025-11-25 11:32:32,260 - ERROR - ❌ No camera found!
2025-11-25 11:32:32,264 - INFO - Video thread started with source: Camera
2025-11-25 11:32:32,264 - INFO - Video thread started with source: Camera
2025-11-25 11:32:32,265 - ERROR - ❌ No camera found!
2025-11-25 11:32:32,266 - ERROR - ❌ No camera found!
2025-11-25 11:32:32,297 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:32,462 - INFO - Video thread started with source: Camera
2025-11-25 11:32:32,463 - INFO - Video thread started with source: Camera
2025-11-25 11:32:32,464 - INFO - Video thread started with source: Camera
2025-11-25 11:32:32,467 - ERROR - ❌ No camera found!
2025-11-25 11:32:32,467 - ERROR - ❌ No camera found!
2025-11-25 11:32:32,470 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:32,472 - ERROR - ❌ No camera found!
2025-11-25 11:32:32,481 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:32,720 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:32,721 - INFO - Video thread started with source: Camera
2025-11-25 11:32:32,724 - ERROR - ❌ No camera found!
2025-11-25 11:32:32,726 - INFO - Video thread started with source: Camera
2025-11-25 11:32:32,728 - INFO - Video thread started with source: Camera
2025-11-25 11:32:32,728 - ERROR - ❌ No camera found!
2025-11-25 11:32:32,728 - ERROR - ❌ No camera found!
2025-11-25 11:32:32,965 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:32,967 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:32,973 - INFO - Video thread started with source: Camera
2025-11-25 11:32:32,974 - INFO - Video thread started with source: Camera
2025-11-25 11:32:32,977 - ERROR - ❌ No camera found!
2025-11-25 11:32:32,977 - INFO - Video thread started with source: Camera
2025-11-25 11:32:32,978 - ERROR - ❌ No camera found!
2025-11-25 11:32:32,978 - ERROR - ❌ No camera found!
2025-11-25 11:32:33,010 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:33,189 - INFO - Video thread started with source: Camera
2025-11-25 11:32:33,192 - INFO - Video thread started with source: Camera
2025-11-25 11:32:33,192 - ERROR - ❌ No camera found!
2025-11-25 11:32:33,194 - ERROR - ❌ No camera found!
2025-11-25 11:32:33,197 - INFO - Video thread started with source: Camera
2025-11-25 11:32:33,200 - ERROR - ❌ No camera found!
2025-11-25 11:32:33,212 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:33,404 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:33,476 - INFO - Video thread started with source: Camera
2025-11-25 11:32:33,476 - ERROR - ❌ No camera found!
2025-11-25 11:32:33,480 - INFO - Video thread started with source: Camera
2025-11-25 11:32:33,480 - INFO - Video thread started with source: Camera
2025-11-25 11:32:33,481 - ERROR - ❌ No camera found!
2025-11-25 11:32:33,490 - ERROR - ❌ No camera found!
2025-11-25 11:32:33,498 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:33,728 - INFO - Video thread started with source: Camera
2025-11-25 11:32:33,728 - INFO - Video thread started with source: Camera
2025-11-25 11:32:33,729 - ERROR - ❌ No camera found!
2025-11-25 11:32:33,732 - ERROR - ❌ No camera found!
2025-11-25 11:32:33,735 - INFO - Video thread started with source: Camera
2025-11-25 11:32:33,740 - ERROR - ❌ No camera found!
2025-11-25 11:32:33,749 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:33,750 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:33,997 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:33,999 - INFO - Video thread started with source: Camera
2025-11-25 11:32:34,002 - ERROR - ❌ No camera found!
2025-11-25 11:32:34,002 - INFO - Video thread started with source: Camera
2025-11-25 11:32:34,003 - ERROR - ❌ No camera found!
2025-11-25 11:32:34,006 - INFO - Video thread started with source: Camera
2025-11-25 11:32:34,007 - ERROR - ❌ No camera found!
2025-11-25 11:32:34,212 - INFO - Video thread started with source: Camera
2025-11-25 11:32:34,212 - INFO - Video thread started with source: Camera
2025-11-25 11:32:34,214 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:34,215 - INFO - Video thread started with source: Camera
2025-11-25 11:32:34,215 - ERROR - ❌ No camera found!
2025-11-25 11:32:34,216 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:34,216 - ERROR - ❌ No camera found!
2025-11-25 11:32:34,216 - ERROR - ❌ No camera found!
2025-11-25 11:32:34,461 - INFO - Video thread started with source: Camera
2025-11-25 11:32:34,461 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:34,461 - INFO - Video thread started with source: Camera
2025-11-25 11:32:34,461 - INFO - Video thread started with source: Camera
2025-11-25 11:32:34,461 - ERROR - ❌ No camera found!
2025-11-25 11:32:34,461 - ERROR - ❌ No camera found!
2025-11-25 11:32:34,462 - ERROR - ❌ No camera found!
2025-11-25 11:32:34,734 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:34,740 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:34,740 - INFO - Video thread started with source: Camera
2025-11-25 11:32:34,742 - ERROR - ❌ No camera found!
2025-11-25 11:32:34,742 - INFO - Video thread started with source: Camera
2025-11-25 11:32:34,742 - INFO - Video thread started with source: Camera
2025-11-25 11:32:34,743 - ERROR - ❌ No camera found!
2025-11-25 11:32:34,748 - ERROR - ❌ No camera found!
2025-11-25 11:32:34,788 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:35,023 - INFO - Video thread started with source: Camera
2025-11-25 11:32:35,024 - ERROR - ❌ No camera found!
2025-11-25 11:32:35,025 - INFO - Video thread started with source: Camera
2025-11-25 11:32:35,029 - ERROR - ❌ No camera found!
2025-11-25 11:32:35,038 - INFO - Video thread started with source: Camera
2025-11-25 11:32:35,038 - ERROR - ❌ No camera found!
2025-11-25 11:32:35,056 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:35,059 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:35,241 - INFO - Video thread started with source: Camera
2025-11-25 11:32:35,252 - ERROR - ❌ No camera found!
2025-11-25 11:32:35,255 - INFO - Video thread started with source: Camera
2025-11-25 11:32:35,258 - INFO - Video thread started with source: Camera
2025-11-25 11:32:35,259 - ERROR - ❌ No camera found!
2025-11-25 11:32:35,261 - ERROR - ❌ No camera found!
2025-11-25 11:32:35,272 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:35,458 - INFO - Video thread started with source: Camera
2025-11-25 11:32:35,458 - INFO - Video thread started with source: Camera
2025-11-25 11:32:35,459 - INFO - Video thread started with source: Camera
2025-11-25 11:32:35,459 - ERROR - ❌ No camera found!
2025-11-25 11:32:35,460 - ERROR - ❌ No camera found!
2025-11-25 11:32:35,460 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:35,461 - ERROR - ❌ No camera found!
2025-11-25 11:32:35,467 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:35,717 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:35,724 - INFO - Video thread started with source: Camera
2025-11-25 11:32:35,725 - INFO - Video thread started with source: Camera
2025-11-25 11:32:35,725 - INFO - Video thread started with source: Camera
2025-11-25 11:32:35,725 - ERROR - ❌ No camera found!
2025-11-25 11:32:35,726 - ERROR - ❌ No camera found!
2025-11-25 11:32:35,726 - ERROR - ❌ No camera found!
2025-11-25 11:32:35,767 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:35,949 - INFO - Video thread started with source: Camera
2025-11-25 11:32:35,954 - INFO - Video thread started with source: Camera
2025-11-25 11:32:35,954 - ERROR - ❌ No camera found!
2025-11-25 11:32:35,955 - ERROR - ❌ No camera found!
2025-11-25 11:32:35,961 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:35,961 - INFO - Video thread started with source: Camera
2025-11-25 11:32:35,961 - ERROR - ❌ No camera found!
2025-11-25 11:32:35,988 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:36,166 - INFO - Video thread started with source: Camera
2025-11-25 11:32:36,168 - ERROR - ❌ No camera found!
2025-11-25 11:32:36,172 - INFO - Video thread started with source: Camera
2025-11-25 11:32:36,177 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:36,178 - ERROR - ❌ No camera found!
2025-11-25 11:32:36,180 - INFO - Video thread started with source: Camera
2025-11-25 11:32:36,181 - ERROR - ❌ No camera found!
2025-11-25 11:32:36,190 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:36,440 - INFO - Video thread started with source: Camera
2025-11-25 11:32:36,440 - INFO - Video thread started with source: Camera
2025-11-25 11:32:36,440 - ERROR - ❌ No camera found!
2025-11-25 11:32:36,441 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:36,443 - ERROR - ❌ No camera found!
2025-11-25 11:32:36,447 - INFO - Video thread started with source: Camera
2025-11-25 11:32:36,455 - ERROR - ❌ No camera found!
2025-11-25 11:32:36,477 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:36,689 - INFO - Video thread started with source: Camera
2025-11-25 11:32:36,694 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:36,694 - INFO - Video thread started with source: Camera
2025-11-25 11:32:36,696 - ERROR - ❌ No camera found!
2025-11-25 11:32:36,698 - ERROR - ❌ No camera found!
2025-11-25 11:32:36,698 - INFO - Video thread started with source: Camera
2025-11-25 11:32:36,705 - ERROR - ❌ No camera found!
2025-11-25 11:32:36,954 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:36,959 - INFO - Video thread started with source: Camera
2025-11-25 11:32:36,963 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:36,964 - ERROR - ❌ No camera found!
2025-11-25 11:32:36,964 - ERROR - ❌ No camera found!
2025-11-25 11:32:36,964 - INFO - Video thread started with source: Camera
2025-11-25 11:32:36,968 - INFO - Video thread started with source: Camera
2025-11-25 11:32:36,970 - ERROR - ❌ No camera found!
2025-11-25 11:32:36,995 - INFO - End of video file reached
2025-11-25 11:32:37,067 - INFO - Video capture loop ended
2025-11-25 11:32:37,176 - INFO - Video thread started with source: Camera
2025-11-25 11:32:37,178 - ERROR - ❌ No camera found!
2025-11-25 11:32:37,179 - INFO - Video thread started with source: Camera
2025-11-25 11:32:37,179 - INFO - Video thread started with source: Camera
2025-11-25 11:32:37,179 - ERROR - ❌ No camera found!
2025-11-25 11:32:37,180 - ERROR - ❌ No camera found!
2025-11-25 11:32:37,326 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:37,385 - INFO - Video thread started with source: Camera
2025-11-25 11:32:37,386 - INFO - Video thread started with source: Camera
2025-11-25 11:32:37,386 - ERROR - ❌ No camera found!
2025-11-25 11:32:37,387 - INFO - Video thread started with source: Camera
2025-11-25 11:32:37,387 - ERROR - ❌ No camera found!
2025-11-25 11:32:37,388 - ERROR - ❌ No camera found!
2025-11-25 11:32:37,634 - INFO - Video thread started with source: Camera
2025-11-25 11:32:37,634 - INFO - Video thread started with source: Camera
2025-11-25 11:32:37,637 - ERROR - ❌ No camera found!
2025-11-25 11:32:37,637 - INFO - Video thread started with source: Camera
2025-11-25 11:32:37,637 - ERROR - ❌ No camera found!
2025-11-25 11:32:37,640 - ERROR - ❌ No camera found!
2025-11-25 11:32:37,746 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:37,851 - INFO - Video thread started with source: Camera
2025-11-25 11:32:37,853 - ERROR - ❌ No camera found!
2025-11-25 11:32:37,855 - INFO - Video thread started with source: Camera
2025-11-25 11:32:37,858 - ERROR - ❌ No camera found!
2025-11-25 11:32:37,861 - INFO - Video thread started with source: Camera
2025-11-25 11:32:37,864 - ERROR - ❌ No camera found!
2025-11-25 11:32:38,063 - INFO - Video thread started with source: Camera
2025-11-25 11:32:38,064 - ERROR - ❌ No camera found!
2025-11-25 11:32:38,064 - INFO - Video thread started with source: Camera
2025-11-25 11:32:38,065 - ERROR - ❌ No camera found!
2025-11-25 11:32:38,074 - INFO - Video thread started with source: Camera
2025-11-25 11:32:38,076 - ERROR - ❌ No camera found!
2025-11-25 11:32:38,093 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:38,347 - INFO - Video thread started with source: Camera
2025-11-25 11:32:38,350 - INFO - Video thread started with source: Camera
2025-11-25 11:32:38,350 - INFO - Video thread started with source: Camera
2025-11-25 11:32:38,351 - ERROR - ❌ No camera found!
2025-11-25 11:32:38,351 - ERROR - ❌ No camera found!
2025-11-25 11:32:38,355 - ERROR - ❌ No camera found!
2025-11-25 11:32:38,556 - INFO - Video thread started with source: Camera
2025-11-25 11:32:38,557 - ERROR - ❌ No camera found!
2025-11-25 11:32:38,567 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:38,567 - INFO - Video thread started with source: Camera
2025-11-25 11:32:38,567 - INFO - Video thread started with source: Camera
2025-11-25 11:32:38,567 - ERROR - ❌ No camera found!
2025-11-25 11:32:38,567 - ERROR - ❌ No camera found!
2025-11-25 11:32:38,754 - INFO - Video thread started with source: Camera
2025-11-25 11:32:38,754 - INFO - Video thread started with source: Camera
2025-11-25 11:32:38,754 - ERROR - ❌ No camera found!
2025-11-25 11:32:38,754 - INFO - Video thread started with source: Camera
2025-11-25 11:32:38,760 - ERROR - ❌ No camera found!
2025-11-25 11:32:38,760 - ERROR - ❌ No camera found!
2025-11-25 11:32:38,972 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:39,034 - INFO - Video thread started with source: Camera
2025-11-25 11:32:39,034 - INFO - Video thread started with source: Camera
2025-11-25 11:32:39,036 - ERROR - ❌ No camera found!
2025-11-25 11:32:39,037 - INFO - Video thread started with source: Camera
2025-11-25 11:32:39,040 - ERROR - ❌ No camera found!
2025-11-25 11:32:39,040 - ERROR - ❌ No camera found!
2025-11-25 11:32:39,236 - INFO - Video thread started with source: Camera
2025-11-25 11:32:39,237 - INFO - Video thread started with source: Camera
2025-11-25 11:32:39,238 - ERROR - ❌ No camera found!
2025-11-25 11:32:39,238 - ERROR - ❌ No camera found!
2025-11-25 11:32:39,239 - INFO - Video thread started with source: Camera
2025-11-25 11:32:39,243 - ERROR - ❌ No camera found!
2025-11-25 11:32:39,275 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:39,431 - INFO - Video thread started with source: Camera
2025-11-25 11:32:39,431 - INFO - Video thread started with source: Camera
2025-11-25 11:32:39,437 - ERROR - ❌ No camera found!
2025-11-25 11:32:39,438 - INFO - Video thread started with source: Camera
2025-11-25 11:32:39,438 - ERROR - ❌ No camera found!
2025-11-25 11:32:39,442 - ERROR - ❌ No camera found!
2025-11-25 11:32:39,691 - INFO - Video thread started with source: Camera
2025-11-25 11:32:39,693 - ERROR - ❌ No camera found!
2025-11-25 11:32:39,695 - INFO - Video thread started with source: Camera
2025-11-25 11:32:39,700 - INFO - Video thread started with source: Camera
2025-11-25 11:32:39,700 - ERROR - ❌ No camera found!
2025-11-25 11:32:39,700 - ERROR - ❌ No camera found!
2025-11-25 11:32:39,738 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:39,876 - INFO - Video thread started with source: Camera
2025-11-25 11:32:39,935 - ERROR - ❌ No camera found!
2025-11-25 11:32:39,938 - INFO - Video thread started with source: Camera
2025-11-25 11:32:39,941 - ERROR - ❌ No camera found!
2025-11-25 11:32:39,942 - INFO - Video thread started with source: Camera
2025-11-25 11:32:39,944 - ERROR - ❌ No camera found!
2025-11-25 11:32:40,138 - INFO - Video thread started with source: Camera
2025-11-25 11:32:40,138 - INFO - Video thread started with source: Camera
2025-11-25 11:32:40,140 - INFO - Video thread started with source: Camera
2025-11-25 11:32:40,140 - ERROR - ❌ No camera found!
2025-11-25 11:32:40,141 - ERROR - ❌ No camera found!
2025-11-25 11:32:40,141 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:40,141 - ERROR - ❌ No camera found!
2025-11-25 11:32:40,407 - INFO - Video thread started with source: Camera
2025-11-25 11:32:40,411 - ERROR - ❌ No camera found!
2025-11-25 11:32:40,411 - ERROR - ❌ No camera found!
2025-11-25 11:32:40,412 - INFO - Video thread started with source: Camera
2025-11-25 11:32:40,412 - INFO - Video thread started with source: Camera
2025-11-25 11:32:40,412 - ERROR - ❌ No camera found!
2025-11-25 11:32:40,609 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:40,615 - INFO - Video thread started with source: Camera
2025-11-25 11:32:40,616 - INFO - Video thread started with source: Camera
2025-11-25 11:32:40,617 - ERROR - ❌ No camera found!
2025-11-25 11:32:40,617 - ERROR - ❌ No camera found!
2025-11-25 11:32:40,619 - INFO - Video thread started with source: Camera
2025-11-25 11:32:40,622 - ERROR - ❌ No camera found!
2025-11-25 11:32:40,826 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:40,828 - INFO - Video thread started with source: Camera
2025-11-25 11:32:40,830 - INFO - Video thread started with source: Camera
2025-11-25 11:32:40,830 - ERROR - ❌ No camera found!
2025-11-25 11:32:40,833 - INFO - Video thread started with source: Camera
2025-11-25 11:32:40,834 - ERROR - ❌ No camera found!
2025-11-25 11:32:40,834 - ERROR - ❌ No camera found!
2025-11-25 11:32:41,082 - INFO - Video thread started with source: Camera
2025-11-25 11:32:41,086 - ERROR - ❌ No camera found!
2025-11-25 11:32:41,086 - INFO - Video thread started with source: Camera
2025-11-25 11:32:41,089 - ERROR - ❌ No camera found!
2025-11-25 11:32:41,090 - INFO - Video thread started with source: Camera
2025-11-25 11:32:41,094 - ERROR - ❌ No camera found!
2025-11-25 11:32:41,293 - INFO - Video thread started with source: Camera
2025-11-25 11:32:41,294 - INFO - Video thread started with source: Camera
2025-11-25 11:32:41,305 - ERROR - ❌ No camera found!
2025-11-25 11:32:41,306 - INFO - Video thread started with source: Camera
2025-11-25 11:32:41,306 - ERROR - ❌ No camera found!
2025-11-25 11:32:41,309 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:41,310 - ERROR - ❌ No camera found!
2025-11-25 11:32:41,502 - INFO - Video thread started with source: Camera
2025-11-25 11:32:41,504 - ERROR - ❌ No camera found!
2025-11-25 11:32:41,507 - INFO - Video thread started with source: Camera
2025-11-25 11:32:41,508 - ERROR - ❌ No camera found!
2025-11-25 11:32:41,516 - INFO - Video thread started with source: Camera
2025-11-25 11:32:41,517 - ERROR - ❌ No camera found!
2025-11-25 11:32:41,610 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:41,784 - INFO - Video thread started with source: Camera
2025-11-25 11:32:41,785 - INFO - Video thread started with source: Camera
2025-11-25 11:32:41,785 - ERROR - ❌ No camera found!
2025-11-25 11:32:41,786 - ERROR - ❌ No camera found!
2025-11-25 11:32:41,787 - ERROR - ❌ No camera found!
2025-11-25 11:32:41,787 - INFO - Video thread started with source: Camera
2025-11-25 11:32:41,985 - INFO - Video thread started with source: Camera
2025-11-25 11:32:41,986 - ERROR - ❌ No camera found!
2025-11-25 11:32:41,987 - INFO - Video thread started with source: Camera
2025-11-25 11:32:41,988 - ERROR - ❌ No camera found!
2025-11-25 11:32:41,990 - INFO - Video thread started with source: Camera
2025-11-25 11:32:42,003 - ERROR - ❌ No camera found!
2025-11-25 11:32:42,008 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:42,209 - INFO - Video thread started with source: Camera
2025-11-25 11:32:42,209 - INFO - Video thread started with source: Camera
2025-11-25 11:32:42,210 - INFO - Video thread started with source: Camera
2025-11-25 11:32:42,210 - ERROR - ❌ No camera found!
2025-11-25 11:32:42,211 - ERROR - ❌ No camera found!
2025-11-25 11:32:42,212 - ERROR - ❌ No camera found!
2025-11-25 11:32:42,396 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:42,459 - INFO - Video thread started with source: Camera
2025-11-25 11:32:42,462 - ERROR - ❌ No camera found!
2025-11-25 11:32:42,462 - INFO - Video thread started with source: Camera
2025-11-25 11:32:42,465 - INFO - Video thread started with source: Camera
2025-11-25 11:32:42,466 - ERROR - ❌ No camera found!
2025-11-25 11:32:42,468 - ERROR - ❌ No camera found!
2025-11-25 11:32:42,659 - INFO - Video thread started with source: Camera
2025-11-25 11:32:42,664 - ERROR - ❌ No camera found!
2025-11-25 11:32:42,668 - INFO - Video thread started with source: Camera
2025-11-25 11:32:42,669 - INFO - Video thread started with source: Camera
2025-11-25 11:32:42,670 - ERROR - ❌ No camera found!
2025-11-25 11:32:42,670 - ERROR - ❌ No camera found!
2025-11-25 11:32:42,676 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:42,885 - INFO - Video thread started with source: Camera
2025-11-25 11:32:42,885 - INFO - Video thread started with source: Camera
2025-11-25 11:32:42,886 - INFO - Video thread started with source: Camera
2025-11-25 11:32:42,886 - ERROR - ❌ No camera found!
2025-11-25 11:32:42,886 - ERROR - ❌ No camera found!
2025-11-25 11:32:42,888 - ERROR - ❌ No camera found!
2025-11-25 11:32:43,139 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:43,142 - INFO - Video thread started with source: Camera
2025-11-25 11:32:43,142 - ERROR - ❌ No camera found!
2025-11-25 11:32:43,143 - INFO - Video thread started with source: Camera
2025-11-25 11:32:43,143 - ERROR - ❌ No camera found!
2025-11-25 11:32:43,148 - INFO - Video thread started with source: Camera
2025-11-25 11:32:43,152 - ERROR - ❌ No camera found!
2025-11-25 11:32:43,353 - INFO - Video thread started with source: Camera
2025-11-25 11:32:43,354 - INFO - Video thread started with source: Camera
2025-11-25 11:32:43,354 - ERROR - ❌ No camera found!
2025-11-25 11:32:43,357 - ERROR - ❌ No camera found!
2025-11-25 11:32:43,357 - INFO - Video thread started with source: Camera
2025-11-25 11:32:43,359 - ERROR - ❌ No camera found!
2025-11-25 11:32:43,452 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:43,554 - INFO - Video thread started with source: Camera
2025-11-25 11:32:43,556 - INFO - Video thread started with source: Camera
2025-11-25 11:32:43,556 - ERROR - ❌ No camera found!
2025-11-25 11:32:43,556 - ERROR - ❌ No camera found!
2025-11-25 11:32:43,556 - INFO - Video thread started with source: Camera
2025-11-25 11:32:43,557 - ERROR - ❌ No camera found!
2025-11-25 11:32:43,807 - INFO - Video thread started with source: Camera
2025-11-25 11:32:43,807 - INFO - Video thread started with source: Camera
2025-11-25 11:32:43,808 - INFO - Video thread started with source: Camera
2025-11-25 11:32:43,808 - ERROR - ❌ No camera found!
2025-11-25 11:32:43,808 - ERROR - ❌ No camera found!
2025-11-25 11:32:43,809 - ERROR - ❌ No camera found!
2025-11-25 11:32:43,912 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:44,014 - INFO - Video thread started with source: Camera
2025-11-25 11:32:44,014 - INFO - Video thread started with source: Camera
2025-11-25 11:32:44,016 - ERROR - ❌ No camera found!
2025-11-25 11:32:44,016 - INFO - Video thread started with source: Camera
2025-11-25 11:32:44,016 - ERROR - ❌ No camera found!
2025-11-25 11:32:44,017 - ERROR - ❌ No camera found!
2025-11-25 11:32:44,220 - INFO - Video thread started with source: Camera
2025-11-25 11:32:44,220 - INFO - Video thread started with source: Camera
2025-11-25 11:32:44,221 - ERROR - ❌ No camera found!
2025-11-25 11:32:44,223 - ERROR - ❌ No camera found!
2025-11-25 11:32:44,224 - INFO - Video thread started with source: Camera
2025-11-25 11:32:44,236 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:44,238 - ERROR - ❌ No camera found!
2025-11-25 11:32:44,471 - INFO - Video thread started with source: Camera
2025-11-25 11:32:44,475 - ERROR - ❌ No camera found!
2025-11-25 11:32:44,476 - INFO - Video thread started with source: Camera
2025-11-25 11:32:44,478 - INFO - Video thread started with source: Camera
2025-11-25 11:32:44,478 - ERROR - ❌ No camera found!
2025-11-25 11:32:44,479 - ERROR - ❌ No camera found!
2025-11-25 11:32:44,675 - INFO - Video thread started with source: Camera
2025-11-25 11:32:44,675 - INFO - Video thread started with source: Camera
2025-11-25 11:32:44,679 - INFO - Video thread started with source: Camera
2025-11-25 11:32:44,679 - ERROR - ❌ No camera found!
2025-11-25 11:32:44,679 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:44,681 - ERROR - ❌ No camera found!
2025-11-25 11:32:44,684 - ERROR - ❌ No camera found!
2025-11-25 11:32:44,877 - INFO - Video thread started with source: Camera
2025-11-25 11:32:44,877 - INFO - Video thread started with source: Camera
2025-11-25 11:32:44,878 - ERROR - ❌ No camera found!
2025-11-25 11:32:44,878 - INFO - Video thread started with source: Camera
2025-11-25 11:32:44,879 - ERROR - ❌ No camera found!
2025-11-25 11:32:44,879 - ERROR - ❌ No camera found!
2025-11-25 11:32:45,142 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:45,145 - INFO - Video thread started with source: Camera
2025-11-25 11:32:45,151 - INFO - Video thread started with source: Camera
2025-11-25 11:32:45,151 - INFO - Video thread started with source: Camera
2025-11-25 11:32:45,152 - ERROR - ❌ No camera found!
2025-11-25 11:32:45,153 - ERROR - ❌ No camera found!
2025-11-25 11:32:45,154 - ERROR - ❌ No camera found!
2025-11-25 11:32:45,352 - INFO - Video thread started with source: Camera
2025-11-25 11:32:45,353 - INFO - Video thread started with source: Camera
2025-11-25 11:32:45,353 - INFO - Video thread started with source: Camera
2025-11-25 11:32:45,354 - ERROR - ❌ No camera found!
2025-11-25 11:32:45,354 - ERROR - ❌ No camera found!
2025-11-25 11:32:45,356 - ERROR - ❌ No camera found!
2025-11-25 11:32:45,559 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:45,566 - INFO - Video thread started with source: Camera
2025-11-25 11:32:45,568 - INFO - Video thread started with source: Camera
2025-11-25 11:32:45,569 - ERROR - ❌ No camera found!
2025-11-25 11:32:45,569 - INFO - Video thread started with source: Camera
2025-11-25 11:32:45,570 - ERROR - ❌ No camera found!
2025-11-25 11:32:45,571 - ERROR - ❌ No camera found!
2025-11-25 11:32:45,816 - INFO - Video thread started with source: Camera
2025-11-25 11:32:45,816 - INFO - Video thread started with source: Camera
2025-11-25 11:32:45,821 - ERROR - ❌ No camera found!
2025-11-25 11:32:45,822 - ERROR - ❌ No camera found!
2025-11-25 11:32:45,823 - INFO - Video thread started with source: Camera
2025-11-25 11:32:45,823 - ERROR - ❌ No camera found!
2025-11-25 11:32:45,981 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:45,991 - INFO - Video thread started with source: Camera
2025-11-25 11:32:46,050 - INFO - Video thread started with source: Camera
2025-11-25 11:32:46,053 - ERROR - ❌ No camera found!
2025-11-25 11:32:46,053 - ERROR - ❌ No camera found!
2025-11-25 11:32:46,060 - INFO - Video thread started with source: Camera
2025-11-25 11:32:46,062 - ERROR - ❌ No camera found!
2025-11-25 11:32:46,248 - INFO - Video thread started with source: Camera
2025-11-25 11:32:46,249 - INFO - Video thread started with source: Camera
2025-11-25 11:32:46,250 - INFO - Video thread started with source: Camera
2025-11-25 11:32:46,250 - ERROR - ❌ No camera found!
2025-11-25 11:32:46,250 - ERROR - ❌ No camera found!
2025-11-25 11:32:46,251 - ERROR - ❌ No camera found!
2025-11-25 11:32:46,502 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:46,508 - INFO - Video thread started with source: Camera
2025-11-25 11:32:46,508 - INFO - Video thread started with source: Camera
2025-11-25 11:32:46,508 - ERROR - ❌ No camera found!
2025-11-25 11:32:46,509 - INFO - Video thread started with source: Camera
2025-11-25 11:32:46,509 - ERROR - ❌ No camera found!
2025-11-25 11:32:46,515 - ERROR - ❌ No camera found!
2025-11-25 11:32:46,729 - INFO - Video thread started with source: Camera
2025-11-25 11:32:46,729 - INFO - Video thread started with source: Camera
2025-11-25 11:32:46,729 - INFO - Video thread started with source: Camera
2025-11-25 11:32:46,730 - ERROR - ❌ No camera found!
2025-11-25 11:32:46,730 - ERROR - ❌ No camera found!
2025-11-25 11:32:46,731 - ERROR - ❌ No camera found!
2025-11-25 11:32:46,943 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:46,948 - INFO - Video thread started with source: Camera
2025-11-25 11:32:46,948 - INFO - Video thread started with source: Camera
2025-11-25 11:32:46,949 - ERROR - ❌ No camera found!
2025-11-25 11:32:46,949 - ERROR - ❌ No camera found!
2025-11-25 11:32:46,951 - INFO - Video thread started with source: Camera
2025-11-25 11:32:46,956 - ERROR - ❌ No camera found!
2025-11-25 11:32:47,213 - INFO - Video thread started with source: Camera
2025-11-25 11:32:47,227 - ERROR - ❌ No camera found!
2025-11-25 11:32:47,227 - INFO - Video thread started with source: Camera
2025-11-25 11:32:47,227 - ERROR - ❌ No camera found!
2025-11-25 11:32:47,227 - INFO - Video thread started with source: Camera
2025-11-25 11:32:47,228 - ERROR - ❌ No camera found!
2025-11-25 11:32:47,446 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:47,451 - INFO - Video thread started with source: Camera
2025-11-25 11:32:47,453 - ERROR - ❌ No camera found!
2025-11-25 11:32:47,453 - INFO - Video thread started with source: Camera
2025-11-25 11:32:47,454 - ERROR - ❌ No camera found!
2025-11-25 11:32:47,455 - INFO - Video thread started with source: Camera
2025-11-25 11:32:47,459 - ERROR - ❌ No camera found!
2025-11-25 11:32:47,647 - INFO - Video thread started with source: Camera
2025-11-25 11:32:47,651 - INFO - Video thread started with source: Camera
2025-11-25 11:32:47,659 - ERROR - ❌ No camera found!
2025-11-25 11:32:47,659 - ERROR - ❌ No camera found!
2025-11-25 11:32:47,659 - INFO - Video thread started with source: Camera
2025-11-25 11:32:47,660 - ERROR - ❌ No camera found!
2025-11-25 11:32:47,869 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:47,940 - INFO - Video thread started with source: Camera
2025-11-25 11:32:47,940 - INFO - Video thread started with source: Camera
2025-11-25 11:32:47,943 - ERROR - ❌ No camera found!
2025-11-25 11:32:47,944 - ERROR - ❌ No camera found!
2025-11-25 11:32:47,944 - INFO - Video thread started with source: Camera
2025-11-25 11:32:47,948 - ERROR - ❌ No camera found!
2025-11-25 11:32:48,136 - INFO - Video thread started with source: Camera
2025-11-25 11:32:48,137 - ERROR - ❌ No camera found!
2025-11-25 11:32:48,144 - INFO - Video thread started with source: Camera
2025-11-25 11:32:48,145 - INFO - Video thread started with source: Camera
2025-11-25 11:32:48,146 - ERROR - ❌ No camera found!
2025-11-25 11:32:48,146 - ERROR - ❌ No camera found!
2025-11-25 11:32:48,307 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:48,374 - INFO - Video thread started with source: Camera
2025-11-25 11:32:48,375 - INFO - Video thread started with source: Camera
2025-11-25 11:32:48,376 - INFO - Video thread started with source: Camera
2025-11-25 11:32:48,376 - ERROR - ❌ No camera found!
2025-11-25 11:32:48,376 - ERROR - ❌ No camera found!
2025-11-25 11:32:48,377 - ERROR - ❌ No camera found!
2025-11-25 11:32:48,389 - ERROR - Task exception was never retrieved
future: <Task finished name='Task-41159' coro=<WebSocketProtocol13.write_message.<locals>.wrapper() done, defined at /home/tech4biz/work/tools/Driver_DSMS_ADAS/venv/lib/python3.12/site-packages/tornado/websocket.py:1111> exception=WebSocketClosedError()>
Traceback (most recent call last):
  File "/home/tech4biz/work/tools/Driver_DSMS_ADAS/venv/lib/python3.12/site-packages/tornado/websocket.py", line 1113, in wrapper
    await fut
tornado.iostream.StreamClosedError: Stream is closed

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/tech4biz/work/tools/Driver_DSMS_ADAS/venv/lib/python3.12/site-packages/tornado/websocket.py", line 1115, in wrapper
    raise WebSocketClosedError()
tornado.websocket.WebSocketClosedError
2025-11-25 11:32:48,540 - INFO - Video thread started with source: Camera
2025-11-25 11:32:48,542 - ERROR - ❌ No camera found!
2025-11-25 11:32:48,542 - INFO - Video thread started with source: Camera
2025-11-25 11:32:48,544 - ERROR - ❌ No camera found!
2025-11-25 11:32:48,548 - INFO - Video thread started with source: Camera
2025-11-25 11:32:48,549 - ERROR - ❌ No camera found!
2025-11-25 11:32:48,707 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:48,775 - INFO - Video thread started with source: Camera
2025-11-25 11:32:48,777 - INFO - Video thread started with source: Camera
2025-11-25 11:32:48,778 - ERROR - ❌ No camera found!
2025-11-25 11:32:48,779 - INFO - Video thread started with source: Camera
2025-11-25 11:32:48,779 - ERROR - ❌ No camera found!
2025-11-25 11:32:48,779 - ERROR - ❌ No camera found!
2025-11-25 11:32:48,806 - INFO - Video thread started with source: Camera
2025-11-25 11:32:48,807 - ERROR - ❌ No camera found!
2025-11-25 11:32:49,049 - INFO - Video thread started with source: Camera
2025-11-25 11:32:49,053 - INFO - Video thread started with source: Camera
2025-11-25 11:32:49,053 - INFO - Video thread started with source: Camera
2025-11-25 11:32:49,053 - ERROR - ❌ No camera found!
2025-11-25 11:32:49,056 - ERROR - ❌ No camera found!
2025-11-25 11:32:49,058 - INFO - Video thread started with source: Camera
2025-11-25 11:32:49,059 - ERROR - ❌ No camera found!
2025-11-25 11:32:49,059 - ERROR - ❌ No camera found!
2025-11-25 11:32:49,063 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:49,278 - INFO - Video thread started with source: Camera
2025-11-25 11:32:49,281 - ERROR - ❌ No camera found!
2025-11-25 11:32:49,281 - INFO - Video thread started with source: Camera
2025-11-25 11:32:49,282 - INFO - Video thread started with source: Camera
2025-11-25 11:32:49,283 - ERROR - ❌ No camera found!
2025-11-25 11:32:49,283 - INFO - Video thread started with source: Camera
2025-11-25 11:32:49,284 - ERROR - ❌ No camera found!
2025-11-25 11:32:49,284 - ERROR - ❌ No camera found!
2025-11-25 11:32:49,531 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:49,537 - INFO - Video thread started with source: Camera
2025-11-25 11:32:49,540 - INFO - Video thread started with source: Camera
2025-11-25 11:32:49,540 - ERROR - ❌ No camera found!
2025-11-25 11:32:49,541 - INFO - Video thread started with source: Camera
2025-11-25 11:32:49,541 - ERROR - ❌ No camera found!
2025-11-25 11:32:49,541 - INFO - Video thread started with source: Camera
2025-11-25 11:32:49,542 - ERROR - ❌ No camera found!
2025-11-25 11:32:49,542 - ERROR - ❌ No camera found!
2025-11-25 11:32:49,801 - INFO - Video thread started with source: Camera
2025-11-25 11:32:49,803 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:49,804 - INFO - Video thread started with source: Camera
2025-11-25 11:32:49,804 - ERROR - ❌ No camera found!
2025-11-25 11:32:49,805 - ERROR - ❌ No camera found!
2025-11-25 11:32:49,809 - INFO - Video thread started with source: Camera
2025-11-25 11:32:49,811 - ERROR - ❌ No camera found!
2025-11-25 11:32:49,812 - INFO - Video thread started with source: Camera
2025-11-25 11:32:49,815 - ERROR - ❌ No camera found!
2025-11-25 11:32:50,054 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:50,054 - INFO - Video thread started with source: Camera
2025-11-25 11:32:50,054 - INFO - Video thread started with source: Camera
2025-11-25 11:32:50,055 - INFO - Video thread started with source: Camera
2025-11-25 11:32:50,055 - INFO - Video thread started with source: Camera
2025-11-25 11:32:50,055 - ERROR - ❌ No camera found!
2025-11-25 11:32:50,056 - ERROR - ❌ No camera found!
2025-11-25 11:32:50,057 - ERROR - ❌ No camera found!
2025-11-25 11:32:50,058 - ERROR - ❌ No camera found!
2025-11-25 11:32:50,296 - INFO - Video thread started with source: Camera
2025-11-25 11:32:50,296 - INFO - Video thread started with source: Camera
2025-11-25 11:32:50,296 - INFO - Video thread started with source: Camera
2025-11-25 11:32:50,296 - ERROR - ❌ No camera found!
2025-11-25 11:32:50,296 - INFO - Video thread started with source: Camera
2025-11-25 11:32:50,297 - ERROR - ❌ No camera found!
2025-11-25 11:32:50,298 - ERROR - ❌ No camera found!
2025-11-25 11:32:50,301 - ERROR - ❌ No camera found!
2025-11-25 11:32:50,337 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:50,591 - INFO - Video thread started with source: Camera
2025-11-25 11:32:50,593 - ERROR - ❌ No camera found!
2025-11-25 11:32:50,594 - INFO - Video thread started with source: Camera
2025-11-25 11:32:50,596 - INFO - Video thread started with source: Camera
2025-11-25 11:32:50,597 - ERROR - ❌ No camera found!
2025-11-25 11:32:50,597 - ERROR - ❌ No camera found!
2025-11-25 11:32:50,604 - INFO - Video thread started with source: Camera
2025-11-25 11:32:50,607 - ERROR - ❌ No camera found!
2025-11-25 11:32:50,867 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:50,875 - INFO - Video thread started with source: Camera
2025-11-25 11:32:50,878 - INFO - Video thread started with source: Camera
2025-11-25 11:32:50,878 - ERROR - ❌ No camera found!
2025-11-25 11:32:50,878 - INFO - Video thread started with source: Camera
2025-11-25 11:32:50,879 - INFO - Video thread started with source: Camera
2025-11-25 11:32:50,879 - ERROR - ❌ No camera found!
2025-11-25 11:32:50,879 - ERROR - ❌ No camera found!
2025-11-25 11:32:50,879 - ERROR - ❌ No camera found!
2025-11-25 11:32:51,117 - INFO - Video thread started with source: Camera
2025-11-25 11:32:51,122 - INFO - Video thread started with source: Camera
2025-11-25 11:32:51,127 - ERROR - ❌ No camera found!
2025-11-25 11:32:51,131 - INFO - Video thread started with source: Camera
2025-11-25 11:32:51,134 - ERROR - ❌ No camera found!
2025-11-25 11:32:51,135 - ERROR - ❌ No camera found!
2025-11-25 11:32:51,137 - INFO - Video thread started with source: Camera
2025-11-25 11:32:51,141 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:51,142 - ERROR - ❌ No camera found!
2025-11-25 11:32:51,317 - INFO - Video thread started with source: Camera
2025-11-25 11:32:51,376 - INFO - Video thread started with source: Camera
2025-11-25 11:32:51,378 - ERROR - ❌ No camera found!
2025-11-25 11:32:51,379 - INFO - Video thread started with source: Camera
2025-11-25 11:32:51,382 - ERROR - ❌ No camera found!
2025-11-25 11:32:51,382 - ERROR - ❌ No camera found!
2025-11-25 11:32:51,385 - INFO - Video thread started with source: Camera
2025-11-25 11:32:51,391 - ERROR - ❌ No camera found!
2025-11-25 11:32:51,521 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:51,623 - INFO - Video thread started with source: Camera
2025-11-25 11:32:51,623 - INFO - Video thread started with source: Camera
2025-11-25 11:32:51,626 - INFO - Video thread started with source: Camera
2025-11-25 11:32:51,627 - ERROR - ❌ No camera found!
2025-11-25 11:32:51,627 - ERROR - ❌ No camera found!
2025-11-25 11:32:51,627 - INFO - Video thread started with source: Camera
2025-11-25 11:32:51,627 - ERROR - ❌ No camera found!
2025-11-25 11:32:51,628 - ERROR - ❌ No camera found!
2025-11-25 11:32:51,875 - INFO - Video thread started with source: Camera
2025-11-25 11:32:51,879 - ERROR - ❌ No camera found!
2025-11-25 11:32:51,879 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:51,880 - INFO - Video thread started with source: Camera
2025-11-25 11:32:51,880 - INFO - Video thread started with source: Camera
2025-11-25 11:32:51,880 - INFO - Video thread started with source: Camera
2025-11-25 11:32:51,880 - ERROR - ❌ No camera found!
2025-11-25 11:32:51,880 - ERROR - ❌ No camera found!
2025-11-25 11:32:51,880 - ERROR - ❌ No camera found!
2025-11-25 11:32:52,111 - INFO - Video thread started with source: Camera
2025-11-25 11:32:52,115 - INFO - Video thread started with source: Camera
2025-11-25 11:32:52,115 - INFO - Video thread started with source: Camera
2025-11-25 11:32:52,115 - ERROR - ❌ No camera found!
2025-11-25 11:32:52,116 - ERROR - ❌ No camera found!
2025-11-25 11:32:52,117 - ERROR - ❌ No camera found!
2025-11-25 11:32:52,118 - INFO - Video thread started with source: Camera
2025-11-25 11:32:52,118 - ERROR - ❌ No camera found!
2025-11-25 11:32:52,371 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:52,374 - INFO - Video thread started with source: Camera
2025-11-25 11:32:52,377 - ERROR - ❌ No camera found!
2025-11-25 11:32:52,380 - INFO - Video thread started with source: Camera
2025-11-25 11:32:52,381 - ERROR - ❌ No camera found!
2025-11-25 11:32:52,381 - INFO - Video thread started with source: Camera
2025-11-25 11:32:52,383 - ERROR - ❌ No camera found!
2025-11-25 11:32:52,389 - INFO - Video thread started with source: Camera
2025-11-25 11:32:52,389 - ERROR - ❌ No camera found!
2025-11-25 11:32:52,625 - INFO - Video thread started with source: Camera
2025-11-25 11:32:52,632 - ERROR - ❌ No camera found!
2025-11-25 11:32:52,633 - INFO - Video thread started with source: Camera
2025-11-25 11:32:52,634 - INFO - Video thread started with source: Camera
2025-11-25 11:32:52,635 - ERROR - ❌ No camera found!
2025-11-25 11:32:52,635 - INFO - Video thread started with source: Camera
2025-11-25 11:32:52,638 - ERROR - ❌ No camera found!
2025-11-25 11:32:52,639 - ERROR - ❌ No camera found!
2025-11-25 11:32:52,651 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:52,884 - INFO - Video thread started with source: Camera
2025-11-25 11:32:52,889 - ERROR - ❌ No camera found!
2025-11-25 11:32:52,889 - INFO - Video thread started with source: Camera
2025-11-25 11:32:52,890 - INFO - Video thread started with source: Camera
2025-11-25 11:32:52,891 - INFO - Video thread started with source: Camera
2025-11-25 11:32:52,894 - ERROR - ❌ No camera found!
2025-11-25 11:32:52,895 - ERROR - ❌ No camera found!
2025-11-25 11:32:52,895 - ERROR - ❌ No camera found!
2025-11-25 11:32:53,081 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:53,135 - INFO - Video thread started with source: Camera
2025-11-25 11:32:53,138 - INFO - Video thread started with source: Camera
2025-11-25 11:32:53,138 - INFO - Video thread started with source: Camera
2025-11-25 11:32:53,139 - INFO - Video thread started with source: Camera
2025-11-25 11:32:53,139 - ERROR - ❌ No camera found!
2025-11-25 11:32:53,139 - ERROR - ❌ No camera found!
2025-11-25 11:32:53,139 - ERROR - ❌ No camera found!
2025-11-25 11:32:53,140 - ERROR - ❌ No camera found!
2025-11-25 11:32:53,334 - INFO - Video thread started with source: Camera
2025-11-25 11:32:53,392 - ERROR - ❌ No camera found!
2025-11-25 11:32:53,396 - INFO - Video thread started with source: Camera
2025-11-25 11:32:53,400 - ERROR - ❌ No camera found!
2025-11-25 11:32:53,405 - ERROR - ❌ No camera found!
2025-11-25 11:32:53,405 - INFO - Video thread started with source: Camera
2025-11-25 11:32:53,406 - INFO - Video thread started with source: Camera
2025-11-25 11:32:53,411 - ERROR - ❌ No camera found!
2025-11-25 11:32:53,413 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:53,633 - INFO - Video thread started with source: Camera
2025-11-25 11:32:53,637 - INFO - Video thread started with source: Camera
2025-11-25 11:32:53,638 - ERROR - ❌ No camera found!
2025-11-25 11:32:53,638 - INFO - Video thread started with source: Camera
2025-11-25 11:32:53,639 - ERROR - ❌ No camera found!
2025-11-25 11:32:53,639 - INFO - Video thread started with source: Camera
2025-11-25 11:32:53,639 - ERROR - ❌ No camera found!
2025-11-25 11:32:53,640 - ERROR - ❌ No camera found!
2025-11-25 11:32:53,887 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:53,887 - INFO - Video thread started with source: Camera
2025-11-25 11:32:53,892 - ERROR - ❌ No camera found!
2025-11-25 11:32:53,892 - INFO - Video thread started with source: Camera
2025-11-25 11:32:53,894 - ERROR - ❌ No camera found!
2025-11-25 11:32:53,895 - INFO - Video thread started with source: Camera
2025-11-25 11:32:53,899 - INFO - Video thread started with source: Camera
2025-11-25 11:32:53,899 - ERROR - ❌ No camera found!
2025-11-25 11:32:53,899 - ERROR - ❌ No camera found!
2025-11-25 11:32:54,157 - INFO - Video thread started with source: Camera
2025-11-25 11:32:54,159 - ERROR - ❌ No camera found!
2025-11-25 11:32:54,159 - INFO - Video thread started with source: Camera
2025-11-25 11:32:54,161 - ERROR - ❌ No camera found!
2025-11-25 11:32:54,161 - INFO - Video thread started with source: Camera
2025-11-25 11:32:54,165 - ERROR - ❌ No camera found!
2025-11-25 11:32:54,170 - INFO - Video thread started with source: Camera
2025-11-25 11:32:54,172 - ERROR - ❌ No camera found!
2025-11-25 11:32:54,304 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:54,411 - INFO - Video thread started with source: Camera
2025-11-25 11:32:54,415 - ERROR - ❌ No camera found!
2025-11-25 11:32:54,416 - INFO - Video thread started with source: Camera
2025-11-25 11:32:54,418 - INFO - Video thread started with source: Camera
2025-11-25 11:32:54,420 - ERROR - ❌ No camera found!
2025-11-25 11:32:54,420 - ERROR - ❌ No camera found!
2025-11-25 11:32:54,423 - INFO - Video thread started with source: Camera
2025-11-25 11:32:54,424 - ERROR - ❌ No camera found!
2025-11-25 11:32:54,690 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:54,691 - ERROR - ❌ No camera found!
2025-11-25 11:32:54,691 - INFO - Video thread started with source: Camera
2025-11-25 11:32:54,693 - INFO - Video thread started with source: Camera
2025-11-25 11:32:54,696 - INFO - Video thread started with source: Camera
2025-11-25 11:32:54,697 - ERROR - ❌ No camera found!
2025-11-25 11:32:54,698 - INFO - Video thread started with source: Camera
2025-11-25 11:32:54,698 - ERROR - ❌ No camera found!
2025-11-25 11:32:54,699 - ERROR - ❌ No camera found!
2025-11-25 11:32:54,887 - INFO - Video thread started with source: Camera
2025-11-25 11:32:54,887 - INFO - Video thread started with source: Camera
2025-11-25 11:32:54,888 - ERROR - ❌ No camera found!
2025-11-25 11:32:54,889 - INFO - Video thread started with source: Camera
2025-11-25 11:32:54,943 - ERROR - ❌ No camera found!
2025-11-25 11:32:54,944 - ERROR - ❌ No camera found!
2025-11-25 11:32:54,946 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:54,950 - INFO - Video thread started with source: Camera
2025-11-25 11:32:54,954 - ERROR - ❌ No camera found!
2025-11-25 11:32:55,183 - ERROR - ❌ No camera found!
2025-11-25 11:32:55,184 - INFO - Video thread started with source: Camera
2025-11-25 11:32:55,191 - INFO - Video thread started with source: Camera
2025-11-25 11:32:55,191 - INFO - Video thread started with source: Camera
2025-11-25 11:32:55,191 - ERROR - ❌ No camera found!
2025-11-25 11:32:55,191 - INFO - Video thread started with source: Camera
2025-11-25 11:32:55,196 - ERROR - ❌ No camera found!
2025-11-25 11:32:55,197 - ERROR - ❌ No camera found!
2025-11-25 11:32:55,418 - INFO - Video thread started with source: Camera
2025-11-25 11:32:55,421 - INFO - Video thread started with source: Camera
2025-11-25 11:32:55,421 - INFO - Video thread started with source: Camera
2025-11-25 11:32:55,422 - ERROR - ❌ No camera found!
2025-11-25 11:32:55,423 - ERROR - ❌ No camera found!
2025-11-25 11:32:55,426 - ERROR - ❌ No camera found!
2025-11-25 11:32:55,428 - INFO - Video thread started with source: Camera
2025-11-25 11:32:55,432 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:55,433 - ERROR - ❌ No camera found!
2025-11-25 11:32:55,671 - INFO - Video thread started with source: Camera
2025-11-25 11:32:55,677 - INFO - Video thread started with source: Camera
2025-11-25 11:32:55,679 - INFO - Video thread started with source: Camera
2025-11-25 11:32:55,680 - ERROR - ❌ No camera found!
2025-11-25 11:32:55,681 - ERROR - ❌ No camera found!
2025-11-25 11:32:55,683 - INFO - Video thread started with source: Camera
2025-11-25 11:32:55,683 - ERROR - ❌ No camera found!
2025-11-25 11:32:55,686 - ERROR - ❌ No camera found!
2025-11-25 11:32:55,924 - INFO - Video thread started with source: Camera
2025-11-25 11:32:55,924 - INFO - Video thread started with source: Camera
2025-11-25 11:32:55,927 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:55,927 - ERROR - ❌ No camera found!
2025-11-25 11:32:55,930 - ERROR - ❌ No camera found!
2025-11-25 11:32:55,931 - INFO - Video thread started with source: Camera
2025-11-25 11:32:55,931 - INFO - Video thread started with source: Camera
2025-11-25 11:32:55,931 - ERROR - ❌ No camera found!
2025-11-25 11:32:55,931 - ERROR - ❌ No camera found!
2025-11-25 11:32:56,187 - INFO - Video thread started with source: Camera
2025-11-25 11:32:56,187 - ERROR - ❌ No camera found!
2025-11-25 11:32:56,188 - INFO - Video thread started with source: Camera
2025-11-25 11:32:56,191 - ERROR - ❌ No camera found!
2025-11-25 11:32:56,191 - INFO - Video thread started with source: Camera
2025-11-25 11:32:56,191 - INFO - Video thread started with source: Camera
2025-11-25 11:32:56,192 - ERROR - ❌ No camera found!
2025-11-25 11:32:56,193 - ERROR - ❌ No camera found!
2025-11-25 11:32:56,229 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:56,437 - INFO - Video thread started with source: Camera
2025-11-25 11:32:56,437 - INFO - Video thread started with source: Camera
2025-11-25 11:32:56,437 - INFO - Video thread started with source: Camera
2025-11-25 11:32:56,438 - INFO - Video thread started with source: Camera
2025-11-25 11:32:56,438 - ERROR - ❌ No camera found!
2025-11-25 11:32:56,439 - ERROR - ❌ No camera found!
2025-11-25 11:32:56,440 - ERROR - ❌ No camera found!
2025-11-25 11:32:56,441 - ERROR - ❌ No camera found!
2025-11-25 11:32:56,685 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:56,687 - INFO - Video thread started with source: Camera
2025-11-25 11:32:56,689 - INFO - Video thread started with source: Camera
2025-11-25 11:32:56,693 - ERROR - ❌ No camera found!
2025-11-25 11:32:56,693 - ERROR - ❌ No camera found!
2025-11-25 11:32:56,693 - INFO - Video thread started with source: Camera
2025-11-25 11:32:56,694 - INFO - Video thread started with source: Camera
2025-11-25 11:32:56,695 - ERROR - ❌ No camera found!
2025-11-25 11:32:56,696 - ERROR - ❌ No camera found!
2025-11-25 11:32:56,956 - INFO - Video thread started with source: Camera
2025-11-25 11:32:56,963 - INFO - Video thread started with source: Camera
2025-11-25 11:32:56,964 - INFO - Video thread started with source: Camera
2025-11-25 11:32:56,965 - ERROR - ❌ No camera found!
2025-11-25 11:32:56,965 - ERROR - ❌ No camera found!
2025-11-25 11:32:56,968 - INFO - Video thread started with source: Camera
2025-11-25 11:32:56,969 - ERROR - ❌ No camera found!
2025-11-25 11:32:56,971 - ERROR - ❌ No camera found!
2025-11-25 11:32:56,981 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:57,218 - INFO - Video thread started with source: Camera
2025-11-25 11:32:57,218 - INFO - Video thread started with source: Camera
2025-11-25 11:32:57,219 - ERROR - ❌ No camera found!
2025-11-25 11:32:57,219 - INFO - Video thread started with source: Camera
2025-11-25 11:32:57,220 - ERROR - ❌ No camera found!
2025-11-25 11:32:57,222 - INFO - Video thread started with source: Camera
2025-11-25 11:32:57,222 - ERROR - ❌ No camera found!
2025-11-25 11:32:57,222 - ERROR - ❌ No camera found!
2025-11-25 11:32:57,409 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:57,463 - INFO - Video thread started with source: Camera
2025-11-25 11:32:57,467 - INFO - Video thread started with source: Camera
2025-11-25 11:32:57,467 - INFO - Video thread started with source: Camera
2025-11-25 11:32:57,468 - ERROR - ❌ No camera found!
2025-11-25 11:32:57,468 - INFO - Video thread started with source: Camera
2025-11-25 11:32:57,468 - ERROR - ❌ No camera found!
2025-11-25 11:32:57,469 - ERROR - ❌ No camera found!
2025-11-25 11:32:57,471 - ERROR - ❌ No camera found!
2025-11-25 11:32:57,729 - INFO - Video thread started with source: Camera
2025-11-25 11:32:57,732 - INFO - Video thread started with source: Camera
2025-11-25 11:32:57,735 - INFO - Video thread started with source: Camera
2025-11-25 11:32:57,736 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:57,736 - ERROR - ❌ No camera found!
2025-11-25 11:32:57,737 - ERROR - ❌ No camera found!
2025-11-25 11:32:57,738 - ERROR - ❌ No camera found!
2025-11-25 11:32:57,744 - INFO - Video thread started with source: Camera
2025-11-25 11:32:57,745 - ERROR - ❌ No camera found!
2025-11-25 11:32:57,991 - INFO - Video thread started with source: Camera
2025-11-25 11:32:57,991 - INFO - Video thread started with source: Camera
2025-11-25 11:32:57,992 - ERROR - ❌ No camera found!
2025-11-25 11:32:57,992 - ERROR - ❌ No camera found!
2025-11-25 11:32:57,995 - INFO - Video thread started with source: Camera
2025-11-25 11:32:57,996 - INFO - Video thread started with source: Camera
2025-11-25 11:32:58,001 - ERROR - ❌ No camera found!
2025-11-25 11:32:58,001 - ERROR - ❌ No camera found!
2025-11-25 11:32:58,099 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:58,274 - INFO - Video thread started with source: Camera
2025-11-25 11:32:58,274 - INFO - Video thread started with source: Camera
2025-11-25 11:32:58,275 - ERROR - ❌ No camera found!
2025-11-25 11:32:58,279 - INFO - Video thread started with source: Camera
2025-11-25 11:32:58,280 - ERROR - ❌ No camera found!
2025-11-25 11:32:58,280 - INFO - Video thread started with source: Camera
2025-11-25 11:32:58,280 - ERROR - ❌ No camera found!
2025-11-25 11:32:58,281 - ERROR - ❌ No camera found!
2025-11-25 11:32:58,422 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:58,528 - INFO - Video thread started with source: Camera
2025-11-25 11:32:58,528 - INFO - Video thread started with source: Camera
2025-11-25 11:32:58,530 - INFO - Video thread started with source: Camera
2025-11-25 11:32:58,531 - ERROR - ❌ No camera found!
2025-11-25 11:32:58,531 - INFO - Video thread started with source: Camera
2025-11-25 11:32:58,531 - ERROR - ❌ No camera found!
2025-11-25 11:32:58,533 - ERROR - ❌ No camera found!
2025-11-25 11:32:58,535 - ERROR - ❌ No camera found!
2025-11-25 11:32:58,806 - INFO - Video thread started with source: Camera
2025-11-25 11:32:58,806 - INFO - Video thread started with source: Camera
2025-11-25 11:32:58,810 - ERROR - ❌ No camera found!
2025-11-25 11:32:58,810 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:58,814 - INFO - Video thread started with source: Camera
2025-11-25 11:32:58,814 - ERROR - ❌ No camera found!
2025-11-25 11:32:58,815 - ERROR - ❌ No camera found!
2025-11-25 11:32:58,815 - INFO - Video thread started with source: Camera
2025-11-25 11:32:58,818 - ERROR - ❌ No camera found!
2025-11-25 11:32:59,083 - INFO - Video thread started with source: Camera
2025-11-25 11:32:59,085 - INFO - Video thread started with source: Camera
2025-11-25 11:32:59,086 - INFO - Video thread started with source: Camera
2025-11-25 11:32:59,087 - ERROR - ❌ No camera found!
2025-11-25 11:32:59,090 - ERROR - ❌ No camera found!
2025-11-25 11:32:59,090 - INFO - Video thread started with source: Camera
2025-11-25 11:32:59,092 - ERROR - ❌ No camera found!
2025-11-25 11:32:59,092 - ERROR - ❌ No camera found!
2025-11-25 11:32:59,189 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:59,385 - INFO - Video thread started with source: Camera
2025-11-25 11:32:59,386 - INFO - Video thread started with source: Camera
2025-11-25 11:32:59,387 - ERROR - ❌ No camera found!
2025-11-25 11:32:59,387 - ERROR - ❌ No camera found!
2025-11-25 11:32:59,388 - INFO - Video thread started with source: Camera
2025-11-25 11:32:59,388 - ERROR - ❌ No camera found!
2025-11-25 11:32:59,410 - INFO - Video thread started with source: Camera
2025-11-25 11:32:59,412 - ERROR - ❌ No camera found!
2025-11-25 11:32:59,578 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:59,586 - INFO - Video thread started with source: Camera
2025-11-25 11:32:59,587 - INFO - Video thread started with source: Camera
2025-11-25 11:32:59,587 - INFO - Video thread started with source: Camera
2025-11-25 11:32:59,591 - ERROR - ❌ No camera found!
2025-11-25 11:32:59,591 - INFO - Video thread started with source: Camera
2025-11-25 11:32:59,592 - ERROR - ❌ No camera found!
2025-11-25 11:32:59,592 - ERROR - ❌ No camera found!
2025-11-25 11:32:59,592 - ERROR - ❌ No camera found!
2025-11-25 11:32:59,793 - INFO - Video thread started with source: Camera
2025-11-25 11:32:59,846 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:32:59,847 - ERROR - ❌ No camera found!
2025-11-25 11:32:59,848 - INFO - Video thread started with source: Camera
2025-11-25 11:32:59,854 - INFO - Video thread started with source: Camera
2025-11-25 11:32:59,854 - ERROR - ❌ No camera found!
2025-11-25 11:32:59,857 - INFO - Video thread started with source: Camera
2025-11-25 11:32:59,857 - ERROR - ❌ No camera found!
2025-11-25 11:32:59,862 - ERROR - ❌ No camera found!
2025-11-25 11:33:00,082 - INFO - Video thread started with source: Camera
2025-11-25 11:33:00,085 - INFO - Video thread started with source: Camera
2025-11-25 11:33:00,085 - ERROR - ❌ No camera found!
2025-11-25 11:33:00,085 - INFO - Video thread started with source: Camera
2025-11-25 11:33:00,085 - ERROR - ❌ No camera found!
2025-11-25 11:33:00,086 - INFO - Video thread started with source: Camera
2025-11-25 11:33:00,086 - ERROR - ❌ No camera found!
2025-11-25 11:33:00,086 - ERROR - ❌ No camera found!
2025-11-25 11:33:00,120 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:00,355 - INFO - Video thread started with source: Camera
2025-11-25 11:33:00,357 - INFO - Video thread started with source: Camera
2025-11-25 11:33:00,358 - INFO - Video thread started with source: Camera
2025-11-25 11:33:00,358 - ERROR - ❌ No camera found!
2025-11-25 11:33:00,361 - INFO - Video thread started with source: Camera
2025-11-25 11:33:00,361 - ERROR - ❌ No camera found!
2025-11-25 11:33:00,361 - ERROR - ❌ No camera found!
2025-11-25 11:33:00,362 - ERROR - ❌ No camera found!
2025-11-25 11:33:00,612 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:00,614 - INFO - Video thread started with source: Camera
2025-11-25 11:33:00,616 - ERROR - ❌ No camera found!
2025-11-25 11:33:00,616 - INFO - Video thread started with source: Camera
2025-11-25 11:33:00,616 - INFO - Video thread started with source: Camera
2025-11-25 11:33:00,618 - ERROR - ❌ No camera found!
2025-11-25 11:33:00,618 - INFO - Video thread started with source: Camera
2025-11-25 11:33:00,618 - ERROR - ❌ No camera found!
2025-11-25 11:33:00,620 - ERROR - ❌ No camera found!
2025-11-25 11:33:00,853 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:00,853 - INFO - Video thread started with source: Camera
2025-11-25 11:33:00,855 - ERROR - ❌ No camera found!
2025-11-25 11:33:00,857 - INFO - Video thread started with source: Camera
2025-11-25 11:33:00,857 - ERROR - ❌ No camera found!
2025-11-25 11:33:00,859 - INFO - Video thread started with source: Camera
2025-11-25 11:33:00,859 - INFO - Video thread started with source: Camera
2025-11-25 11:33:00,859 - ERROR - ❌ No camera found!
2025-11-25 11:33:00,860 - ERROR - ❌ No camera found!
2025-11-25 11:33:01,139 - INFO - Video thread started with source: Camera
2025-11-25 11:33:01,139 - INFO - Video thread started with source: Camera
2025-11-25 11:33:01,139 - INFO - Video thread started with source: Camera
2025-11-25 11:33:01,140 - ERROR - ❌ No camera found!
2025-11-25 11:33:01,141 - ERROR - ❌ No camera found!
2025-11-25 11:33:01,142 - ERROR - ❌ No camera found!
2025-11-25 11:33:01,142 - INFO - Video thread started with source: Camera
2025-11-25 11:33:01,144 - ERROR - ❌ No camera found!
2025-11-25 11:33:01,173 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:01,402 - INFO - Video thread started with source: Camera
2025-11-25 11:33:01,404 - INFO - Video thread started with source: Camera
2025-11-25 11:33:01,404 - ERROR - ❌ No camera found!
2025-11-25 11:33:01,405 - ERROR - ❌ No camera found!
2025-11-25 11:33:01,407 - INFO - Video thread started with source: Camera
2025-11-25 11:33:01,411 - INFO - Video thread started with source: Camera
2025-11-25 11:33:01,411 - ERROR - ❌ No camera found!
2025-11-25 11:33:01,414 - ERROR - ❌ No camera found!
2025-11-25 11:33:01,660 - INFO - Video thread started with source: Camera
2025-11-25 11:33:01,666 - ERROR - ❌ No camera found!
2025-11-25 11:33:01,666 - INFO - Video thread started with source: Camera
2025-11-25 11:33:01,666 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:01,667 - INFO - Video thread started with source: Camera
2025-11-25 11:33:01,667 - ERROR - ❌ No camera found!
2025-11-25 11:33:01,668 - INFO - Video thread started with source: Camera
2025-11-25 11:33:01,669 - ERROR - ❌ No camera found!
2025-11-25 11:33:01,670 - ERROR - ❌ No camera found!
2025-11-25 11:33:01,906 - INFO - Video thread started with source: Camera
2025-11-25 11:33:01,906 - INFO - Video thread started with source: Camera
2025-11-25 11:33:01,909 - ERROR - ❌ No camera found!
2025-11-25 11:33:01,910 - INFO - Video thread started with source: Camera
2025-11-25 11:33:01,913 - INFO - Video thread started with source: Camera
2025-11-25 11:33:01,913 - ERROR - ❌ No camera found!
2025-11-25 11:33:01,913 - ERROR - ❌ No camera found!
2025-11-25 11:33:01,915 - ERROR - ❌ No camera found!
2025-11-25 11:33:02,098 - INFO - Video thread started with source: Camera
2025-11-25 11:33:02,157 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:02,159 - INFO - Video thread started with source: Camera
2025-11-25 11:33:02,163 - INFO - Video thread started with source: Camera
2025-11-25 11:33:02,163 - ERROR - ❌ No camera found!
2025-11-25 11:33:02,163 - INFO - Video thread started with source: Camera
2025-11-25 11:33:02,164 - ERROR - ❌ No camera found!
2025-11-25 11:33:02,165 - ERROR - ❌ No camera found!
2025-11-25 11:33:02,165 - ERROR - ❌ No camera found!
2025-11-25 11:33:02,409 - INFO - Video thread started with source: Camera
2025-11-25 11:33:02,410 - INFO - Video thread started with source: Camera
2025-11-25 11:33:02,410 - INFO - Video thread started with source: Camera
2025-11-25 11:33:02,410 - INFO - Video thread started with source: Camera
2025-11-25 11:33:02,411 - ERROR - ❌ No camera found!
2025-11-25 11:33:02,411 - ERROR - ❌ No camera found!
2025-11-25 11:33:02,411 - ERROR - ❌ No camera found!
2025-11-25 11:33:02,412 - ERROR - ❌ No camera found!
2025-11-25 11:33:02,444 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:02,678 - INFO - Video thread started with source: Camera
2025-11-25 11:33:02,678 - INFO - Video thread started with source: Camera
2025-11-25 11:33:02,679 - INFO - Video thread started with source: Camera
2025-11-25 11:33:02,679 - ERROR - ❌ No camera found!
2025-11-25 11:33:02,679 - ERROR - ❌ No camera found!
2025-11-25 11:33:02,681 - ERROR - ❌ No camera found!
2025-11-25 11:33:02,682 - INFO - Video thread started with source: Camera
2025-11-25 11:33:02,684 - ERROR - ❌ No camera found!
2025-11-25 11:33:02,906 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:02,968 - INFO - Video thread started with source: Camera
2025-11-25 11:33:02,971 - ERROR - ❌ No camera found!
2025-11-25 11:33:02,971 - INFO - Video thread started with source: Camera
2025-11-25 11:33:02,972 - INFO - Video thread started with source: Camera
2025-11-25 11:33:02,973 - ERROR - ❌ No camera found!
2025-11-25 11:33:02,976 - INFO - Video thread started with source: Camera
2025-11-25 11:33:02,976 - ERROR - ❌ No camera found!
2025-11-25 11:33:02,976 - ERROR - ❌ No camera found!
2025-11-25 11:33:03,238 - INFO - Video thread started with source: Camera
2025-11-25 11:33:03,240 - ERROR - ❌ No camera found!
2025-11-25 11:33:03,241 - INFO - Video thread started with source: Camera
2025-11-25 11:33:03,242 - INFO - Video thread started with source: Camera
2025-11-25 11:33:03,242 - ERROR - ❌ No camera found!
2025-11-25 11:33:03,242 - INFO - Video thread started with source: Camera
2025-11-25 11:33:03,242 - ERROR - ❌ No camera found!
2025-11-25 11:33:03,246 - ERROR - ❌ No camera found!
2025-11-25 11:33:03,496 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:03,497 - INFO - Video thread started with source: Camera
2025-11-25 11:33:03,499 - ERROR - ❌ No camera found!
2025-11-25 11:33:03,501 - INFO - Video thread started with source: Camera
2025-11-25 11:33:03,503 - INFO - Video thread started with source: Camera
2025-11-25 11:33:03,505 - ERROR - ❌ No camera found!
2025-11-25 11:33:03,505 - ERROR - ❌ No camera found!
2025-11-25 11:33:03,506 - INFO - Video thread started with source: Camera
2025-11-25 11:33:03,507 - ERROR - ❌ No camera found!
2025-11-25 11:33:03,737 - INFO - Video thread started with source: Camera
2025-11-25 11:33:03,737 - INFO - Video thread started with source: Camera
2025-11-25 11:33:03,737 - INFO - Video thread started with source: Camera
2025-11-25 11:33:03,738 - INFO - Video thread started with source: Camera
2025-11-25 11:33:03,738 - ERROR - ❌ No camera found!
2025-11-25 11:33:03,738 - ERROR - ❌ No camera found!
2025-11-25 11:33:03,739 - ERROR - ❌ No camera found!
2025-11-25 11:33:03,739 - ERROR - ❌ No camera found!
2025-11-25 11:33:03,774 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:04,006 - INFO - Video thread started with source: Camera
2025-11-25 11:33:04,007 - INFO - Video thread started with source: Camera
2025-11-25 11:33:04,068 - ERROR - ❌ No camera found!
2025-11-25 11:33:04,069 - INFO - Video thread started with source: Camera
2025-11-25 11:33:04,070 - ERROR - ❌ No camera found!
2025-11-25 11:33:04,070 - ERROR - ❌ No camera found!
2025-11-25 11:33:04,283 - INFO - Video thread started with source: Camera
2025-11-25 11:33:04,284 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:04,284 - INFO - Video thread started with source: Camera
2025-11-25 11:33:04,285 - ERROR - ❌ No camera found!
2025-11-25 11:33:04,289 - ERROR - ❌ No camera found!
2025-11-25 11:33:04,289 - INFO - Video thread started with source: Camera
2025-11-25 11:33:04,291 - ERROR - ❌ No camera found!
2025-11-25 11:33:04,490 - INFO - Video thread started with source: Camera
2025-11-25 11:33:04,491 - ERROR - ❌ No camera found!
2025-11-25 11:33:04,491 - INFO - Video thread started with source: Camera
2025-11-25 11:33:04,492 - INFO - Video thread started with source: Camera
2025-11-25 11:33:04,492 - ERROR - ❌ No camera found!
2025-11-25 11:33:04,492 - ERROR - ❌ No camera found!
2025-11-25 11:33:04,592 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:04,721 - INFO - Video thread started with source: Camera
2025-11-25 11:33:04,722 - ERROR - ❌ No camera found!
2025-11-25 11:33:04,724 - INFO - Video thread started with source: Camera
2025-11-25 11:33:04,725 - ERROR - ❌ No camera found!
2025-11-25 11:33:04,877 - INFO - Video thread started with source: Camera
2025-11-25 11:33:04,879 - INFO - Video thread started with source: Camera
2025-11-25 11:33:04,880 - ERROR - ❌ No camera found!
2025-11-25 11:33:04,880 - ERROR - ❌ No camera found!
2025-11-25 11:33:04,890 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:05,030 - INFO - Video thread started with source: Camera
2025-11-25 11:33:05,032 - ERROR - ❌ No camera found!
2025-11-25 11:33:05,033 - INFO - Video thread started with source: Camera
2025-11-25 11:33:05,034 - ERROR - ❌ No camera found!
2025-11-25 11:33:05,189 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:05,190 - INFO - Video thread started with source: Camera
2025-11-25 11:33:05,190 - ERROR - ❌ No camera found!
2025-11-25 11:33:05,193 - INFO - Video thread started with source: Camera
2025-11-25 11:33:05,195 - ERROR - ❌ No camera found!
2025-11-25 11:33:05,362 - INFO - Video thread started with source: Camera
2025-11-25 11:33:05,363 - INFO - Video thread started with source: Camera
2025-11-25 11:33:05,364 - ERROR - ❌ No camera found!
2025-11-25 11:33:05,364 - ERROR - ❌ No camera found!
2025-11-25 11:33:05,376 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:05,525 - INFO - Video thread started with source: Camera
2025-11-25 11:33:05,525 - INFO - Video thread started with source: Camera
2025-11-25 11:33:05,526 - ERROR - ❌ No camera found!
2025-11-25 11:33:05,527 - ERROR - ❌ No camera found!
2025-11-25 11:33:05,666 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:05,671 - INFO - Video thread started with source: Camera
2025-11-25 11:33:05,671 - INFO - Video thread started with source: Camera
2025-11-25 11:33:05,672 - ERROR - ❌ No camera found!
2025-11-25 11:33:05,673 - ERROR - ❌ No camera found!
2025-11-25 11:33:05,837 - INFO - Video thread started with source: Camera
2025-11-25 11:33:05,837 - INFO - Video thread started with source: Camera
2025-11-25 11:33:05,838 - ERROR - ❌ No camera found!
2025-11-25 11:33:05,839 - ERROR - ❌ No camera found!
2025-11-25 11:33:05,913 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:06,000 - INFO - Video thread started with source: Camera
2025-11-25 11:33:06,001 - ERROR - ❌ No camera found!
2025-11-25 11:33:06,097 - INFO - Video thread started with source: Camera
2025-11-25 11:33:06,098 - ERROR - ❌ No camera found!
2025-11-25 11:33:06,103 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:06,197 - INFO - Video thread started with source: Camera
2025-11-25 11:33:06,198 - ERROR - ❌ No camera found!
2025-11-25 11:33:06,290 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:06,295 - INFO - Video thread started with source: Camera
2025-11-25 11:33:06,295 - ERROR - ❌ No camera found!
2025-11-25 11:33:06,383 - INFO - Video thread started with source: Camera
2025-11-25 11:33:06,384 - ERROR - ❌ No camera found!
2025-11-25 11:33:06,396 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:06,480 - INFO - Video thread started with source: Camera
2025-11-25 11:33:06,481 - ERROR - ❌ No camera found!
2025-11-25 11:33:06,584 - INFO - Video thread started with source: Camera
2025-11-25 11:33:06,585 - ERROR - ❌ No camera found!
2025-11-25 11:33:06,592 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:06,683 - INFO - Video thread started with source: Camera
2025-11-25 11:33:06,684 - ERROR - ❌ No camera found!
2025-11-25 11:33:06,782 - INFO - Video thread started with source: Camera
2025-11-25 11:33:06,783 - ERROR - ❌ No camera found!
2025-11-25 11:33:06,787 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:06,883 - INFO - Video thread started with source: Camera
2025-11-25 11:33:06,884 - ERROR - ❌ No camera found!
2025-11-25 11:33:06,978 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:06,981 - INFO - Video thread started with source: Camera
2025-11-25 11:33:06,981 - ERROR - ❌ No camera found!
2025-11-25 11:33:07,077 - INFO - Video thread started with source: Camera
2025-11-25 11:33:07,077 - ERROR - ❌ No camera found!
2025-11-25 11:33:07,090 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:07,166 - INFO - Video thread started with source: Camera
2025-11-25 11:33:07,167 - ERROR - ❌ No camera found!
2025-11-25 11:33:07,259 - INFO - Video thread started with source: Camera
2025-11-25 11:33:07,260 - ERROR - ❌ No camera found!
2025-11-25 11:33:07,266 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:07,359 - INFO - Video thread started with source: Camera
2025-11-25 11:33:07,360 - ERROR - ❌ No camera found!
2025-11-25 11:33:07,456 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:07,532 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:07,609 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:07,679 - INFO - Video thread started with source: Camera
2025-11-25 11:33:07,681 - ERROR - ❌ No camera found!
2025-11-25 11:33:07,687 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:07,787 - INFO - Video thread started with source: Camera
2025-11-25 11:33:07,788 - ERROR - ❌ No camera found!
2025-11-25 11:33:07,885 - INFO - Video thread started with source: Camera
2025-11-25 11:33:07,886 - ERROR - ❌ No camera found!
2025-11-25 11:33:07,891 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:07,983 - INFO - Video thread started with source: Camera
2025-11-25 11:33:07,984 - ERROR - ❌ No camera found!
2025-11-25 11:33:08,084 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:08,086 - INFO - Video thread started with source: Camera
2025-11-25 11:33:08,088 - ERROR - ❌ No camera found!
2025-11-25 11:33:08,188 - INFO - Video thread started with source: Camera
2025-11-25 11:33:08,190 - ERROR - ❌ No camera found!
2025-11-25 11:33:08,223 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:08,287 - INFO - Video thread started with source: Camera
2025-11-25 11:33:08,287 - ERROR - ❌ No camera found!
2025-11-25 11:33:08,385 - INFO - Video thread started with source: Camera
2025-11-25 11:33:08,386 - ERROR - ❌ No camera found!
2025-11-25 11:33:08,403 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:08,487 - INFO - Video thread started with source: Camera
2025-11-25 11:33:08,488 - ERROR - ❌ No camera found!
2025-11-25 11:33:08,582 - INFO - Video thread started with source: Camera
2025-11-25 11:33:08,583 - ERROR - ❌ No camera found!
2025-11-25 11:33:08,597 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:08,673 - INFO - Video thread started with source: Camera
2025-11-25 11:33:08,674 - ERROR - ❌ No camera found!
2025-11-25 11:33:08,765 - INFO - Video thread started with source: Camera
2025-11-25 11:33:08,766 - ERROR - ❌ No camera found!
2025-11-25 11:33:08,772 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:08,862 - INFO - Video thread started with source: Camera
2025-11-25 11:33:08,862 - ERROR - ❌ No camera found!
2025-11-25 11:33:08,899 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:08,954 - INFO - Video thread started with source: Camera
2025-11-25 11:33:08,954 - ERROR - ❌ No camera found!
2025-11-25 11:33:09,045 - INFO - Video thread started with source: Camera
2025-11-25 11:33:09,045 - ERROR - ❌ No camera found!
2025-11-25 11:33:09,078 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:09,138 - INFO - Video thread started with source: Camera
2025-11-25 11:33:09,139 - ERROR - ❌ No camera found!
2025-11-25 11:33:09,230 - INFO - Video thread started with source: Camera
2025-11-25 11:33:09,231 - ERROR - ❌ No camera found!
2025-11-25 11:33:09,236 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:09,321 - INFO - Video thread started with source: Camera
2025-11-25 11:33:09,321 - ERROR - ❌ No camera found!
2025-11-25 11:33:09,413 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:09,415 - INFO - Video thread started with source: Camera
2025-11-25 11:33:09,416 - ERROR - ❌ No camera found!
2025-11-25 11:33:09,508 - INFO - Video thread started with source: Camera
2025-11-25 11:33:09,509 - ERROR - ❌ No camera found!
2025-11-25 11:33:09,521 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:09,602 - INFO - Video thread started with source: Camera
2025-11-25 11:33:09,603 - ERROR - ❌ No camera found!
2025-11-25 11:33:09,699 - INFO - Video thread started with source: Camera
2025-11-25 11:33:09,700 - ERROR - ❌ No camera found!
2025-11-25 11:33:09,712 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:09,800 - INFO - Video thread started with source: Camera
2025-11-25 11:33:09,800 - ERROR - ❌ No camera found!
2025-11-25 11:33:09,899 - INFO - Video thread started with source: Camera
2025-11-25 11:33:09,902 - ERROR - ❌ No camera found!
2025-11-25 11:33:09,902 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:09,994 - INFO - Video thread started with source: Camera
2025-11-25 11:33:09,995 - ERROR - ❌ No camera found!
2025-11-25 11:33:10,030 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:10,087 - INFO - Video thread started with source: Camera
2025-11-25 11:33:10,088 - ERROR - ❌ No camera found!
2025-11-25 11:33:10,177 - INFO - Video thread started with source: Camera
2025-11-25 11:33:10,178 - ERROR - ❌ No camera found!
2025-11-25 11:33:10,191 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:10,272 - INFO - Video thread started with source: Camera
2025-11-25 11:33:10,272 - ERROR - ❌ No camera found!
2025-11-25 11:33:10,362 - INFO - Video thread started with source: Camera
2025-11-25 11:33:10,363 - ERROR - ❌ No camera found!
2025-11-25 11:33:10,365 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:10,458 - INFO - Video thread started with source: Camera
2025-11-25 11:33:10,458 - ERROR - ❌ No camera found!
2025-11-25 11:33:10,490 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:10,558 - INFO - Video thread started with source: Camera
2025-11-25 11:33:10,559 - ERROR - ❌ No camera found!
2025-11-25 11:33:10,654 - INFO - Video thread started with source: Camera
2025-11-25 11:33:10,655 - ERROR - ❌ No camera found!
2025-11-25 11:33:10,663 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:10,749 - INFO - Video thread started with source: Camera
2025-11-25 11:33:10,749 - ERROR - ❌ No camera found!
2025-11-25 11:33:10,843 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:10,846 - INFO - Video thread started with source: Camera
2025-11-25 11:33:10,847 - ERROR - ❌ No camera found!
2025-11-25 11:33:10,938 - INFO - Video thread started with source: Camera
2025-11-25 11:33:10,939 - ERROR - ❌ No camera found!
2025-11-25 11:33:10,950 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:11,032 - INFO - Video thread started with source: Camera
2025-11-25 11:33:11,033 - ERROR - ❌ No camera found!
2025-11-25 11:33:11,123 - INFO - Video thread started with source: Camera
2025-11-25 11:33:11,124 - ERROR - ❌ No camera found!
2025-11-25 11:33:11,127 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:11,214 - INFO - Video thread started with source: Camera
2025-11-25 11:33:11,214 - ERROR - ❌ No camera found!
2025-11-25 11:33:11,245 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:11,306 - INFO - Video thread started with source: Camera
2025-11-25 11:33:11,307 - ERROR - ❌ No camera found!
2025-11-25 11:33:11,406 - INFO - Video thread started with source: Camera
2025-11-25 11:33:11,406 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:11,407 - ERROR - ❌ No camera found!
2025-11-25 11:33:11,494 - INFO - Video thread started with source: Camera
2025-11-25 11:33:11,495 - ERROR - ❌ No camera found!
2025-11-25 11:33:11,584 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:11,587 - INFO - Video thread started with source: Camera
2025-11-25 11:33:11,588 - ERROR - ❌ No camera found!
2025-11-25 11:33:11,677 - INFO - Video thread started with source: Camera
2025-11-25 11:33:11,677 - ERROR - ❌ No camera found!
2025-11-25 11:33:11,764 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:11,767 - INFO - Video thread started with source: Camera
2025-11-25 11:33:11,768 - ERROR - ❌ No camera found!
2025-11-25 11:33:11,855 - INFO - Video thread started with source: Camera
2025-11-25 11:33:11,856 - ERROR - ❌ No camera found!
2025-11-25 11:33:11,886 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:11,945 - INFO - Video thread started with source: Camera
2025-11-25 11:33:11,946 - ERROR - ❌ No camera found!
2025-11-25 11:33:12,036 - INFO - Video thread started with source: Camera
2025-11-25 11:33:12,037 - ERROR - ❌ No camera found!
2025-11-25 11:33:12,043 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:12,127 - INFO - Video thread started with source: Camera
2025-11-25 11:33:12,127 - ERROR - ❌ No camera found!
2025-11-25 11:33:12,219 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:12,221 - INFO - Video thread started with source: Camera
2025-11-25 11:33:12,222 - ERROR - ❌ No camera found!
2025-11-25 11:33:12,311 - INFO - Video thread started with source: Camera
2025-11-25 11:33:12,312 - ERROR - ❌ No camera found!
2025-11-25 11:33:12,342 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:12,401 - INFO - Video thread started with source: Camera
2025-11-25 11:33:12,402 - ERROR - ❌ No camera found!
2025-11-25 11:33:12,493 - INFO - Video thread started with source: Camera
2025-11-25 11:33:12,494 - ERROR - ❌ No camera found!
2025-11-25 11:33:12,498 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:12,584 - INFO - Video thread started with source: Camera
2025-11-25 11:33:12,584 - ERROR - ❌ No camera found!
2025-11-25 11:33:12,618 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:12,690 - INFO - Video thread started with source: Camera
2025-11-25 11:33:12,691 - ERROR - ❌ No camera found!
2025-11-25 11:33:12,812 - INFO - Video thread started with source: Camera
2025-11-25 11:33:12,812 - ERROR - ❌ No camera found!
2025-11-25 11:33:12,842 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:12,911 - INFO - Video thread started with source: Camera
2025-11-25 11:33:12,912 - ERROR - ❌ No camera found!
2025-11-25 11:33:13,001 - INFO - Video thread started with source: Camera
2025-11-25 11:33:13,001 - ERROR - ❌ No camera found!
2025-11-25 11:33:13,007 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:13,091 - INFO - Video thread started with source: Camera
2025-11-25 11:33:13,091 - ERROR - ❌ No camera found!
2025-11-25 11:33:13,179 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:13,182 - INFO - Video thread started with source: Camera
2025-11-25 11:33:13,183 - ERROR - ❌ No camera found!
2025-11-25 11:33:13,271 - INFO - Video thread started with source: Camera
2025-11-25 11:33:13,271 - ERROR - ❌ No camera found!
2025-11-25 11:33:13,305 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:13,361 - INFO - Video thread started with source: Camera
2025-11-25 11:33:13,361 - ERROR - ❌ No camera found!
2025-11-25 11:33:13,450 - INFO - Video thread started with source: Camera
2025-11-25 11:33:13,451 - ERROR - ❌ No camera found!
2025-11-25 11:33:13,461 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:13,540 - INFO - Video thread started with source: Camera
2025-11-25 11:33:13,541 - ERROR - ❌ No camera found!
2025-11-25 11:33:13,628 - INFO - Video thread started with source: Camera
2025-11-25 11:33:13,629 - ERROR - ❌ No camera found!
2025-11-25 11:33:13,635 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:13,720 - INFO - Video thread started with source: Camera
2025-11-25 11:33:13,721 - ERROR - ❌ No camera found!
2025-11-25 11:33:13,810 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:13,813 - INFO - Video thread started with source: Camera
2025-11-25 11:33:13,814 - ERROR - ❌ No camera found!
2025-11-25 11:33:13,902 - INFO - Video thread started with source: Camera
2025-11-25 11:33:13,903 - ERROR - ❌ No camera found!
2025-11-25 11:33:13,916 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:13,993 - INFO - Video thread started with source: Camera
2025-11-25 11:33:13,994 - ERROR - ❌ No camera found!
2025-11-25 11:33:14,085 - INFO - Video thread started with source: Camera
2025-11-25 11:33:14,088 - ERROR - ❌ No camera found!
2025-11-25 11:33:14,088 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:14,178 - INFO - Video thread started with source: Camera
2025-11-25 11:33:14,179 - ERROR - ❌ No camera found!
2025-11-25 11:33:14,211 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:14,270 - INFO - Video thread started with source: Camera
2025-11-25 11:33:14,270 - ERROR - ❌ No camera found!
2025-11-25 11:33:14,366 - INFO - Video thread started with source: Camera
2025-11-25 11:33:14,367 - ERROR - ❌ No camera found!
2025-11-25 11:33:14,373 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:14,466 - INFO - Video thread started with source: Camera
2025-11-25 11:33:14,467 - ERROR - ❌ No camera found!
2025-11-25 11:33:14,566 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:14,569 - INFO - Video thread started with source: Camera
2025-11-25 11:33:14,571 - ERROR - ❌ No camera found!
2025-11-25 11:33:14,681 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:14,751 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:14,825 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:14,900 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:14,974 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:15,051 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:15,126 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:15,204 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:15,282 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:15,361 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:15,432 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:15,504 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:15,575 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:15,646 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:15,716 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:15,789 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:15,860 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:15,930 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:15,999 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:16,068 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:16,140 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:16,210 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:16,280 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:16,352 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:16,423 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:16,494 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:16,563 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:16,632 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:16,708 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
2025-11-25 11:33:16,781 - ERROR - Error processing frame: Graph has errors: 
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.
; Packet timestamp mismatch on a calculator receiving from stream "image". Current minimum expected timestamp is 5766610 but received 5766609. Are you using a custom InputStreamHandler? Note that some InputStreamHandlers allow timestamps that are not strictly monotonically increasing. See for example the ImmediateInputStreamHandler class comment.